CtrlK
BlogDocsLog inGet started
Tessl Logo

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).

57

Quality

66%

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

Quality

Content

78%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 is a well-structured, concise overview with strong actionable directives and clear verification steps, appropriately delegating details to one external reference. It only falls short of top marks on minor over-explanation and the absence of an explicit error-recovery loop.

DimensionReasoningScore

Conciseness

The body is lean with short, focused sections and bullets, but the 'Explain' section mildly re-explains a SEO concept Claude largely knows and the Quick Reference overlaps slightly with Fix.

4 / 5

Actionability

Provides concrete, specific directives ('301 redirects', 'verify they return 301... not 200', 'check the sitemap for uppercase <loc> entries') with no inline code, which is acceptable for an instruction skill but keeps it just short of fully copy-paste-ready.

4 / 5

Workflow Clarity

Clear sequenced Check → Fix → Code Review flow with explicit verification checkpoints (test response codes, confirm 301 vs 200), though it lacks an explicit 'if check fails → fix → re-check' recovery loop.

4 / 5

Progressive Disclosure

A well-organized overview (Quick Reference, Check, Fix, Explain, Code Review) that delegates implementation details and code examples to a single, clearly signaled one-level-deep reference (references/rule.md), which exists.

5 / 5

Total

17

/

20

Passed

Description

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

The description has a strong explicit 'Use when' trigger and a reasonably distinct niche, but the actual capability is implied rather than stated and the most natural trigger phrases (lowercase URLs, URL case) are absent.

Suggestions

State the concrete action explicitly, e.g. 'Normalize URLs to lowercase and 301-redirect uppercase variants to prevent duplicate content.'

Add the natural trigger phrases users would say, such as 'lowercase URLs', 'URL case', or 'duplicate content from mixed-case URLs'.

Tighten 'configuring a new site's routing' to something more specific to URL casing to reduce overlap with general routing skills.

DimensionReasoningScore

Specificity

Names the domain (URL structure, routing) and a couple of actions ('auditing URL structure', 'configuring a new site's routing') but never states the concrete capability (enforce lowercase, 301-redirect uppercase), so it is not comprehensive enough for a 4.

3 / 5

Completeness

The 'when' is explicit ('Use when auditing URL structure or configuring a new site's routing'), but the 'what' is only weakly implied via 'Applies to any server or framework...' rather than stated as a concrete action, so it does not clearly satisfy both.

3 / 5

Trigger Term Quality

Includes relevant terms ('URL structure', 'routing') but misses the most natural user phrases for this skill such as 'lowercase URLs', 'URL case', and 'duplicate content'.

3 / 5

Distinctiveness Conflict Risk

Carves a fairly specific lowercase-URL/routing niche with only minor overlap risk against general routing or SEO skills, though 'configuring a new site's routing' is somewhat broad.

4 / 5

Total

13

/

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.

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.