lowercase

Use when auditing URL structure or configuring a new site's routing. Applies to any server or framework that allows case-insensitive file systems (Linux servers are case-sensitive by default).

Quality

72%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/lowercase/SKILL.md

Quality

Content

87%

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

The body is concise, actionable, and cleanly structured with an appropriately placed one-level reference. The main gap is workflow clarity: the redirect workflow lacks an inline verification/feedback checkpoint despite link-equity risk, though the reference file does include verification steps.

Suggestions

Add an inline verification step in the body after Fix (e.g. 'Crawl uppercase variants to confirm 301, not 200, before relying on the redirect') so the feedback loop is visible without opening the reference.

State explicitly that uppercase URLs must be redirected before removal, not dropped, to surface the link-equity risk at the overview level.

Dimension	Reasoning	Score
Conciseness	The body is lean and sectioned (Quick Reference / Check / Fix / Explain / Code Review) with every line earning its place; the brief Explain section restates the duplicate-content rationale on-topic without padding, matching the 'Lean and efficient' anchor.	3 / 3
Actionability	Concrete, specific instructions ('Add 301 redirects from any existing uppercase URLs to their lowercase equivalents', 'verify they return 301 to the lowercase version, not 200') give actionable direction; per the instruction-skill scoring note, absence of inline code is not penalized when guidance is this concrete.	3 / 3
Workflow Clarity	Check → Fix → Code Review is sequenced, but the operation deploys 301 redirects that carry link-equity risk with no inline validation/feedback loop in the body — the rubric caps workflow clarity at 2 when validation is missing for destructive or equity-affecting operations.	2 / 3
Progressive Disclosure	A clear overview with a single well-signaled one-level-deep reference to references/rule.md (verified to exist and not further nested), with content appropriately split, matching the 'Clear overview with well-signaled one-level-deep references' anchor.	3 / 3
	Total	11 / 12 Passed

Description

57%

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

The description gives a clear, third-person trigger scoped to URL structure and routing, with good distinctiveness. Its weakness is that the core capability (enforce lowercase URLs) is implied rather than stated, and trigger vocabulary leans slightly technical.

Suggestions

Lead with an explicit 'what' verb phrase, e.g. 'Enforces lowercase URLs and 301-redirects uppercase variants' before the 'Use when' clause.

Add common trigger terms users would actually say — 'lowercase URLs', 'URL SEO', 'duplicate URLs' — alongside 'URL structure' and 'routing'.

Replace or soften 'case-insensitive file systems' with user-facing phrasing unless the technical precision is essential.

Dimension	Reasoning	Score
Specificity	Names the domain ("URL structure", "a new site's routing", "case-insensitive file systems") and concrete actions ("auditing", "configuring") but stops short of listing multiple specific operations, matching the 'Names domain and some actions' anchor.	2 / 3
Completeness	The 'Use when...' clause gives a strong explicit trigger (when), but the actual capability (enforce lowercase URLs) is only implied rather than stated, so it sits at the 'Has what, but when is missing or only implied' level inverted — the when is explicit while the what is implied, still a 2.	2 / 3
Trigger Term Quality	"URL structure" and "routing" are natural user terms, but "case-insensitive file systems" is technical jargon and common variations ("lowercase URLs", "SEO", "URLs") are absent, fitting the 'some relevant keywords but missing common variations' anchor.	2 / 3
Distinctiveness Conflict Risk	Lowercase URL normalization for case-insensitive filesystems is a clear niche with distinct triggers unlikely to fire for unrelated skills, matching the 'Clear niche with distinct triggers' anchor.	3 / 3
	Total	9 / 12 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: thedaviddias/Front-End-Checklist
Path: skills/lowercase/SKILL.md
Commit: 48405aa

Reviewed: about 10 hours ago

Table of Contents

Discovery Implementation Validation

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.