analyze-results
Skill8 starsChanged 8 months agoMITView on GitHub
Analyze YOLO training runs — compares to baseline/best, checks per-class regression, analyzes training dynamics and tune convergence, writes actionable recommendations.
11 other projects use a version of this.
Adopted by
Most recently taken up by
- AfonsoZhang/auto-research-systemtheir own version, first seen Nov 15, 2026
- Seraght/claude-skillstheir own version, first seen Oct 25, 2026
- yvesory/academic-research-suitetheir own version, first seen Oct 9, 2026
- talhaMah56/claude_skillstheir own version, first seen Sep 12, 2026
- EarthOnlinePlayer5732/my-skillstheir own version, first seen Aug 11, 2026
- wanshuiyin/Auto-claude-code-research-in-sleeptheir own version, first seen Jul 15, 2026
Used with
Projects with it also use experiment-plan.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
raja21068Skillexperiment-plan
Turn a refined research proposal or method idea into a detailed, claim-driven experiment roadmap. Use after `research-refine`, or when the user asks for a detailed experiment plan, ablation matrix, evaluation protocol, run order, compute budget, or paper-ready validation that supports the core problem, novelty, simplicity, and any LLM / VLM / Diffusion / RL-based contribution.
Also in 3 projects that use this
Other versions11 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 11
- wanshuiyin/Auto-claude-code-research-in-sleep★ 19ksame name
- zjunlp/Mechanist★ 75same name
- sunnnybala/Rstack★ 69same name
- Chanw-research/claude-code-paper-writing★ 42same name
- EarthOnlinePlayer5732/my-skills★ 17same name
- yvesory/academic-research-suite★ 9same name
- Yusong-Enceladus/claude-skills★ 8same name
- raja21068/AutoResearch★ 2same name
- AfonsoZhang/auto-research-system★ 1same name
- Seraght/claude-skills★ 0same name
1 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository15 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- active-learningSkill
- annotateSkill
- auto-experimentSkill
- benchmarkSkill
- compare-modelsSkill
- cvat-deploySkill
- cvat-pullSkill
- cvat-pushSkill
- explain-resultsSkill
- monitor-trainingSkill
- review-annotationsSkill
- review-datasetSkill
- setup-projectSkill
- training-loopSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 1 is distinctive, and 1 is very specific to this project.
0
Common
Most of the 10 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 53
Write experiments/analysis.md with findings and recommendations.
- Distinctive: line 60
Keep analysis concise — focus on what changed and what to try next, not restating all historical metrics.
“Common” is measured: kept by at least 6 in 10 of the 10 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Analyze Results
Single-pass analysis run after each experiment or on-demand via /analyze.
Data
Read:
- Latest experiment's report +
results.csvortune_results.csv - Current best metrics from
experiments/summary.mdjournal entries experiments/dataset_profile.yamltraining-plan.md(thresholds, goals, constraints)
Results.csv Lookup Order
experiments/exp_NNN_name/train/results.csvexperiments/exp_NNN_name/results.csv- Fall back to
metrics.yaml— note that training dynamics analysis is unavailable
For tune runs, also check:
experiments/exp_NNN_name/tune/tune_results.csv
Analysis
Comparison: Latest vs baseline AND current best (mAP50-95, per-class AP)
Per-class regression check: Flag any class exceeding training-plan.md threshold vs current best
Training dynamics (if results.csv available):
- Convergence speed: epochs to reach 90% of final mAP
- Overfitting onset: epoch where val loss diverges from train loss
- Loss plateau: epochs with <0.1% change in val loss
- LR effectiveness: correlation between LR schedule phase and metric improvement
Tune analysis (if tune_results.csv available):
- Tune convergence: are later iterations improving or stalled?
- Best params found vs defaults — which params moved the most?
- Top-N trial spread: how tight is the performance range?
Diminishing returns detection (when 3+ experiments show <0.5% change):
- Same-category stall (all augmentation, or all LR variations): that lever is exhausted, try a different category
- Cross-category stall (multiple lever types tried): model may be at ceiling for this dataset/architecture
- Recommendation differs per stall type — surface this explicitly
Recommendations: Ordered by expected impact. Each cites evidence from the analysis.
Output
Write experiments/analysis.md with findings and recommendations. Print top 3 findings + top 3 recommendations.
Findings also inform the journal entry's learning field and the next DIAGNOSE step in the reasoning loop.
Important
- The reasoning loop's DIAGNOSE step reads
analysis.mdfrom the previous experiment or last explicit/analyze. It does NOT read analysis of the experiment that just ran before it has been analyzed. - Keep analysis concise — focus on what changed and what to try next, not restating all historical metrics.
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
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.

