mcpField
P
paper-context-resolver

paper-context-resolver

github.com/lllllllamaData & databases486479.8k installsUpdated 5w ago
Repository

About paper-context-resolver

paper-context-resolver is an optional helper skill within Rigor that supplies narrow paper evidence when a reproduction-critical gap remains after reading the README and repository. It targets questions about dataset version, split, preprocessing or evaluation protocol, and does not summarize the whole paper.

Key features

  1. 01Narrow evidence lookup for reproduction gaps
  2. 02Flags conflicts between README and paper
  3. 03Distinguishes direct evidence from inference
  4. 04Returns answers relevant to the reproduction question

Use cases

  1. 01Confirming dataset version or split definition
  2. 02Checking evaluation protocol and preprocessing steps
  3. 03Mapping checkpoints to reported paper results

Install

Copy the command and run it in a terminal.

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

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

Bundled filesagents/openai.yamlreferences/paper-assisted-reproduction.md

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