mcpField
P
paper-context-resolver

paper-context-resolver

github.com/lllllllamaData & databases486140.4k installsUpdated 5w ago
Repository

About paper-context-resolver

paper-context-resolver is a helper skill for Rigor Paper Context that fills narrow evidence gaps when a README and repo files lack reproduction-critical details. It is aimed at orchestrator-invoked reproduction workflows and answers only reproduction-relevant questions rather than summarizing the whole paper.

Key features

  1. 01Supplements dataset version and split details
  2. 02Checks evaluation protocol and checkpoint mapping
  3. 03Flags conflicts between README and paper
  4. 04Separates direct evidence from inference

Use cases

  1. 01Filling in dataset split details missing from a README
  2. 02Verifying checkpoint correspondence with paper experiment setup
  3. 03Providing a narrow evidence supplement alongside a main skill

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/lllllllama/ai-paper-reproduction-skill --skill paper-context-resolver

After installing, type/paper-context-resolverin Claude Code to confirm it loaded.

Details

From the project README

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.

Comments

Markdown supported