Run Train (RigorPilot)
Conservative execution of selected training commands — startup/short-run verification, kickoff, resume — with command/config/seed/log/checkpoint evidence in train_outputs/
- What
- Conservative execution of selected training commands — startup/short-run verification, kickoff, resume — with command/config/seed/log/checkpoint evidence in train_outputs/
- Cost
- Free
- Needs
- a deep-learning training setup with compute (GPU/accelerator time) and a pre-selected, runnable training command — the skill executes conservatively; it doesn't pick your training strategy.
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — the RigorPilot "Rigor Train" skill: conservative execution of a selected training command for deep-learning research repositories. It applies when the training command has already been selected and should be run conservatively — startup verification, short-run verification, full kickoff, or resume — with command, config, seed, log, checkpoint, status and metric evidence written to standardized `train_outputs/` (`SUMMARY.md`, `COMMANDS.md`, `LOG.md`, `SCIENTIFIC_CHANGELOG.md`, `COMPARABILITY_REPORT.md`, `status.json`). The boundaries are clear: it executes a selected training command and normalizes the resulting evidence; it does not choose the research goal on its own, does not own exploratory branching or speculative code adaptation, and records partial, blocked, resumed and kicked-off states explicitly while preserving reproducibility context (configs, seeds, checkpoints, logs, metrics, runtime assumptions). Not for environment setup, asset download, inference-only or evaluation-only execution, speculative exploration, multi-variant sweeps, or autonomous idea implementation. By @lllllllama, listed here with credit to its creator. Honest caveats: it burns real GPU time — budgets, timeouts and cost awareness are entirely your responsibility; the command must be selected before the skill runs, it won't pick your training strategy for you; checkpoint and log evidence is only as good as the repo's own instrumentation. Skill Harbor never reviews the code, review it yourself before use.
Version:
Install
Prerequisites: a deep-learning training setup with compute (GPU/accelerator time) and a pre-selected, runnable training command — the skill executes conservatively; it doesn't pick your training strategy. Install "Run Train (RigorPilot)" for me. The RigorPilot training skill: conservative execution of a selected training command (startup verification, short-run verification, kickoff, resume) with standardized command/config/seed/log/checkpoint evidence in train_outputs/. Repository: https://github.com/lllllllama/rigorpilot-skills/blob/main/skills/run-train/SKILL.md 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "rigorpilot-run-train". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself. GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.