AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Explore Run

skill-lllllllama-rigorpilot-skills-explore-run · by lllllllama

Rigor Improve / Rigor Explore run leaf skill for bounded exploratory evidence in deep learning research repositories. Use when the researcher explicitly authorizes exploratory runs such as 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/`. Do not use…

— No reviews yet
0 installs
9 views
0.0% view→install

Install

$ agentstack add skill-lllllllama-rigorpilot-skills-explore-run

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • ✓ Prompt-injection patterns
  • ✓ Secret / credential exfiltration
  • ✓ Dangerous shell & filesystem operations
  • ✓ Untrusted network calls
  • ✓ Known-malicious package signatures

What it can access

  • ✓ Network access No
  • ✓ Filesystem access No
  • ✓ Shell / process execution No
  • ✓ Environment & secrets No
  • ✓ Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-lllllllama-rigorpilot-skills-explore-run)

Reliability & compatibility

✓ Security review passed
0 installs to date
— no reviews yet
● 19d ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Explore Run? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

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 ../ai-research-reproduction/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, ../ai-research-reproduction/references/explore-variant-spec.md, ../ai-research-reproduction/references/deep-learning-experiment-principles.md, scripts/plan_variants.py, and scripts/write_outputs.py.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Versions

  • v0.1.0 Imported from the upstream source.