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

Analyze Results

skill-macroman5-autotrain-yolo-analyze-results · by MacroMan5

Analyze YOLO training runs — compares to baseline/best, checks per-class regression, analyzes training dynamics and tune convergence, writes actionable recommendations.

No reviews yet
0 installs
8 views
0.0% view→install

Install

$ agentstack add skill-macroman5-autotrain-yolo-analyze-results

✓ 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-macroman5-autotrain-yolo-analyze-results)

Reliability & compatibility

Security review passed
0 installs to date
no reviews yet
4mo 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 Analyze Results? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Analyze Results

Single-pass analysis run after each experiment or on-demand via /analyze.

Data

Read:

  • Latest experiment's report + results.csv or tune_results.csv
  • Current best metrics from experiments/summary.md journal entries
  • experiments/dataset_profile.yaml
  • training-plan.md (thresholds, goals, constraints)

Results.csv Lookup Order

  1. experiments/exp_NNN_name/train/results.csv
  2. experiments/exp_NNN_name/results.csv
  3. 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.md from 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.

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.