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.
NewMaintained
Automatic
◆Research pack
Last verified 7/24/2026
What it changes
Passed 7 of 21 test cases with the skill, and 14 of 21 without it.
Without skill67%
With skill33%
3 fixed2 passed either way17 still failing0 broke
Pass-rate lift
-33 pp
Tokens
+10%
Agent turns
0%
Response time
-4%
Model gemini-3.6-flashMeasured 7/24/2026v15 of 22 cases passed with skill · 21 comparable
Tokens, turns and time describe resource use, not a dollar price.
What's inside
The instructions your model reads when the skill loads.
SKILL.md44 lines2 files
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