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, 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.
Save adds this to your Playground favorites. Hearts show appreciation.
How you can use it
- Look up one missing detail, such as a dataset split or evaluation method, from a paper when a code repository's README does not explain it.
- Record where a paper and its code disagree on a detail needed to reproduce results.
Who it's for
- Researchers reproducing deep learning results from a paper's code
- Reviewers checking whether a code repository matches its paper
Written by AI from this item's description. Check the source before relying on it.
See what it would do for your project in Playground →Set it up
Pick the app you use.
paper-context-resolver
- 1
Open Plugins → Skills
Left sidebar → Plugins, then the Skills tab.
- 2
Add → Upload from your computer
Pick the SKILL.md (or Create with editor and paste the text), then Create.
- 3
Use it with /
In a chat, type / and pick the skill, then write your request.
Show the skill file
# 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`.
Read a skill before you install it: it tells the AI what to do. Promptu never installs or runs anything.
Install from the command line
npx skills add https://github.com/lllllllama/rigorpilot-skills
Review commands before running them. Promptu never runs code on your machine or pushes changes to your repo.

