CtrlK
BlogDocsLog inGet started
Tessl Logo

length

Use when generating URL slugs from article titles, auditing URL structures for unnecessary depth or length, or reviewing URL patterns in a CMS or router configuration.

70

Quality

86%

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

SKILL.md
Quality
Evals
Security

Quality

Content

72%

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

A well-structured, actionable audit skill with clean progressive disclosure to a single real reference file. Its main weaknesses are conciseness redundancy between the intro and Explain sections and the absence of an explicit validation/verification checkpoint after destructive 301-redirect URL changes.

Suggestions

Collapse the Explain section into the intro (or vice versa) — both cover URL truncation, shareability, and crawl distance, so merging removes the redundancy that holds conciseness at 2.

Add an explicit verification step to the Fix workflow (e.g., after 301 redirects and sitemap/internal-link updates, verify redirects resolve and re-crawl affected URLs), which would lift workflow_clarity above the destructive-operation cap of 2.

Tighten general statements Claude already knows (e.g., "Google recommends keeping URLs 'simple, descriptive, and readable'") to keep every token earning its place.

DimensionReasoningScore

Conciseness

Mostly efficient with concrete Quick Reference/Check/Fix sections, but the Explain section restates the intro (URL truncation, shareability, crawl distance) and some general guidance Claude already knows; could be tightened. Not a score-1 padded wall explaining what URLs are, but the redundancy keeps it below 3.

2 / 3

Actionability

Provides concrete, actionable guidance for an instruction-only audit skill: explicit thresholds (path >100 chars, >4 segments), a named stop-word list, and concrete before/after URL transformations plus specific code-review operations. The scoring note allows absence of code in instruction-only skills when guidance is actionable, which it is.

3 / 3

Workflow Clarity

Fix offers a numbered sequence (shorten slugs, flatten structure, remove dates, 301 redirects, update sitemaps) but no validation checkpoint after destructive/batch URL changes with 301 redirects. Per the scoring notes, missing verification for destructive batch operations caps workflow clarity at 2.

2 / 3

Progressive Disclosure

Body is a well-organized overview (Quick Reference, Check, Fix, Explain, Code Review) that defers full code examples and framework guidance to a clearly signaled, one-level-deep reference; references/rule.md exists and is referenced exactly once, matching the clear-overview anchor.

3 / 3

Total

10

/

12

Passed

Description

100%

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 strong, third-person description with an explicit "Use when" trigger and three concrete, naturally-phrased capabilities. It clearly communicates both what the skill does and when to invoke it within a distinct SEO URL-hygiene niche.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "generating URL slugs from article titles", "auditing URL structures for unnecessary depth or length", "reviewing URL patterns in a CMS or router configuration" — matching the multi-action anchor rather than the single-domain score-2 example.

3 / 3

Completeness

Opens with an explicit "Use when..." trigger clause and embeds the concrete capabilities (generate/audit/review) as the "what", satisfying both what and when; the guideline cap at 2 only applies when "Use when" guidance is missing, which it is not.

3 / 3

Trigger Term Quality

Uses natural terms a user would say ("URL slugs", "article titles", "URL structures", "URL patterns", "CMS or router configuration") with good coverage of common phrasings; not jargon-only like the score-1 anchor.

3 / 3

Distinctiveness Conflict Risk

Occupies a clear niche (SEO URL length/slug hygiene) with distinct triggers unlikely to fire for unrelated skills; matches the clear-niche anchor.

3 / 3

Total

12

/

12

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository
thedaviddias/Front-End-Checklist
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.