AgentStack
SKILL unreviewed MIT Self-run

Training Loop Debugger

skill-maximussthegreat-ml-researcher-os-training-loop-debugger · by maximussthegreat

Use when reviewing ML training code, suspicious metrics, unstable loss, broken evaluation, or a model that appears too good to be true.

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

Install

$ agentstack add skill-maximussthegreat-ml-researcher-os-training-loop-debugger

Open-source listing — not yet scanned by AgentStack. Follow the source repository for install instructions.

Security review

⚠ Flagged

1 finding(s); flagged for manual review. · v0.1.0 How review works →

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

What it can access

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

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.

Are you the author of Training Loop Debugger? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Training Loop Debugger

Use this skill to review training and evaluation code before trusting results.

Goal

Find the smallest code or protocol issue that could invalidate reported model metrics.

Review order

  1. Data loading
  2. Split creation
  3. Preprocessing fit and transform
  4. Model initialization
  5. Loss and optimizer
  6. Training mode and eval mode
  7. Metric computation
  8. Checkpoint selection
  9. Test set use
  10. Logging and reproducibility

High-risk bugs

Immediately flag:

  • fitting scalers, tokenizers, imputers, or feature selectors on validation or test data
  • using test data for early stopping
  • computing metrics on logits when probabilities or labels are required
  • forgetting model.eval() during evaluation
  • forgetting torch.no_grad() during evaluation
  • using different preprocessing at train and eval time
  • reporting the best validation run as test performance
  • changing seeds until a good result appears

Required output

| Area | Finding | Severity | Evidence | Fix | | --- | --- | --- | --- | --- |

Severity must be one of:

  • blocker
  • high
  • medium
  • low

Rules

  • Do not claim the model is fixed until a rerun is available.
  • Do not rewrite the whole project when a small patch explains the issue.
  • If logs are missing, ask for logs or mark the conclusion as provisional.

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.