env-and-assets-bootstrap
installsforks
How to install env-and-assets-bootstrap?
lllllllama/rigorpilot-skills/env-and-assets-bootstrap
$npx -y skills add lllllllama/RigorPilot-Skills --skill env-and-assets-bootstrapRigor 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
SKILL.md
| 1 | # env-and-assets-bootstrap |
| 2 | |
| 3 | Use this as the Rigor Setup skill. The installed slug remains |
| 4 | `env-and-assets-bootstrap` for compatibility. |
| 5 | |
| 6 | Use the shared operating principles in |
| 7 | `../../references/agent-operating-principles.md`; this skill should keep setup |
| 8 | planning conservative while leaving environment-specific judgment to the model. |
| 9 | |
| 10 | ## When to apply |
| 11 | |
| 12 | - After repo intake identifies a credible reproduction target. |
| 13 | - When environment creation or asset path preparation is needed before running commands. |
| 14 | - When the repo depends on checkpoints, datasets, or cache directories. |
| 15 | - When the user explicitly wants setup help before any run attempt. |
| 16 | |
| 17 | ## When not to apply |
| 18 | |
| 19 | - When the repository already ships a ready-to-run environment that does not need translation. |
| 20 | - When the task is only to scan and plan. |
| 21 | - When the task is only to report results from commands that already ran. |
| 22 | - When the request is a generic conda or package-management question outside repo reproduction. |
| 23 | |
| 24 | ## Clear boundaries |
| 25 | |
| 26 | - This skill prepares environment and asset assumptions. |
| 27 | - It does not own target selection. |
| 28 | - It does not own final reporting. |
| 29 | - It does not perform paper lookup except by forwarding gaps to the optional paper resolver. |
| 30 | |
| 31 | ## Input expectations |
| 32 | |
| 33 | - target repo path |
| 34 | - selected reproduction goal |
| 35 | - relevant README setup steps |
| 36 | - any known OS or package constraints |
| 37 | |
| 38 | ## Output expectations |
| 39 | |
| 40 | - conservative environment setup notes |
| 41 | - candidate conda commands |
| 42 | - asset path plan |
| 43 | - checkpoint and dataset source hints |
| 44 | - unresolved dependency or asset risks |
| 45 | |
| 46 | ## Notes |
| 47 | |
| 48 | Use `references/env-policy.md`, `references/assets-policy.md`, `scripts/bootstrap_env.py`, `scripts/plan_setup.py`, and `scripts/prepare_assets.py`. |
| 49 | Use `scripts/bootstrap_env.sh` only as a POSIX wrapper around the Python bootstrapper when a shell entrypoint is more convenient. |
People who liked this also viewed
6 picksType
- microsoft-foundryDeploy, evaluate, fine-tune, and manage Foundry agents end-to-end with azd: hosted agent scaffold/run/deploy, prompt agent create, batch eval, continuous eval, prompt optimizer, Agent Optimizer scaffoSkillsJul 2026
- azure-deployExecute Azure deployments for ALREADY-PREPARED applications that have existing .azure/deployment-plan.md and infrastructure files. DO NOT use this skill when the user asks to CREATE a new application SkillsJul 2026
- azure-preparePrepare azd-based Azure projects for deployment: generates azure.yaml, infrastructure (Bicep/Terraform), and Dockerfiles for the Azure Developer CLI (azd) workflow. USE ONLY when the user explicitly wSkillsJul 2026
- azure-validate--- name: azure-validate description: "Pre-deployment validation for Azure readiness. Run deep checks on configuration, infrastructure (Bicep or Terraform), RBAC role assignments, managed identity pSkillsJul 2026
- azure-aigatewayConfigure Azure API Management as an AI Gateway for AI models, MCP tools, and agents. WHEN: semantic caching, token limit, content safety, load balancing, AI model governance, MCP rate limiting, jailbSkillsJul 2026
- azure-hosted-copilot-sdkOfficial agent plugin providing skills and MCP server configurations for Azure scenarios.SkillsJul 2026
