Build this skill enables AI assistant to track and manage ai/ml model versions using the model-versioning-tracker plugin. it should be used when the user asks to manage model versions, track model lineage, log model performance, or implement version control f... Use when appropriate context detected. Trigger with relevant phrases based on skill purpose.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill tracking-model-versions68
Quality
20%
Does it follow best practices?
Impact
72%
1.10xAverage score across 12 eval scenarios
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/ai-ml/model-versioning-tracker/skills/tracking-model-versions/SKILL.mdDiscovery
32%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 suffers from being truncated mid-sentence and using completely generic boilerplate for the 'when' clause. While it identifies a specific domain (AI/ML model versioning) and mentions some concrete actions, the placeholder trigger guidance ('Use when appropriate context detected') provides zero value for skill selection among multiple options.
Suggestions
Replace the generic 'Use when appropriate context detected. Trigger with relevant phrases based on skill purpose' with specific triggers like 'Use when user mentions MLflow, model registry, model artifacts, experiment tracking, or ML model deployment'
Complete the truncated description to fully list all capabilities (the text cuts off at 'implement version control f...')
Rewrite in proper third person voice - remove 'Build this skill enables AI assistant' and start with action verbs like 'Tracks and manages AI/ML model versions...'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (AI/ML model versioning) and lists some actions (track model versions, track model lineage, log model performance, implement version control), but the description is truncated and uses vague language like 'Build this skill enables AI assistant'. | 2 / 3 |
Completeness | The 'what' is partially present but truncated. The 'when' clause is completely generic boilerplate ('Use when appropriate context detected. Trigger with relevant phrases based on skill purpose') that provides no actual guidance for skill selection. | 1 / 3 |
Trigger Term Quality | Contains some relevant keywords like 'model versions', 'model lineage', 'model performance', 'version control', but the generic 'Trigger with relevant phrases based on skill purpose' adds no value and the description is cut off, potentially missing important trigger terms. | 2 / 3 |
Distinctiveness Conflict Risk | The AI/ML model versioning domain is somewhat specific, but the truncated description and generic trigger guidance could cause overlap with other ML-related skills or general version control skills. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
7%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 template with placeholder content that provides no actionable guidance for using the model-versioning-tracker plugin. It lacks any concrete code examples, specific API calls, or actual commands. The content is padded with generic statements and boilerplate that Claude already knows, wasting tokens without providing value.
Suggestions
Add executable code examples showing actual API calls to the model-versioning-tracker plugin (e.g., specific function calls, CLI commands, or SDK usage)
Remove redundant sections and generic boilerplate (duplicate overview, obvious best practices like 'implement error handling')
Replace abstract example descriptions with concrete input/output pairs showing actual code and expected responses
Specify actual prerequisites: name the exact dependencies, required environment variables, and configuration needed
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose with redundant sections (Overview repeats itself), explains obvious concepts Claude knows (what version control is, what error handling means), and includes generic boilerplate that adds no value ('This skill provides automated assistance for model versioning tracker tasks' appears twice). | 1 / 3 |
Actionability | No concrete code, commands, or executable examples provided. Examples describe what 'the skill will do' abstractly rather than showing actual code to interact with the model-versioning-tracker plugin. Prerequisites mention 'required dependencies' without naming them. | 1 / 3 |
Workflow Clarity | The 'How It Works' section is vague ('Generate Code', 'Execute Task') without showing actual steps. No validation checkpoints, no specific commands, and the Instructions section is completely generic boilerplate that could apply to any skill. | 1 / 3 |
Progressive Disclosure | Content is organized into sections with headers, but everything is in one file with no references to external documentation. The structure exists but contains mostly filler content that doesn't warrant the organization. | 2 / 3 |
Total | 5 / 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 | |
Table of Contents
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.