Paper Context Resolver
- 176k installs
- 512 repo stars
- Updated July 26, 2026
- lllllllama/rigorpilot-skills
This is a copy of paper-context-resolver by lllllllama - installs and ranking accrue to the original listing.
paper-context-resolver is a RigorPilot helper skill that fetches precise reproduction details from primary paper sources for developers who hit critical README gaps during deep learning repo reproduction.
About
paper-context-resolver is the Rigor Paper Context helper in rigorpilot-skills for README-first deep learning reproduction. It activates only when README and repository files leave a narrow reproduction-critical gap, then resolves specific paper details such as dataset splits, preprocessing steps, evaluation protocols, checkpoint mapping, or runtime assumptions from primary sources while recording conflicts. Developers reach for paper-context-resolver during ai-research-reproduction when documented repo guidance is incomplete but the missing detail is essential to a trustworthy run. The skill is not for general paper summaries, title-only lookups, environment setup, command execution, or replacing README guidance by default.
- Resolves narrow reproduction-critical gaps from primary paper sources
- Targets dataset version, split, preprocessing, evaluation protocol, checkpoint mapping, or runtime assumptions
- Records any conflicts with README or repo files
- Helper-tier skill designed for orchestration with main reproduction agents
- Strict boundaries prevent general summarization or README replacement
Paper Context Resolver by the numbers
- 175,938 all-time installs (skills.sh)
- +25,331 installs in the week ending Jul 28, 2026 (Skillselion tracking)
- Security screen: MEDIUM risk (skills.sh audit)
- Data as of Jul 28, 2026 (Skillselion catalog sync)
npx skills add https://github.com/lllllllama/rigorpilot-skills --skill paper-context-resolverAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 176k |
|---|---|
| repo stars | ★ 512 |
| Security audit | 2 / 3 scanners passed |
| Last updated | July 26, 2026 |
| Repository | lllllllama/rigorpilot-skills ↗ |
How do you fill ML reproduction gaps from papers?
Fetch precise reproduction details like dataset splits, preprocessing steps, or evaluation protocols from the original paper when the README leaves a critical gap.
Who is it for?
ML engineers reproducing research code who encounter a single critical README gap answerable from the primary paper.
Skip if: Developers who need full paper summaries, generic repo scanning, environment bootstrap, or broad literature review instead of one reproduction-critical detail.
When should I use this skill?
README and repo files leave a narrow reproduction-critical gap requiring a specific paper detail such as splits or evaluation protocol.
What you get
Recorded paper-sourced details and documented conflicts for a specific reproduction gap
- Resolved paper detail for a specific gap
- Recorded source conflicts
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
Notes
Use references/paper-assisted-reproduction.md.
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.
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
Related skills
Setup Matt Pocock SkillsScaffold the per-repo configuration that Matt Pocock’s engineering agent skills rely on so they understand the issue tracker, triage labels, and domain documentation la462k185k
Lark Skill MakerQuickly turn any Lark/Feishu OpenAPI call or multi-step workflow into a reusable agent skill with its own SKILL.md.379k15.8k
CavemanSlash token usage by roughly 75% while keeping every technical detail intact when working with Claude Code, Cursor or similar agents.378k92.5k
Lark AppsConnect Claude, Cursor or custom agents directly to Lark (Feishu) for messaging, document automation, approval workflows and enterprise data access.375k
Running Claude Code Via Litellm CopilotRun Claude Code at a fraction of the cost by routing requests through LiteLLM to the GitHub Copilot Chat API.270k72
Codex PetGenerate a complete Codex Pet spritesheet and metadata from one reference image without needing an OpenAI key or Codex Pro.246k8How it compares
Use paper-context-resolver for one missing reproduction fact; use repo-intake-and-plan when the first step is choosing the smallest trustworthy target from repository docs.
FAQ
When should paper-context-resolver be used?
paper-context-resolver should be used only when README and repository files leave a narrow reproduction-critical gap. Rigor Paper Context fetches specific details like dataset splits or evaluation protocols from primary paper sources and records conflicts.
What is paper-context-resolver not designed to do?
paper-context-resolver is not designed for general paper summary, title-only lookup, environment setup, command execution, or replacing README guidance by default. It resolves one targeted reproduction detail at a time.
Is Paper Context Resolver safe to install?
skills.sh reports 2 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.