Skip to content
Back to skills

Ml Experiment Tracking

ASecurity

Track machine learning experiments with reproducible parameters and metrics

  • 42 stars
  • 0 votes
  • 0 copies
  • 4 views
  • Added May 31, 2026
researchgoperformance

Security analysis

A100/100

Scanned May 31, 2026

npx -y skills add diegosouzapw/awesome-omni-skill --skill ml-experiment-tracking --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Ml Experiment Tracking?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Ml Experiment Tracking
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/diegosouzapw-ml-experiment-tracking/badge)](https://www.skillsdirectory.com/skills/diegosouzapw-ml-experiment-tracking)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: ML Experiment Tracking
description: Track machine learning experiments with reproducible parameters and metrics
category: ml
version: 1.0.0
triggers:
  - model-training
  - experiment-run
  - hyperparameter-search
globs: "**/models/**,**/experiments/**,**/ml/**"
---

# ML Experiment Tracking Skill

Track machine learning experiments with reproducible parameters and metrics.

## Trigger Conditions
- Model configuration changes or hyperparameter updates
- New experiment run initiated
- User invokes with "track experiment" or "compare models"

## Input Contract
- **Required:** Experiment parameters (model, hyperparameters, data)
- **Required:** Evaluation metrics
- **Optional:** Baseline comparison, hypothesis

## Output Contract
- Experiment log entry with full reproducibility info
- Comparison table against baseline/prior runs
- Recommendation on whether to promote or iterate

## Tool Permissions
- **Read:** Model configs, training data metadata, metric logs
- **Write:** Experiment logs, comparison reports
- **Execute:** Metric collection commands

## Execution Steps
1. Record experiment hypothesis and parameters
2. Capture environment (dependencies, data version, code commit)
3. Execute or observe training run
4. Collect metrics and artifacts
5. Compare against baseline and prior experiments
6. Recommend: promote, iterate, or abandon

## Success Criteria
- Experiment is fully reproducible from logged parameters
- Metrics compared against baseline
- Clear recommendation with rationale

## Escalation Rules
- Escalate if model performance degrades vs. baseline
- Escalate if data drift detected in training set
- Escalate if experiment requires new infrastructure

## Example Invocations

**Input:** "Compare the BERT-base and DistilBERT models for our classification task"

**Output:** Experiment log: BERT-base (F1: 0.92, latency: 45ms, size: 440MB) vs DistilBERT (F1: 0.89, latency: 12ms, size: 260MB). Recommendation: DistilBERT for production (3% F1 trade-off for 73% latency improvement). Promote to staging for A/B test.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…