CtrlK
BlogDocsLog inGet started
Tessl Logo

special-chars

Use when applies to any site with user-generated slugs, CMS-generated URLs, or content in non-English languages. Use when auditing URLs for crawl errors or canonicalization issues.

56

Quality

63%

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

Quality

Content

80%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 skill body is concise, well-structured, and uses progressive disclosure effectively with a real one-level reference. Its main weakness is workflow clarity for a batch-audit task, where an explicit validation/verification checkpoint is missing from the body.

Suggestions

Add an explicit verification step in the Check or Fix section (e.g., confirm flagged URLs return distinct 200s for different encodings before acting) to satisfy the batch-operation validation requirement.

Include one short inline slugify/sanitization snippet in the Fix section so guidance is copy-paste ready without opening the reference.

State the recommended order explicitly (scan → confirm duplicate responses → fix generation logic → redirect old URLs) to make the sequence and feedback loop unmistakable.

DimensionReasoningScore

Conciseness

The body is lean and well-organized with no padding or restating of basic concepts; every section (Quick Reference, Check, Fix, Explain, Code Review) earns its place.

5 / 5

Actionability

The Check section gives a concrete scan regex and flags to look for, and Fix gives specific steps (replace spaces with hyphens, percent-encode, redirect), though no inline copy-paste example is provided in the body itself.

4 / 5

Workflow Clarity

The Check→Fix→Explain→Code Review sections form a sequence, but this is a batch audit skill and the body lacks an explicit validation/verification checkpoint, capping workflow clarity at 3 per the batch-operation rule.

3 / 5

Progressive Disclosure

The body is a clear overview with a well-signaled one-level-deep reference ('see references/rule.md') that exists as a real file, with detailed code and examples appropriately split into that reference.

5 / 5

Total

17

/

20

Passed

Description

47%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, niche trigger conditions but omits any statement of what the skill actually does, leaving the 'what' half of completeness empty. Trigger-term coverage is solid though missing common synonyms.

Suggestions

Lead with a concrete capability verb (e.g., 'Scans crawled URL paths for special characters and flags encoding/canonicalization issues') so the 'what' is explicit.

Add natural synonyms such as 'URL encoding', 'percent-encoding', and 'broken URLs' to broaden trigger coverage.

Merge the two 'Use when' clauses into a single, tighter trigger sentence to reduce redundancy.

DimensionReasoningScore

Specificity

The description names the domain (special characters in URLs) via 'user-generated slugs, CMS-generated URLs' but states no concrete actions — there is no verb describing what the skill does, only when to apply it.

2 / 5

Completeness

It has an explicit and repeated 'when' ('Use when ...') but never states the 'what' — the action the skill performs is entirely unstated, matching the anchor where only the trigger is present without the capability.

2 / 5

Trigger Term Quality

Natural phrases users would say are present ('user-generated slugs', 'CMS-generated URLs', 'crawl errors', 'canonicalization issues'), though synonyms like 'URL encoding' or 'percent-encoding' are missing.

4 / 5

Distinctiveness Conflict Risk

Triggers are fairly niche (special chars, slugs, canonicalization) and unlikely to fire for unrelated skills, with only minor overlap risk against general SEO skills.

4 / 5

Total

12

/

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.