CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

hyphens

Use when auditing URL structures for word separator format, generating slugs from titles, or planning a URL migration from underscores or spaces to hyphens with appropriate redirects.

Quality

73%

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 ./skills/hyphens/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

61%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 well-structured, mostly actionable skill body with a clean overview-to-reference split. Its weaknesses are a thrice-repeated rationale Claude already knows, and a migration workflow that lists clear steps but omits explicit post-migration validation despite being a batch operation.

Suggestions

State the hyphens-vs-underscores rationale once (e.g., in Quick Reference) and delete the duplicated intro paragraph and 'Explain' section, or move the Mueller/Explain detail into references/rule.md.

Add an explicit validation step to the Fix workflow, e.g., 'After deploying redirects, verify each old URL returns a 301 to its new hyphenated equivalent and re-crawl to confirm no underscore URLs remain.'

Make the redirect step concrete by including a minimal example (e.g., an nginx or .htaccess 301 rule mapping /best_practices to /best-practices) instead of only naming the action.

DimensionReasoningScore

Conciseness

The body is mostly efficient, but the hyphens-vs-underscores rationale is stated three times (intro paragraph, Quick Reference bullet 1, and the 'Explain' section — 'Google interprets hyphens as word separators in URLs, but treats underscores as word joiners'), and this is a concept Claude already knows. This matches 'mostly efficient but includes some unnecessary explanation or could be tightened' rather than score 2, since the Check/Fix/Code Review sections are tight and unpadded.

3 / 5

Actionability

Concrete and executable in most places: the Check section names exact flags ('underscores (_)', 'spaces encoded as %20 or +', 'mixed separators'), and Fix includes a runnable slug regex ('title.toLowerCase().replace(/\s+/g, \'-\').replace(/[^a-z0-9-]/g, \'\')'). It falls short of 5 because steps like 'Set up 301 permanent redirects' and 'Submit the new URLs to Google Search Console' give no concrete config or command, deferring entirely to the reference file.

4 / 5

Workflow Clarity

The Fix section has a clear 7-step sequence, but a site-wide URL migration is a batch operation with no explicit validation checkpoint — there is no 'verify old URLs return 301', 'crawl for remaining underscore URLs', or re-check step after migration. Per the rubric's cap for batch operations lacking validation, this cannot exceed 3; the sequence is present but checkpoints are missing or implicit.

3 / 5

Progressive Disclosure

The body is a well-organized ~40-line overview with clearly signaled, one-level-deep navigation — 'For full implementation details, code examples, and framework-specific guidance, see references/rule.md' — and that file exists as real detail content. It is below 5 only because some inline material (the 'Explain' rationale and 'Code Review' section) duplicates or could live in the reference, leaving minor organization gaps.

4 / 5

Total

14

/

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 solid description with a clear niche, an explicit 'Use when' trigger, and several concrete, naturally phrased actions. Its main limitation is structure: it is one long trigger clause rather than a separate what/when pair, and a few natural synonyms (dashes, kebab-case) are absent.

DimensionReasoningScore

Specificity

The description lists three concrete actions — 'auditing URL structures for word separator format', 'generating slugs from titles', 'planning a URL migration from underscores or spaces to hyphens with appropriate redirects' — which matches the anchor for several specific actions with minor coverage gaps (e.g., enforcing slug format in code or reviewing redirect rules is only implied). It is above score 3 because more than 1-2 actions are named concretely, but below 5 because coverage of the skill's actual capabilities (check, fix, code-review modes shown in the body) is incomplete.

4 / 5

Completeness

Both 'what' (audit URL word separators, generate slugs, plan a migration with 301 redirects) and an explicit 'when' ('Use when...') are present, matching the score-4 anchor. It is not 5 because the entire description is a single 'when' clause with the 'what' embedded in it, and the trigger phrasing could be more natural and specific about what a user would actually say.

4 / 5

Trigger Term Quality

Natural terms users would say are present: 'URL structures', 'slugs', 'underscores', 'spaces', 'hyphens', 'migration', 'redirects' — good keyword coverage matching the score-4 anchor. It falls short of 5 because common synonyms like 'dashes' or 'kebab-case' and explicit user phrasings ('hyphens vs underscores in URLs') are missing.

4 / 5

Distinctiveness Conflict Risk

URL word-separator format is a clear niche with distinct triggers (underscores, spaces, hyphens, slugs, 301 redirects), matching 'mostly distinct; minor overlap risk'. It is below 5 because there is minor overlap risk with general SEO-audit or slug-generation skills that could also fire on URL-structure requests.

4 / 5

Total

16

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

thedaviddias/Front-End-Checklist

Path

skills/hyphens/SKILL.md

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.