Claude
Skill
paper-context-resolver
Rigor Paper Context helper for README-first deep learning repo reproduction. Use only when the README and repository files leave a narrow reproduction-critical gap and the task is to resolve a specific paper detail such as dataset split, preprocessing, evaluation protocol, checkp
Virus-scanned
Reviewed automatically before listing.
Download
lllllllama-rigorpilot-skills-skills_paper-context-resolver-bd91195.zip · 2 KB
Install
skills CLI
npx skills add https://github.com/lllllllama/RigorPilot-Skills/tree/main/skills/paper-context-resolver
Claude Code
claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install lllllllama-rigorpilot-skills@llmmart
Git
git clone https://github.com/lllllllama/RigorPilot-Skills.git
The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole lllllllama/rigorpilot-skills collection as a plugin from our marketplace. Git is the plain clone.
Skill manifest
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.
Files (rigorpilot-skills)
-
agents
-
openai.yaml 368 B
display_name: Rigor Paper Context short_description: Rigor Paper Context helper for narrow reproduction-critical paper gaps without overriding README by default. default_prompt: Use the linked paper only to resolve a narrow reproduction-critical detail such as dataset split, evaluation protocol, preprocessing, or checkpoint mapping, and record any README conflicts.
-
-
references
-
paper-assisted-reproduction.md 1.3 KB
# Paper-Assisted Reproduction ## Purpose Use paper context only to unblock README-first reproduction when the repository leaves a critical gap. Only invoke this step after README and repo inspection already produced a concrete unanswered question. ## Source order 1. paper link explicitly provided by the README 2. official project page or official paper page 3. arXiv or OpenReview primary paper record 4. Google Scholar only to help locate the primary source ## Allowed question types - dataset version or split - preprocessing or postprocessing details - evaluation protocol details - checkpoint or model variant mapping - critical runtime assumptions ## Trigger discipline Good trigger: - "README is ambiguous about the evaluation split. Check the linked paper and record the conflict if needed." Bad trigger: - "Summarize this paper." - "Find the paper for this repository title and explain it." - "Tell me everything the paper changed compared with prior work." ## Default exclusions - full paper summary - novelty explanation - broad related-work discussion - speculative "best settings" not tied to reproduction ## Conflict rule If README and paper disagree: - do not silently replace README - record the conflict - explain which source says what - preserve the README-first policy in the final report
-
-
SKILL.md 2 KB
--- name: paper-context-resolver description: Rigor Paper Context helper for README-first deep learning repo reproduction. Use only when the README and repository files leave a narrow reproduction-critical gap and the task is to resolve a specific paper detail such as dataset split, preprocessing, evaluation protocol, checkpoint mapping, or runtime assumption from primary paper sources while recording conflicts. Do not use for general paper summary, repo scanning, environment setup, command execution, title-only paper lookup, or replacing README guidance by default. --- # 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 (0)
Sign in to join the conversation.
Reviews (0)
No reviews yet.
No comments yet.