env-and-assets-bootstrap

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

references/env-policy.md

references/assets-policy.md

scripts/bootstrap_env.sh

scripts/prepare_assets.py