Explore Run

explore-run

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 for end-to-end exploration orchestration on top of `current_research`, trusted baseline execution, conservative training verification, default routing, verified SOTA claims, or implicit experimentation.

lllllllama/rigorpilot-skills·310.5Kinstalls497stars

SKILL.md

Full skill instructions

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.

Install skill

Copy and run in your terminal

npx -y skills add https://github.com/lllllllama/rigorpilot-skills --skill explore-run

View on GitHub

explore-run

paper-context-resolver
Rigor Paper Context helper for README-first deep learning repo reproduction. Use only when the README and repository files leave a narrow reproduction-critical gap and the task is to resolve a specific paper detail such as dataset split, preprocessing, evaluation protocol, checkpoint mapping, or runtime assumption from primary paper sources while recording conflicts. Do not use for general paper summary, repo scanning, environment setup, command execution, title-only paper lookup, or replacing README guidance by default.
451K installs
repo-intake-and-plan
Rigor Intake helper for README-first deep learning repo reproduction. Use when the task is specifically to scan a repository, read the README and common project files, extract documented commands, classify inference, evaluation, and training candidates, and return the smallest trustworthy reproduction plan to the main orchestrator. Do not use for environment setup, asset download, command execution, final reporting, paper lookup, or end-to-end orchestration.
450.2K installs
minimal-run-and-audit
Rigor Run skill for README-first deep learning repo reproduction. Use when the task is specifically to capture or normalize evidence from the selected smoke test or documented inference or evaluation command and write standardized `repro_outputs/` files, including patch notes when repository files changed. Do not use for training execution, initial repo intake, generic environment setup, paper lookup, target selection, hidden scientific-meaning changes, or end-to-end orchestration by itself.
450.2K installs
env-and-assets-bootstrap
Rigor 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. Do not use for repo scanning, full orchestration, paper interpretation, final run reporting, or generic environment setup that is not tied to a specific reproduction target.
450.1K installs

More skills from lllllllama

lllllllama/rigorpilot-skills

ai-research-explore

Rigor Explore compatible skill slug for meaningful and potentially novel deep learning research candidates. Use when the researcher has chosen the task family, dataset, benchmark, evaluation method, provided SOTA references, and wants candidate-only exploration on top of `current_research` with auditable repo understanding, idea gating, fair comparison, and governed experiments written to `explore_outputs/`. Do not use for README-first trusted reproduction, open-ended direction finding, narrow code-only or run-only exploration, passive repo analysis, verified novelty claims, or implicit experimentation.

497 311.4K

View

lllllllama/rigorpilot-skills

analyze-project

Rigor Analyze / Rigor Audit read-only skill for deep learning research repositories. Use when the user wants to read and understand a repository, inspect model structure and training or inference entrypoints, review configs and insertion points, or flag suspicious implementation patterns without modifying code or running heavy jobs. Do not use for active command execution, broad refactoring, speculative code adaptation, or automatic bug fixing.

497 311.2K

View

lllllllama/rigorpilot-skills

explore-code

Rigor Improve implementation leaf skill for auditable candidate implementation in deep learning research repositories. Use when the researcher explicitly authorizes exploratory work on an isolated branch or worktree to transplant modules, adapt a backbone, add LoRA or adapter layers, replace a head, or stitch together meaningful low-risk migration ideas with rollback-aware records in `explore_outputs/`. Do not use for end-to-end exploration orchestration on top of `current_research`, trusted baseline reproduction, conservative debugging, environment setup, verified contribution claims, or default repository analysis.

497 310.7K

View

lllllllama/rigorpilot-skills

safe-debug

Rigor Debug / Rigor Audit skill for deep learning research work. Use when the user pastes a traceback, terminal error, CUDA OOM, checkpoint load failure, shape mismatch, NaN loss symptom, or training failure and wants conservative diagnosis before any patching, with debug fixes clearly separated from research contributions. Do not use for broad refactoring, speculative adaptation, automatic exploratory patching, or general repository familiarization.

497 310.7K

View

lllllllama/rigorpilot-skills

run-train

Rigor Train skill for deep learning research repositories. Use when a documented or selected training command should be run conservatively for startup verification, short-run verification, full kickoff, or resume, with command, config, seed, log, checkpoint, status, and metric evidence written to standardized `train_outputs/`. Do not use for environment setup, exploratory sweeps, speculative idea implementation, or end-to-end orchestration.

497 310.5K

View

lllllllama/ai-paper-reproduction-skill