CtrlK
BlogDocsLog inGet started
Tessl Logo

extract-version

Parse and validate semantic version strings from various formats. Use for extracting versions from text, validating semver compliance, or comparing version numbers.

61

Quality

71%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/extract-version/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A clear, actionable, well-sequenced parsing skill that gives concrete regex, components, validation rules, and broad examples. Its main weakness is conciseness: the repeated full-JSON examples and lack of an explicit retry loop keep it from the top band.

Suggestions

Consolidate the six examples: show the complete output JSON once, then for subsequent cases display only the fields that differ, to cut repetition and respect the token budget.

Add a brief fix-and-retry feedback loop in the Error Handling section (e.g., on invalid component, identify the offending identifier and re-attempt after correction) to lift workflow clarity.

Encode the no-leading-zeros rule into the validation step or expand the regex so the executable guidance matches the stated validation rules with no gaps.

DimensionReasoningScore

Conciseness

The body is directive and avoids explaining concepts Claude already knows, but six worked examples each repeat the full output JSON object with near-identical structure, which is repetition that could be tightened by showing the complete object once and only the differing fields afterward.

3 / 5

Actionability

Provides a concrete copy-paste regex, defined components, validation rules, and six input/output examples covering common cases; minor gaps remain because the leading-zero validation rule is not encoded in the regex and no complete runnable function wraps the logic.

4 / 5

Workflow Clarity

Steps 1–5 are clearly sequenced (receive → extract → parse → validate → return) with an explicit validation step, an error-handling section, and a validation checklist; it falls short of 5 only because there is no explicit fix-and-retry feedback loop for invalid input.

4 / 5

Progressive Disclosure

Content is well organized into clear sections (When to Use, Instructions, Error Handling, Examples, Validation, Supporting Files) and is self-contained with no external references needed; it is over 50 lines so the simple-skill exception does not lift it to 5, but structure is solid with only minor organization gaps.

4 / 5

Total

15

/

20

Passed

Description

75%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A well-constructed description that pairs a clear capability statement with a concrete "Use for" trigger list and stays in third person. It is balanced across all dimensions without notable defects, sitting at a solid 4 rather than 5 due to minor coverage and phrasing gaps.

DimensionReasoningScore

Specificity

Names the domain and lists several concrete actions — "Parse and validate semantic version strings", "extracting versions from text", "validating semver compliance", "comparing version numbers" — but omits normalization which the body later covers, leaving minor coverage gaps rather than comprehensive coverage.

4 / 5

Completeness

Explicitly answers both what ("Parse and validate semantic version strings from various formats") and when ("Use for extracting versions from text, validating semver compliance, or comparing version numbers"); the trigger is concrete task-list guidance but framed as "Use for" rather than user-speech triggers, so it is not a clean 5.

4 / 5

Trigger Term Quality

Includes natural terms users would say ("semantic version strings", "semver compliance", "version numbers", "extracting versions") with the synonym pair semver/semantic version, but stops short of comprehensive coverage of every phrasing a user might reach for.

4 / 5

Distinctiveness Conflict Risk

The semver niche is mostly distinct with clear triggers, though "extracting versions from text" is broad enough to carry minor overlap risk with general string/text-extraction skills, keeping it just below a 5.

4 / 5

Total

16

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
maslennikov-ig/claude-code-orchestrator-kit
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.