env-and-assets-bootstrap — Claude Code skill: prep a repo environment
Prepares environment and checkpoint/dataset paths before the first run of a README-documented repo.
npx skills add lllllllama/RigorPilot-Skills --skill env-and-assets-bootstrap -a claude-codeWhat env-and-assets-bootstrap does
The skill kicks in once a repo is picked as the reproduction target and no environment exists for it yet. It drafts a conservative plan: conda commands, assumptions about checkpoint and dataset paths, cache location hints, and setup notes. All of that happens before you run anything from the README.
Inside are two policy references (references/env-policy.md, references/assets-policy.md) and three Python scripts: scripts/bootstrap_env.py, scripts/plan_setup.py, scripts/prepare_assets.py. There is also scripts/bootstrap_env.sh, though it is only a POSIX wrapper around the Python bootstrapper when a shell entrypoint suits you better. Input it expects: the target repo path, the chosen reproduction goal, relevant README setup steps, and any known OS or package constraints.
The boundaries are tight. Target selection is not its job, and neither is final reporting. It does not scan repos or read papers — gaps get forwarded to an optional paper resolver. If the repo already ships a ready-to-run environment that needs no translation, the skill adds nothing. Same for generic conda questions outside a specific reproduction target.
What it helps with
- draft an environment plan before the first run of a repo
- pin down checkpoint and dataset paths
- pick conda commands that match the README
- flag unresolved dependency and asset risks
- point out where cache directories live
Example prompts for the agent
- prepare the environment and asset paths for this repo from its README
- draft a conservative conda setup plan before we run anything
- check which checkpoints and datasets are needed and where to find them
How to install env-and-assets-bootstrap
1Skills CLI (Vercel)
npx skills add lllllllama/RigorPilot-Skills --skill env-and-assets-bootstrap -a claude-code2Manually: put the files in place
~/.claude/skills/env-and-assets-bootstrap/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/env-and-assets-bootstrap/
1Skills CLI (Vercel)
npx skills add lllllllama/RigorPilot-Skills --skill env-and-assets-bootstrap -a codex2Manually: put the files in place
.agents/skills/env-and-assets-bootstrap/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add lllllllama/RigorPilot-Skills --skill env-and-assets-bootstrap -a cursor2Manually: put the files in place
.cursor/skills/env-and-assets-bootstrap/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install lllllllama/RigorPilot-Skills env-and-assets-bootstrap2Manually: put the files in place
.github/skills/env-and-assets-bootstrap/SKILL.md1Skills CLI (Vercel)
npx skills add lllllllama/RigorPilot-Skills --skill env-and-assets-bootstrap -a gemini-cli2Platform CLI
gemini skills install https://github.com/lllllllama/RigorPilot-Skills --path skills/env-and-assets-bootstrapManually: put the files in place
.devin/skills/env-and-assets-bootstrap/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add lllllllama/RigorPilot-Skills --skill env-and-assets-bootstrap -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
From the same set9
The whole set →Similar
Questions about env-and-assets-bootstrap
How do I install env-and-assets-bootstrap in Claude?
Run npx skills add lllllllama/RigorPilot-Skills --skill env-and-assets-bootstrap -a claude-code. The skill file then sits at ~/.claude/skills/env-and-assets-bootstrap/SKILL.md.
What does env-and-assets-bootstrap do?
It produces conservative environment notes, candidate conda commands, an asset path plan, and hints on where checkpoints and datasets come from. It works before any README command runs.
What is outside its scope?
It does not pick the reproduction target, scan the repo, interpret the paper, or write the final report. Paper gaps go to an optional paper resolver.
Source text
SKILL.md · MIT
--- 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. --- # 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 `../ai-research-reproduction/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.
© lllllllama · MIT · lllllllama/RigorPilot-Skills