trailing-slash

Use when applies to all static and dynamic websites. Use when auditing a site for duplicate content, setting up a new site, or after migrating platforms that changed URL conventions.

Quality

55%

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/trailing-slash/SKILL.md

Quality

Content

65%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 content is a well-structured, lean overview that correctly offloads implementation detail to a real references/rule.md file with clear one-level navigation. Its main weakness is that the body states the audit/fix steps without an explicit validation checkpoint, and executable redirect/canonical examples live only in the reference rather than being surfaced inline.

Suggestions

Add a short 'Verify' step to the body's Fix section (e.g. re-test both URL variants return a single 200 + 301 and confirm canonical points to the preferred version) so the validate→fix→retry loop is visible without opening the reference.

Surface one concrete redirect snippet inline (e.g. the Nginx `rewrite ^/(.*)/$ /$1 permanent;` line) so the SKILL.md is immediately actionable for the most common case.

Move or summarize the rule.md 'Standards'/'Verification' checklist into the body's Code Review section so reviewers can confirm search-facing output without a second file hop.

Dimension	Reasoning	Score
Conciseness	The body is lean — Quick Reference bullets, short Check/Fix/Explain/Code Review sections — and assumes Claude knows what trailing slashes and 301 redirects are; only minor padding remains (e.g. restating the duplicate-content rationale in both the intro and Quick Reference), placing it just above the 'mostly efficient' anchor.	4 / 5
Actionability	The Check/Fix sections give concrete, executable tests ('Both should NOT return HTTP 200 — one must 301-redirect', 'curl -I') via the reference, but the body itself contains no copy-paste redirect rules or canonical-tag snippets — those live only in references/rule.md — so guidance is actionable but incomplete in the SKILL.md body.	3 / 5
Workflow Clarity	Check and Fix sections sequence the audit and remediation, but there is no explicit validation checkpoint confirming the redirect/canonical state after the fix (the cap for destructive/batch-audit operations without validation applies); the reference's 'Verification' section supplies this, yet the SKILL.md body lacks the validate→fix→retry loop.	3 / 5
Progressive Disclosure	The SKILL.md is a concise overview with well-signaled one-level-deep navigation — 'see references/rule.md' — and the referenced file exists and holds the detailed code examples, matching the clear-overview-with-one-level-deep-references anchor exactly.	5 / 5
	Total	15 / 20 Passed

Description

45%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 provides clear invocation triggers tied to duplicate-content audits, new sites, and platform migrations, but omits the core 'trailing slash' keyword and never states the concrete action the skill performs. The opening 'Use when applies to all...' is awkward and reads as a trigger clause with no preceding capability statement.

Suggestions

Lead with a concrete capability statement naming the action, e.g. 'Audits and enforces consistent trailing-slash URL conventions across a site to prevent duplicate content.'

Add the primary trigger term 'trailing slashes' (and variants like 'trailing slash', 'URL conventions') so users who mention the actual symptom surface this skill.

Drop or tighten 'applies to all static and dynamic websites' — it is overly broad and raises conflict risk with general SEO skills; the duplicate-content/migration triggers already scope the niche.

Dimension	Reasoning	Score
Specificity	It names the domain ('all static and dynamic websites') and lists scenarios ('auditing a site for duplicate content', 'setting up a new site', 'after migrating platforms'), but never states a concrete action the skill performs — there is no 'enforces'/'audits'/'fixes' trailing-slash verb, so it sits below the 3 anchor which requires 1-2 concrete actions.	2 / 5
Completeness	The 'when' is explicit and even repeated ('Use when...'), but the 'what' is effectively missing: the description never says what the skill does, only when to invoke it, matching the 3 anchor of a clear 'what' absent with 'when' present only weakly implied.	3 / 5
Trigger Term Quality	Phrases like 'auditing a site for duplicate content', 'setting up a new site', and 'migrating platforms that changed URL conventions' are natural triggers, but the most relevant keyword — 'trailing slash' — is entirely absent, leaving common variations and the core synonym missing.	3 / 5
Distinctiveness Conflict Risk	'applies to all static and dynamic websites' is very broad and would overlap with many SEO/canonicalization skills, though the duplicate-content and migration-URL scenarios narrow the niche somewhat, leaving it at the 'somewhat specific but could still overlap' anchor.	3 / 5
	Total	11 / 20 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/trailing-slash/SKILL.md
Commit: 30756a7

Reviewed: 4 days 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.