Paper Context Resolver

by lllllllamafb3ccdf5aa64No licenseListed Oct 8, 2026Updated Oct 8, 2026

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.

Instructions onlyResearch & Analysis
AI-generated overview

Resolves narrow reproduction-critical gaps in deep learning repos by consulting primary paper sources and recording conflicts.

What it does
This helper skill answers a specific reproduction question — such as dataset split, preprocessing, evaluation protocol, checkpoint mapping, or runtime assumptions — when the README and repository files leave a critical gap. It narrows the source list, returns only reproduction-relevant findings, and notes conflicts between the README and the paper. It distinguishes direct evidence from inference and does not summarize the whole paper.
When to use it
Use it when a concrete reproduction question exists and the README or repo files do not resolve it. It is meant as an optional, orchestrator-invoked supplement to README-first reproduction, not a replacement. Do not use it for general paper summaries, repo scanning, environment setup, command execution, or title-only paper lookup.
Requirements
Instructions only; no scripts are shipped. It expects target repo metadata, a reproduction-critical question, existing README or repo evidence, and any known paper links, and it references a bundled guidance document. Access to primary paper sources is implied.

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.

Source and attribution

Source:lllllllama/rigorpilot-skillsinskills/paper-context-resolverat commitfb3ccdf

License: No license

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal