SkillHub GitHub

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 2 of 5 in the RigorPilot bundle · Before it: repo-intake-and-plan · After it: env-and-assets-bootstrap

TLDR

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 page · Source on GitHub · All skills from lllllllama/rigorpilot-skills

Installs
450,930 on skills.sh, Sep 21, 2026
Repo stars
492 lllllllama/rigorpilot-skills
First seen
Mar 30, 2026 on skills.sh
Weekly installs
48
-100% over 8 weeks · week to Sep 21
Weekly values
Week toInstalls
Aug 311,191
Aug 1032,245
Aug 1750,275
Aug 2441,240
Aug 3172
Sep 754
Sep 1458
Sep 2148
Category
category:science

Research reproduction, financial data, charts and diagrams.
Type
type:workflow

A multi-step process the agent follows: interview, debug, run a TDD loop, review.
Effect
effect:none

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
needs:none

Instructions only. Works in any agent that supports skills.
Publisher
by:community

Everyone else. Unverified vendor claims default to community.
Topics
ml-research

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.