CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

Quality

73%

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

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, lean overview with an actionable check procedure and a clean one-level pointer to references/rule.md for details. Its main weakness is the absence of any post-fix validation step and the Fix section relying entirely on the reference for concrete examples.

DimensionReasoningScore

Conciseness

The body is lean and tightly sectioned (Quick Reference, Check, Fix, Explain, Code Review), but the opening line duplicates the description and the Quick Reference bullets restate RFC 3986 basics (unreserved set, %20 vs +) that Claude already knows — minor over-explanation that could be trimmed.

4 / 5

Actionability

The Check section is genuinely executable ("characters outside `[A-Za-z0-9\-_./~]`", flag spaces/`#`/`?`/`&`/`=`/`+`, "check if different encodings of the same URL return separate 200 responses"), and Fix gives concrete direction (replace spaces with hyphens, percent-encode reserved chars, set up redirects). Falls short of 5 because the Fix path has no inline code or commands — examples are deferred to references/rule.md — and short of nothing at 3 since the guidance is concrete rather than pseudocode-level.

4 / 5

Workflow Clarity

A clear Check → Fix → Explain → Code Review sequence is present, with one embedded verification checkpoint (the dual-encoding 200-response test). Minor validation gap: no post-fix verification step (e.g., confirm redirects resolve or re-run the scan), which fits anchor 4 rather than 5.

4 / 5

Progressive Disclosure

SKILL.md is a concise overview with well-organized sections, and the single reference is real (references/rule.md, verified), clearly signaled ("For full implementation details, code examples, and framework-specific guidance, see `references/rule.md`"), and exactly one level deep — the ideal split for a simple rule skill.

5 / 5

Total

17

/

20

Passed

Description

57%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 strong, explicit trigger conditions but never states what the skill does, and it omits the very keywords ('special characters', 'URL encoding') that make it both findable and distinct from neighboring SEO rules. It functions as a pure trigger line rather than a what+when description.

Suggestions

Lead with an explicit capability statement before the triggers, e.g., 'Checks URL paths for special characters (spaces, reserved symbols, non-ASCII) and guides fixing slug generation, encoding, and redirects.'

Add the natural trigger terms users would actually say: 'special characters', 'URL encoding', 'percent-encoding', and 'spaces in URLs' — none currently appear despite being the skill's core concept.

Mention 'special characters in URL paths/slug' explicitly to reduce overlap with other SEO skills triggered by generic 'crawl errors' or 'canonicalization issues'.

DimensionReasoningScore

Specificity

The description names the domain ("user-generated slugs, CMS-generated URLs, or content in non-English languages") and one concrete action ("auditing URLs for crawl errors or canonicalization issues"), matching anchor 3's '1-2 concrete actions, but not comprehensive'. It is not a 4 because no several-action capability list is given, and not a 2 because 'auditing URLs for crawl errors or canonicalization issues' is more concrete than a generic verb like 'Processes PDF files'.

3 / 5

Completeness

The 'when' is explicit and specific (two 'Use when...' clauses), but the 'what' is never separately stated — the skill's activity is only implied through the gerund in "Use when auditing URLs for crawl errors or canonicalization issues". This sits above anchor 2 (only a vague 'when', no 'what') but below anchor 4, which requires both explicitly.

3 / 5

Trigger Term Quality

Good natural keyword coverage — "user-generated slugs", "CMS-generated URLs", "non-English languages", "crawl errors", "canonicalization issues" — fitting anchor 4. It misses 5 because the most natural user phrasings are absent: "special characters" (the skill's own name), "URL encoding", "percent-encoding", and "spaces in URLs" never appear.

4 / 5

Distinctiveness Conflict Risk

The slug/CMS/non-English triggers are moderately specific, but the second clause ("auditing URLs for crawl errors or canonicalization issues") overlaps heavily with other SEO audit skills (canonical-tag rules, crawl-error rules), and the description omits its own distinctive concept — special characters in URL paths. Anchor 3 ('could still overlap with similar skills') is the best fit.

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

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/special-chars/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.