CtrlK
BlogDocsLog inGet started
Tessl Logo

title-unique

Use when applies to all HTML pages. Use when auditing a site crawl report or investigating why multiple pages compete for the same keyword in search results.

45

Quality

47%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/title-unique/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

72%

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 tight, well-structured overview that defers depth appropriately to a real reference file, with concrete check and fix guidance. Its main weakness is the absence of an explicit validation/verification checkpoint in the body for a batch audit task.

DimensionReasoningScore

Conciseness

The body is lean and well-organized into tight sections (Quick Reference, Check, Fix, Explain, Code Review) with no padded library explanations or generic concept exposition beyond a brief, relevant framing sentence.

3 / 3

Actionability

The Check and Fix sections give specific guidance and examples (CMS defaults, the '[Specific Topic] – [Site Name]' pattern), but executable specifics such as crawl tooling and code are deferred to references/rule.md rather than included.

2 / 3

Workflow Clarity

Check/Fix/Explain/Code Review imply a loose sequence, but the body lacks an explicit numbered workflow or validation checkpoint for this batch audit operation; verification steps live only in the reference file.

2 / 3

Progressive Disclosure

The body is a concise overview that clearly signals a single one-level-deep reference ('see references/rule.md'), and that file exists and holds the detailed implementation guidance.

3 / 3

Total

10

/

12

Passed

Description

22%

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 is trigger-focused but fails to state what the skill does, never references page titles, and opens with a grammatically awkward, overly broad applicability clause. It answers 'when' weakly while leaving 'what' entirely unstated.

Suggestions

Lead with a concrete capability statement such as 'Audits HTML pages for duplicate <title> tags and guides fixes to keep page titles unique across a site.'

Add natural trigger terms users would actually say, e.g. 'duplicate page titles', 'title tags', or 'pages competing for the same keyword'.

Replace the vague 'applies to all HTML pages' opener with a scoped statement tied specifically to title uniqueness to reduce conflict with other SEO skills.

DimensionReasoningScore

Specificity

The description states only 'applies to all HTML pages' and offers no concrete actions describing what the skill does; it never mentions auditing, checking, or fixing page titles.

1 / 3

Completeness

It provides 'when' triggers but entirely omits the 'what' — the skill's purpose of ensuring unique page titles is never stated, leaving the core capability missing.

1 / 3

Trigger Term Quality

Phrases like 'auditing a site crawl report' and 'multiple pages compete for the same keyword in search results' are reasonably natural, but the obvious terms 'page titles', 'title tags', and 'duplicate titles' are absent.

2 / 3

Distinctiveness Conflict Risk

The keyword-competition trigger is somewhat niche, yet 'applies to all HTML pages' is overly broad and, combined with no mention of titles, could match many SEO audit skills.

2 / 3

Total

6

/

12

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.