env-and-assets-bootstrap
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.
Works with
--- name: env-and-assets-bootstrap description: 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. license: MIT --- # env-and-assets-bootstrap Use this as the Rigor Setup skill. The installed slug remains `env-and-assets-bootstrap` for compatibility. Use the shared operating principles in `../../references/agent-operating-principles.md`; this skill should keep setup planning conservative while leaving environment-specific judgment to the model. ## When to apply - After repo intake identifies a credible reproduction target. - When environment creation or asset path preparation is needed before running commands. - When the repo depends on checkpoints, datasets, or cache directories. - When the user explicitly wants setup help before any run attempt. ## When not to apply - When the repository already ships a ready-to-run environment that does not need translation. - When the task is only to scan and plan. - When the task is only to report results from commands that already ran. - When the request is a generic conda or package-management question outside repo reproduction. ## Clear boundaries - This skill prepares environment and asset assumptions. - It does not own target selection. - It does not own final reporting. - It does not perform paper lookup except by forwarding gaps to the optional paper resolver. ## Input expectations - target repo path - selected reproduction goal - relevant README setup steps - any known OS or package constraints ## Output expectations - conservative environment setup notes - candidate conda commands - asset path plan - checkpoint and dataset source hints - unresolved dependency or asset risks ## Notes Use `references/env-policy.md`, `references/assets-policy.md`, `scripts/bootstrap_env.py`, `scripts/plan_setup.py`, and `scripts/prepare_assets.py`. Use `scripts/bootstrap_env.sh` only as a POSIX wrapper around the Python bootstrapper when a shell entrypoint is more convenient.
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.
repo-intake-and-plan
lllllllama/rigorpilot-skills
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.
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.
