paper-context-resolver

Resolve reproduction-critical gaps by extracting dataset, preprocessing, and protocol details from primary papers. Targets narrow reproduction questions (dataset splits, preprocessing steps, evaluation protocols, checkpoint mappings) rather than general paper summaries Requires concrete reproduction context: existing README, repo evidence, and a specific gap to fill Documents conflicts between README guidance and paper sources explicitly Designed as a helper skill, typically invoked by orchestrators to supplement README-first reproduction workflows Skips general paper explanation, title-only lookups, and environment setup tasks

INSTALLATION
npx skills add https://github.com/lllllllama/ai-paper-reproduction-skill --skill paper-context-resolver
Run in your project or agent environment. Adjust flags if your CLI version differs.

SKILL.md

paper-context-resolver

Use this as the Rigor Paper Context helper. The installed slug remains

paper-context-resolver for compatibility.

When to apply

  • README and repo files leave a reproduction-critical gap.
  • The gap concerns dataset version, split, preprocessing, evaluation protocol, checkpoint mapping, or runtime assumptions.
  • The main skill needs a narrow evidence supplement instead of a full paper summary.
  • There is already a concrete reproduction question to answer.

When not to apply

  • The README already gives enough reproduction detail.
  • The user wants a general paper explanation rather than reproduction support.
  • The goal is to override README instructions without documenting the conflict.
  • The only available input is a paper title and there is no concrete reproduction gap yet.

Clear boundaries

  • This skill is optional.
  • This skill is helper-tier and should usually be orchestrator-invoked.
  • It supplements README-first reproduction.
  • It does not replace the main orchestration flow.
  • It does not summarize the whole paper by default.

Input expectations

  • target repo metadata
  • reproduction-critical question
  • existing README or repo evidence
  • any already known paper links

Output expectations

  • narrowed source list
  • reproduction-relevant answer only
  • explicit README-paper conflict note when applicable
  • clear distinction between direct evidence and inference

Notes

Use references/paper-assisted-reproduction.md.

BrowserAct

Let your agent run on any real-world website

Bypass CAPTCHA & anti-bot for free. Start local, scale to cloud.

Explore BrowserAct Skills →

Stop writing automation&scrapers

Install the CLI. Run your first Skill in 30 seconds. Scale when you're ready.

Start free
free · no credit card