CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

Quality

78%

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

Quality

Content

72%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.

The body delivers highly actionable audit and fix guidance with precise thresholds, examples, and a well-signaled one-level-deep reference file. Its weaknesses are rationale padding (the Explain section duplicating the intro and criteria restated across three sections) and the absence of validation checkpoints in a batch URL-restructuring workflow.

Suggestions

Remove or merge the "Explain" section into the intro, and consolidate the triplicated criteria (100-character limit, stop words, segment counting) so they appear once — e.g., keep Quick Reference as the only summary.

Add an explicit verification step after URL changes: confirm 301 redirects resolve, new URLs return 200, and check crawl errors in Search Console before treating the fix as complete.

DimensionReasoningScore

Conciseness

The "Explain" section ("Google recommends keeping URLs 'simple, descriptive, and readable'. Long URLs are more prone to being truncated in search snippets, harder to share...") duplicates the intro's rationale and explains concepts Claude already knows, and the 100-character limit, stop words, and segment-counting criteria each appear in Quick Reference, Check, and Code Review. Mostly efficient — Check and Fix are dense and prescriptive — but includes unnecessary explanation and could be tightened, matching anchor 3 rather than anchor 2's more pervasive padding.

3 / 5

Actionability

Fully executable guidance for an instruction-only skill: deterministic predicates ("Path length over 100 characters", "More than 4 path segments", an explicit stop-word list), concrete before/after fixes ("/how-to-optimise-your-websites-core-web-vitals → /optimise-core-web-vitals", "/blog/2024/march/technology/css-grid → /blog/css-grid"), and a concrete review procedure ("Report the longest 10 URLs by character count and deepest 10 by segment count"). Specific examples cover the common cases, matching anchor 5.

5 / 5

Workflow Clarity

The Check → Fix → Code Review sequence is clear and Fix includes mitigation steps ("Implement changes with 301 redirects", "Update sitemaps and internal links after URL changes"), but this is a batch operation over all site URLs involving risky URL restructuring, and there is no validation checkpoint — nothing verifies redirects resolve, new URLs return 200, or crawl errors stay clean. Per the rubric's cap for batch/destructive workflows without validation, this cannot score above 3 ("steps listed but validation gaps").

3 / 5

Progressive Disclosure

The body is a well-sectioned ~41-line overview and the single bundle file, references/rule.md, exists, is one level deep, clearly signaled ("For full implementation details, code examples, and framework-specific guidance, see `references/rule.md`"), and delivers what it promises (slug-generation code, Next.js route examples, a length-guidelines table). This matches anchor 5: clear overview, appropriately split, easy navigation.

5 / 5

Total

16

/

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 an explicit 'Use when' clause containing three concrete trigger scenarios and domain-specific vocabulary. Its main weakness is that the capability statement ('what') is folded into the trigger clause rather than stated separately, and a few natural synonyms (clean URLs, permalinks, SEO) are absent.

Suggestions

Lead with a declarative capability statement (e.g., "Generates clean URL slugs and audits URL paths for excessive length, nesting depth, stop words, and date segments") before the "Use when" clause so the 'what' is explicit and independent of the triggers.

Add natural synonyms users commonly say — "clean URLs", "permalinks", "SEO-friendly URLs", "stop words" — to broaden trigger coverage toward the top anchor.

DimensionReasoningScore

Specificity

Names three concrete, specific actions — "generating URL slugs from article titles", "auditing URL structures for unnecessary depth or length", "reviewing URL patterns in a CMS or router configuration" — each with a concrete object. This matches anchor 4 (several specific actions, minor gaps) rather than anchor 5, because the skill's actual outputs (flagging violations, shortening URLs, redirect guidance) are not named; it exceeds anchor 3, which expects only 1-2 concrete actions.

4 / 5

Completeness

The 'when' is explicit with three concrete trigger scenarios ("Use when generating... auditing... or reviewing..."), and the gerund phrases name the actions, but there is no standalone declarative 'what' statement — the skill's outputs must be inferred from the trigger scenarios. This falls between anchor 4 and anchor 5 and is noticeably above the midpoint, so 4.

4 / 5

Trigger Term Quality

Includes natural terms users would actually say: "URL slugs", "article titles", "URL structures", "depth or length", "CMS", "router configuration". Good keyword coverage matching anchor 4, but not anchor 5 — common synonyms such as "clean URLs", "permalinks", "SEO-friendly URLs", or "stop words" are missing; it is broader than anchor 3's 'some relevant keywords'.

4 / 5

Distinctiveness Conflict Risk

A clear niche (URL slug length/depth hygiene) distinguishable from generic SEO skills, but "generating URL slugs" could overlap a dedicated slug-generation skill and "reviewing URL patterns in a CMS or router configuration" overlaps general router-config review. Matches anchor 4 (mostly distinct, minor overlap risk with closely related skills) rather than anchor 5's minimal conflict risk.

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/length/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.