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.
Works with
--- name: repo-intake-and-plan description: 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. license: MIT --- # repo-intake-and-plan Use this as the Rigor Intake helper. The installed slug remains `repo-intake-and-plan` for compatibility. ## When to apply - At the beginning of README-first reproduction work. - When the main skill needs a fast map of repo structure and documented commands. - When inference, evaluation, and training candidates must be classified conservatively. - When the user explicitly wants to inspect the repo first and not run anything yet. ## When not to apply - When execution has already started and the task is now about running commands or writing outputs. - When the target is not a repository-backed reproduction task. - When the user only wants paper interpretation without repo inspection. - When the user already has a selected documented command and only needs setup or execution. ## Clear boundaries - This skill scans and plans. - This skill is helper-tier and should usually be orchestrator-invoked. - It does not install environments. - It does not prepare large assets. - It does not execute substantive reproduction commands. - It does not decide high-risk patching. ## Input expectations - Target repository path. - Access to README and common project files if present. - Optional user hints about desired priority, such as inference-first. ## Output expectations - concise repo structure summary - documented command inventory - inferred candidate categories: inference, evaluation, training, other - minimum trustworthy reproduction recommendation - notable ambiguity or risk list ## Notes Use `references/repo-scan-rules.md` and helper scripts under `scripts/`.
More Writing & Documentation skills
paper-context-resolver
lllllllama/rigorpilot-skills
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.
minimal-run-and-audit
lllllllama/rigorpilot-skills
Rigor Run skill for README-first deep learning repo reproduction. Use when the task is specifically to capture or normalize evidence from the selected smoke test or documented inference or evaluation command and write standardized `repro_outputs/` files, including patch notes when repository files changed. Do not use for training execution, initial repo intake, generic environment setup, paper lookup, target selection, hidden scientific-meaning changes, or end-to-end orchestration by itself.
env-and-assets-bootstrap
lllllllama/rigorpilot-skills
Rigor Setup skill for README-first deep learning repo reproduction. Use when the task is specifically to prepare a conservative conda-first environment, checkpoint and dataset path assumptions, cache location hints, and setup notes before any run on a README-documented repository. Do not use for repo scanning, full orchestration, paper interpretation, final run reporting, or generic environment setup that is not tied to a specific reproduction target.
