Explore Run (RigorPilot)
Bounded exploratory runs — small-subset validation, short-cycle probes, batch sweeps, idle-GPU search — ranked by cost/success-rate/expected-gain with fair-comparison caveats
- What
- Bounded exploratory runs — small-subset validation, short-cycle probes, batch sweeps, idle-GPU search — ranked by cost/success-rate/expected-gain with fair-comparison caveats
- Cost
- Free
- Needs
- a deep-learning research setup with compute (GPU/accelerator time) for the runs — this skill plans and ranks exploratory runs; actual execution hands off to minimal-run-and-audit or run-train.
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — the RigorPilot "Rigor Improve / Rigor Explore" run leaf skill for bounded exploratory evidence in deep-learning research repositories. It plans exploratory execution only when the researcher explicitly authorizes it: small-subset validation, short-cycle guess-and-check, batch sweeps, idle-GPU search, or quick transfer-learning trials — with fair-comparison caveats and no-overclaim summaries in `explore_outputs/`. Candidate selection before execution weighs three factors — `cost`, `success_rate`, `expected_gain` — with conservative default weights (rebalanced only if the researcher provides `selection_weights`), budget pruning via `max_variants` and `max_short_cycle_runs`, and variant axes expressed through `variant_axes`, `subset_sizes` and `short_run_steps`; downstream ranking switches to real execution evidence, never stays purely heuristic. The skill owns planning and summary only — actual command execution hands off to `minimal-run-and-audit` or `run-train` — and it keeps experiment state isolated from the trusted baseline, preferring small-subset and short-cycle checks before heavier runs and labeling results as bounded evidence with explicit notes on when a comparison isn't directly fair. By @lllllllama, listed here with credit to its creator. Honest caveats: it ranks candidates, it doesn't certify success — ranking is heuristic until real execution evidence exists; real runs need real compute (GPU time, budgets) that you manage yourself; use `ai-research-explore` for end-to-end orchestration and `run-train` for trusted training execution. Skill Harbor never reviews the code, review it yourself before use.
Version:
Quick answer
Explore Run (RigorPilot) is a free Muse skill that runs bounded exploratory runs: small-subset validation, short-cycle probes, batch sweeps and idle-GPU search, ranked by cost, success rate and expected gain, with fair-comparison caveats, so exploration stays cheap, comparable and honest about what it has not proven.
Install
Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox · Nov 11, 2026📌 Pinned version: commit fb3ccdfStep 0 — before installing anything: read this install prompt, summarize in a few lines what this build does and what installing it involves, then ask me to confirm before you proceed. Prerequisites: a deep-learning research setup with compute (GPU/accelerator time) for the runs — this skill plans and ranks exploratory runs; actual execution hands off to minimal-run-and-audit or run-train. Install "Explore Run (RigorPilot)" for me. The RigorPilot run leaf skill: bounded exploratory runs (small-subset validation, short-cycle probes, batch sweeps, idle-GPU search) ranked by cost/success-rate/expected-gain, with fair-comparison caveats and no-overclaim summaries in explore_outputs/. Repository: https://raw.githubusercontent.com/lllllllama/rigorpilot-skills/fb3ccdf5aa64b1fa5b1d0463e666a8bc8bc26e01/skills/explore-run/SKILL.md Pinned version: install the code at commit fb3ccdf5aa64b1fa5b1d0463e666a8bc8bc26e01 exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder 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-explore-run". 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.
Saved to your recent installs. Find it anytime on /connect.
🔒 Security, provenance and what this touches
The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Verification certificate
Dated facts about what was checked for this listing, and how. This is not a safety certification.
- Pinned version
- fb3ccdf · 2026-10-13
- Sandbox install test
- Install ran in our test sandbox · Nov 11, 2026 · Observed during the install test: files.pythonhosted.org, pypi.org
- Creator identity
- Not verified
- Fingerprint watch
- Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
- Install prompt analysis
- 2026-10-13 : No commands, network calls, packages, file writes or API keys detected.
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
Questions
How do I install a skill?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill 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 skill before installing it.