Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
lllllllama avatar

Explore Run

  • 176k installs
  • 512 repo stars
  • Updated July 26, 2026
  • lllllllama/rigorpilot-skills

explore-run is a Claude Code skill for planning, ranking, and executing bounded exploratory deep learning runs with evidence-based candidate selection.

About

An exploratory execution skill for deep learning research. Use it when you have explicit authorization for exploration and want to run small-subset validation, sweeps, or quick trials with fair-comparison caveats.

  • Plans and ranks exploratory runs with cost, success rate, and expected gain
  • Executes small-subset validation, short-cycle trials, or batch sweeps
  • Labels results as bounded evidence with no-overclaim summaries

Explore Run by the numbers

  • 175,906 all-time installs (skills.sh)
  • +25,326 installs in the week ending Jul 28, 2026 (Skillselion tracking)
  • Ranked #4 of 2,066 Data Science & ML skills by installs in the Skillselion catalog
  • Security screen: MEDIUM risk (skills.sh audit)
  • Data as of Jul 28, 2026 (Skillselion catalog sync)
At a glance

explore-run capabilities & compatibility

Capabilities
variant planning · candidate ranking · experiment execution · evidence collection
Use cases
research · testing
npx skills add https://github.com/lllllllama/rigorpilot-skills --skill explore-run

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs176k
repo stars512
Security audit2 / 3 scanners passed
Last updatedJuly 26, 2026
Repositorylllllllama/rigorpilot-skills

What it does

Plan and execute bounded exploratory deep learning runs with candidate ranking.

Who is it for?

Small-subset validation,Short-cycle training probes,Batch sweeps,Idle-GPU search

Skip if: Trusted training execution,Conservative verification,Repository setup,Implicit experimentation

When should I use this skill?

The researcher explicitly authorizes exploratory runs for small-subset validation, short-cycle probes, batch sweeps, or quick transfer-learning trials.

What you get

explore_outputs/ bundle with TOP_RUNS.md ranking candidates by real evidence with cost, success rate, and expected gain.

  • explore_outputs/TOP_RUNS.md
  • explore_outputs/SCIENTIFIC_CHANGELOG.md
  • explore_outputs/COMPARABILITY_REPORT.md

By the numbers

  • Three ranking factors: cost, success_rate, expected_gain; pre- and post-execution scoring

Files

SKILL.mdMarkdownGitHub ↗

explore-run

Use this as the Rigor Improve / Rigor Explore run leaf skill. The installed slug remains explore-run for compatibility.

Use the shared operating principles in ../../references/agent-operating-principles.md; this skill should guide candidate run planning while preserving model judgment about the active repo.

When to apply

  • When the researcher explicitly authorizes exploratory runs.
  • When the task is a small-subset validation, short-cycle training probe, batch sweep, idle-GPU search, or quick transfer-learning trial.
  • When the output should rank candidate runs rather than certify trusted success.

When not to apply

  • When the user wants trusted training execution or conservative verification.
  • When there is no explicit exploratory authorization.
  • When the task is repository setup, intake, or debugging.

Clear boundaries

  • This skill owns exploratory execution planning and summary only.
  • Use ai-research-explore instead when the task spans both current_research coordination and exploratory code changes.
  • It may hand off actual command execution to minimal-run-and-audit or run-train.
  • It should keep experiment state isolated from the trusted baseline.
  • It should prefer small-subset and short-cycle checks before heavier exploratory runs.
  • It should label run results as bounded evidence and explain when a comparison

is not directly fair.

Ranking Semantics

  • Pre-execution candidate selection uses three factors: cost, success_rate, and expected_gain.
  • Default weights should stay conservative unless the researcher explicitly provides selection_weights.
  • Budget pruning still applies after scoring through max_variants and max_short_cycle_runs.
  • If runs are executed later, downstream ranking should switch to real execution evidence, not stay purely heuristic.

Variant Spec Hints

  • Use variant_axes to define the candidate dimension grid.
  • Use subset_sizes and short_run_steps to express exploratory run scale.
  • Use selection_weights to rebalance cost, success_rate, and expected_gain.
  • Use primary_metric and metric_goal so downstream ranking can order executed candidates consistently.

Output expectations

  • explore_outputs/CHANGESET.md
  • explore_outputs/SCIENTIFIC_CHANGELOG.md
  • explore_outputs/COMPARABILITY_REPORT.md
  • explore_outputs/TOP_RUNS.md
  • explore_outputs/status.json

Notes

Use references/execution-policy.md, ../../references/explore-variant-spec.md, ../../references/deep-learning-experiment-principles.md, scripts/plan_variants.py, and scripts/write_outputs.py.

Related skills

Forks & variants (3)

Explore Run has 3 known copies in the catalog totaling 431 installs. They canonicalize to this original listing.

How it compares

Pick explore-run over minimal-run-and-audit when comparing multiple agent variants on an experiment branch rather than producing a single auditable verification report.

FAQ

How are candidates ranked?

Pre-execution: by cost, success_rate, expected_gain. Post-execution: by real command status, observed metrics, and artifacts.

Are results claimed as verified success?

No. Results are labeled as bounded evidence with explanations of when comparisons are not directly fair.

Is Explore Run safe to install?

skills.sh reports 2 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.