paper-context-resolver
lllllllama/rigorpilot-skills
Resolve reproduction-critical paper details when README and repo files leave gaps.
What is paper-context-resolver?
A helper skill for deep learning repo reproduction that fills narrow, specific gaps by extracting reproduction-critical details from primary paper sources. Use it when you have a concrete reproduction question about dataset splits, preprocessing, evaluation protocols, checkpoints, or runtime assumptions that the README doesn't answer.
- Identifies reproduction-critical gaps between README/repo files and paper requirements
- Extracts specific details: dataset splits, preprocessing steps, evaluation protocols, checkpoint mappings, runtime assumptions
- Documents conflicts between README guidance and paper specifications
- Provides narrowed source lists and evidence-backed answers
- Distinguishes direct evidence from inference in findings
How to install paper-context-resolver
npx skills add https://github.com/lllllllama/rigorpilot-skills --skill paper-context-resolverHow to use paper-context-resolver
- 1.Identify the specific reproduction-critical question (dataset split, preprocessing, evaluation protocol, etc.)
- 2.Gather existing README and repo file evidence
- 3.Provide the paper link or metadata if available
- 4.Run the skill with the target repo metadata and concrete reproduction question
- 5.Review the narrowed source list and reproduction-relevant answer
- 6.Check for any documented README-paper conflicts
Use cases
- Determining the exact dataset split used in a paper when the repo README is vague
- Finding preprocessing parameters or evaluation metrics not documented in the repository
- Resolving checkpoint naming or model weight mapping discrepancies
- Clarifying runtime assumptions (batch size, hardware, precision) from the original paper
- Recording conflicts when README instructions differ from paper methodology
- Deep learning researchers reproducing published work
- ML engineers implementing paper-based systems
- Repository maintainers documenting reproduction steps
- Anyone needing precise paper details for reproducibility verification
paper-context-resolver FAQ
Use it when you have a concrete reproduction gap and need the skill to narrow down which paper sections contain the answer, document conflicts with the README, and distinguish evidence from inference.
No. It focuses only on reproduction-critical details. For general paper explanations, use a different approach.
Don't use this skill. It's designed to fill gaps when the README is insufficient, not to override or replace README guidance.
No. It only extracts and documents paper details relevant to reproduction. Environment setup and command execution are out of scope.
The skill explicitly documents the conflict and notes it in the output, helping you decide which source to follow.
Full instructions (SKILL.md)
Source of truth, from lllllllama/rigorpilot-skills.
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.
Related skills
More from lllllllama/rigorpilot-skills and the wider catalog.
analyze-project
Read-only analysis of deep learning repositories to understand structure, configs, and suspicious patterns.
ai-research-explore
Auditable deep learning research exploration with idea gating, fair comparison, and governed experiments.
explore-code
Auditable exploratory code modifications for deep learning research on isolated branches with rollback tracking.
ai-research-reproduction
README-first deep learning repository reproduction with auditable evidence and standardized outputs.
safe-debug
Conservative diagnosis and minimal patching for deep learning training failures without automatic code mutation.
run-train
Execute and document deep learning training runs with reproducibility and status tracking.