Skills lllllllama rigorpilot-skills RigorPilot
paper-context-resolver
- Use it when:
- You're reproducing a paper's code and the README leaves one specific question open, such as a dataset split or evaluation protocol.
- It does:
- Looks up that one detail in the paper's primary sources: the README's paper link, the project page, arXiv or OpenReview.
- You get:
- A short answer with its sources, separating direct evidence from inference and noting any conflict with the README.
- Not for:
- Summarizing a paper, finding a paper from its title alone, or overriding the README.
- Usually called by:
- RigorPilot's main skill, which reproduces a research repo from its README.
Skill 3 of 11 in the RigorPilot bundle, after repo-intake-and-plan and before env-and-assets-bootstrap.
TL;DR
A narrow, optional helper in RigorPilot, a set of skills that reproduces deep-learning research code by following its README. It comes in only after the README and repo files have been read and a concrete gap remains, such as which dataset version or split, which preprocessing, which evaluation protocol, or which checkpoint matches which model. It searches in a fixed order: the paper the README links, the official project or paper page, the arXiv or OpenReview record, and Google Scholar only to locate those. It answers that question alone, without a paper summary or guessed "best settings". When the paper and README disagree, it doesn't quietly switch to the paper: it records the conflict, says which source says what, and keeps the README as the default.
Summarizes the skill at fb3ccdf.
npx skills add https://github.com/lllllllama/rigorpilot-skills --skill paper-context-resolver skills.sh pageSource on GitHubAll skills from lllllllama/rigorpilot-skills
More weekly downloads than 93% of skills
Weekly values
| Week to | Installs |
|---|---|
| Sep 21 | 48 |
| Sep 28 | 39 |
| Oct 5 | 59 |
| Oct 12 | 3,511 |
| Oct 19 | 10,927 |
| Oct 26 | 11,049 |
| Nov 2 | 8,756 |
| Nov 9 | 7,280 |
More downloads than 96% of skills
Fewer stars than 88% of repos
Newer than 97% of skills
| Category |
Research reproduction, financial data, charts and diagrams. |
|---|---|
| Type |
A multi-step process the agent follows: interview, debug, run a TDD loop, review. |
| Effect |
Adds no side effects of its own. It shapes how the agent thinks, writes or reviews. Guidelines and routers are always effect:none, even when the task they support edits code. |
| Needs |
Instructions only. Works in any agent that supports skills. |
| Publisher |
Everyone else. Unverified vendor claims default to community. |
| Topics |
SKILL.md
From lllllllama/rigorpilot-skills at fb3ccdf. Checked daily, last changed Oct 20, 2026.
Frontmatter
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.