agentleFS
MacroMan5MacroMan5/autotrain-yolo/.claude/skills/auto-experiment/SKILL.md

auto-experiment

Skill8 starsChanged 8 months agoMITView on GitHub

Run autonomous YOLO training experiments — reads training-plan.md, assesses bottlenecks, acts strategically, and delegates HP optimization to model.tune().

2 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

12 rules. About 0 are common, 6 are distinctive, and 6 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 6

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    If not found, check for program.md (deprecated name) and warn user to rename it

    line 16
  2. Distinctive:

    Read in order before every session:

    line 23
  3. Very specific:

    If no baseline exists: yolo-experiment baseline --budget 5 --patience 3 After baseline, update training-plan.md Current Performance section.

    line 32
  4. Distinctive:

    After baseline, update training-plan.md Current Performance section.

    line 33
  5. Very specific:

    Write a session marker in summary.md:

    line 37
  6. Distinctive:

    If a session marker exists with today's date and no end marker, this is a resumed session — count existing entries toward budget.

    line 41
  7. Distinctive:

    Read dataset profile, per-class AP, training dynamics from last run.

    line 49
  8. Distinctive:

    Write a hypothesis: "I expect X because Y, so I'll do Z"

    line 56
  9. Very specific:

    Read experiment report from experiments/exp_NNN_*/report.md

    line 90
  10. Very specific:

    Write session end marker: ## Session End — N experiments run

    line 97
  11. Very specific:

    Write experiments/session_YYYY-MM-DD.md with before/after + key learnings

    line 98
  12. Distinctive:

    Update training-plan.md Model Lineage with current best path, metrics, source experiment

    line 99

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Auto-Experiment — Strategic Decision Loop

Autonomous experimentation via hypothesis-driven reasoning. The agent makes strategic decisions (architecture, data, augmentation strategy). HP optimization is delegated to model.tune() — don't compete with it.

Pre-Flight

  1. yolo-project.yaml exists — run /setup if not
  2. training-plan.md exists with goals + boundaries — run /setup if not
    • If not found, check for program.md (deprecated name) and warn user to rename it
  3. Dataset is valid — yolo-validate
  4. GPU available — python -c "import torch; print(torch.cuda.is_available())"
  5. Read experiments/dataset_profile.yaml — run /review-dataset if missing

Context Loading

Read in order before every session:

  1. yolo-project.yaml — classes, dataset path, model defaults
  2. training-plan.md — goals, hard constraints, soft preferences, allowed actions, domain knowledge
  3. experiments/summary.md — all prior journal entries (if exists)
  4. experiments/dataset_profile.yaml — dataset characteristics for architecture reasoning
  5. experiments/analysis.md — latest analysis (if exists)

Baseline

If no baseline exists: yolo-experiment baseline --budget 5 --patience 3 After baseline, update training-plan.md Current Performance section.

Session Start

Write a session marker in summary.md:

## Session YYYY-MM-DD HH:MM — Budget: N experiments

If a session marker exists with today's date and no end marker, this is a resumed session — count existing entries toward budget.

Reasoning Loop

For each decision, follow all 3 steps in order:

1. ASSESS — What's the bottleneck?

Read dataset profile, per-class AP, training dynamics from last run.

Classify the bottleneck:

  • Data quality → active learning (/review-dataset, /cvat-push, /autolabel)
  • Architecture mismatch → swap config (yolo-experiment run --override "model=configs/architectures/...")
  • HP not optimized → yolo-experiment tune --space <preset>

Write a hypothesis: "I expect X because Y, so I'll do Z"

Cold-start (first post-baseline): Focus on dataset profile characteristics, per-class AP spread, class imbalance. Training dynamics analysis starts from experiment 2 onward.

2. ACT — Do the right thing

Architecture change:

yolo-experiment run --override "model=configs/architectures/yolo11-p2.yaml" --budget <epochs>

Requires dataset profile justification — cite ≥2 numbers. See resources/architecture-guide.md.

HP optimization (delegate to model.tune):

# Use presets when diagnosis maps cleanly:
yolo-experiment tune --space lr --iterations 20 --epochs 10
yolo-experiment tune --space augmentation --iterations 20 --epochs 10
yolo-experiment tune --space loss --iterations 15 --epochs 10
yolo-experiment tune --space optimizer --iterations 20 --epochs 10

# Use custom when diagnosis is specific:
yolo-experiment tune --space "lr0=0.001:0.01 momentum=0.85:0.98" --iterations 20 --epochs 10

Strategic experiment (resolution, freeze depth, augmentation strategy):

yolo-experiment run --override "<param>=<value>" --budget <epochs>

Data action (when data quality is the bottleneck): /review-dataset, /cvat-push, /autolabel

3. LOG — Record what happened

  • Read experiment report from experiments/exp_NNN_*/report.md
  • Append simplified journal entry to summary.md matching schema in resources/journal-schema.yaml
  • Every field marked REQUIRED must be present.
  • Decide: continue this direction, try different lever, or stop

Session End

  1. Write session end marker: ## Session End — N experiments run
  2. Write experiments/session_YYYY-MM-DD.md with before/after + key learnings
  3. Update training-plan.md Model Lineage with current best path, metrics, source experiment

Guardrails

  • Checkpoint backup — hook handles automatically before every run/tune
  • Immutable data — NEVER modify original dataset files
  • Architecture change gate — 3+ experiments on current architecture with <0.5% improvement before switching. Exception: >50% small objects with no P2 head (see resources/architecture-guide.md)
  • Architecture justification — must cite ≥2 dataset profile numbers in journal
  • Log everything — write journal entry even if experiment fails

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.