mlflow-tracking-setup
Mlflow Tracking Setup - Auto-activating skill for ML Training. Triggers on: mlflow tracking setup, mlflow tracking setup Part of the ML Training skill category.
36
3%
Does it follow best practices?
Impact
96%
0.96xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/07-ml-training/mlflow-tracking-setup/SKILL.mdQuality
Discovery
7%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description is extremely weak, essentially just restating the skill name with a duplicated trigger term. It fails to describe any concrete actions, lacks natural trigger keywords users would use, and provides no explicit guidance on when Claude should select this skill. It reads more like an auto-generated stub than a functional skill description.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Configures MLflow tracking servers, sets up experiment logging, defines tracking URIs, and initializes artifact storage for ML experiments.'
Add an explicit 'Use when...' clause with diverse trigger terms, e.g., 'Use when the user asks about setting up MLflow, configuring experiment tracking, logging ML metrics, tracking model training runs, or setting up a tracking URI.'
Remove the duplicate trigger term and expand with natural keyword variations users might say, such as 'experiment tracking', 'log metrics', 'MLflow server setup', 'tracking URI configuration', 'model registry'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only says 'Mlflow Tracking Setup' without listing any concrete actions like configuring experiment tracking, logging metrics, setting up artifact stores, or creating runs. It is essentially just a name repeated, not a description of capabilities. | 1 / 3 |
Completeness | The 'what' is extremely vague (just the skill name) and the 'when' is only implied through the duplicate trigger phrase. There is no explicit 'Use when...' clause or meaningful explanation of what the skill does or when Claude should select it. | 1 / 3 |
Trigger Term Quality | The trigger terms listed are just 'mlflow tracking setup' repeated twice. It misses natural variations users might say such as 'experiment tracking', 'log metrics', 'MLflow server', 'tracking URI', 'mlflow configure', or 'model logging'. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'mlflow' does provide some domain specificity that distinguishes it from generic ML skills, but the lack of detail about what specific MLflow tracking tasks it handles could cause overlap with other MLflow-related or ML experiment tracking skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is essentially a placeholder with no substantive content. It contains only meta-descriptions of what it claims to do without any actual instructions, code, commands, or concrete guidance for setting up MLflow tracking. It fails on every dimension because it provides zero actionable information.
Suggestions
Add concrete, executable code examples showing MLflow tracking setup (e.g., `mlflow.set_tracking_uri()`, `mlflow.set_experiment()`, `mlflow.start_run()`, logging params/metrics/artifacts).
Include a clear step-by-step workflow: install MLflow, configure tracking URI, create experiment, log runs, with validation steps like verifying the tracking server is accessible.
Remove all meta-description sections (Purpose, When to Use, Capabilities, Example Triggers) and replace with actual technical content—code snippets, configuration examples, and common patterns.
Add references to advanced topics like remote tracking server setup, artifact storage configuration, and model registry integration as separate linked files or clearly delineated sections.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and meta-description. It explains what the skill does in abstract terms without providing any actual technical content about MLflow tracking setup. Every section restates the same vague idea. | 1 / 3 |
Actionability | There is zero concrete guidance—no code, no commands, no configuration examples, no specific steps for setting up MLflow tracking. It only describes rather than instructs. | 1 / 3 |
Workflow Clarity | No workflow is defined. The skill claims to provide 'step-by-step guidance' but contains no actual steps, sequences, or validation checkpoints. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of vague descriptions with no references to detailed materials, no links to examples or configuration files, and no meaningful structural organization. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Commit
3076d78
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.