paper-context-resolver

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.

Aller à l'installation

Dépôt: lllllllama/RigorPilot-Skills
Dernière activité de la source: 18 mai 2026 à 03:58
Langue détectée de SKILL.md: anglais
Étoiles: 477
Forks: 16

Options d'installation

Le prompt qui vérifie d'abord la source est sélectionné par défaut. Vous pouvez passer à une commande directe ou télécharger une copie locale.

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Une commande directe contourne le prompt de vérification. Examinez la source avant de l'exécuter.

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

La commande reste sur une seule ligne. Faites défiler horizontalement pour la vérifier avant de la copier.

Vous préférez une copie locale ? Téléchargez les fichiers actuellement disponibles dans SkillsMP.

Vérifiez les fichiers source

Lisez SKILL.md et les fichiers associés affichés par SkillsMP avant de décider de l'installer.

Explorateur de fichiers

3 fichiers

SKILL.md

Instructions source · Aperçu en lecture seule

Retour à la recherche Retour à l’installation

ai-research-explore

Rigor Explore compatible skill slug for meaningful and potentially novel deep learning research candidates. Use when the researcher has chosen the task family, dataset, benchmark, evaluation method, provided SOTA references, and wants candidate-only exploration on top of `current_research` with auditable repo understanding, idea gating, fair comparison, and governed experiments written to `explore_outputs/`. Do not use for README-first trusted reproduction, open-ended direction finding, narrow code-only or run-only exploration, passive repo analysis, verified novelty claims, or implicit experimentation.

2026-07-26

ai-research-reproduction

Rigor Reproduce compatible skill slug for README-first deep learning repository reproduction. Use when the user wants an end-to-end, minimal-trustworthy flow that reads the repository first, selects the smallest documented inference or evaluation target, coordinates intake, setup, trusted execution, optional trusted training, optional repository analysis, and optional paper-gap resolution, enforces conservative patch rules, records evidence assumptions deviations and human decision points, and writes the standardized `repro_outputs/` bundle. Do not use for paper summary, generic environment setup, isolated repo scanning, standalone command execution, silent protocol changes, score chasing, or broad research assistance outside repository-grounded reproduction.

2026-07-26

repo-intake-and-plan

Rigor Intake helper for README-first deep learning repo reproduction. Use when the task is specifically to scan a repository, read the README and common project files, extract documented commands, classify inference, evaluation, and training candidates, and return the smallest trustworthy reproduction plan to the main orchestrator. Do not use for environment setup, asset download, command execution, final reporting, paper lookup, or end-to-end orchestration.

2026-07-26

Tout voir dans ce dépôt

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.

name

paper-context-resolver

description