Paper Context Resolver

Published by lllllllama in rigorpilot-skills

Review recommended451k installs

What this skill does

It helps an agent resolve a specific deep learning reproduction question by checking primary paper sources against README and repository evidence. It returns relevant findings, notes conflicts, and distinguishes direct evidence from inference. Best for Researchers and engineers reproducing a deep learning repository with a specific unresolved implementation detail.

Add Paper Context Resolver to your agent

Review the source and files first. When you are ready, copy the prompt instruction or use the CLI command supported by your environment.

Install with a prompt

Paste this into a compatible coding agent:

add this skill "paper-context-resolver" from https://github.com/lllllllama/rigorpilot-skills

Install with the CLI

Run this command in a controlled environment after reviewing the repository:

npx skills add https://github.com/lllllllama/rigorpilot-skills --skill paper-context-resolver

Skill instructions

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.

Files included

  • agents/openai.yaml
  • references/paper-assisted-reproduction.md
  • SKILL.md

More skills

Paper Context Resolver: Install, Source and Security | FunnelSlayer