CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

duplicate-description

Use when auditing a site's meta tag uniqueness, generating page-specific meta descriptions, or reviewing CMS templates that inject the same description globally.

Quality

81%

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

SKILL.md
Quality
Evals
Security

Quality

Content

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

A well-structured, actionable overview with excellent progressive disclosure through a single valid one-level reference. The main cost is redundancy: the same Google-snippet rationale is repeated across the intro, Quick Reference, and Explain sections, padding the token budget without adding guidance Claude doesn't already have.

Suggestions

State the Google-rewrites-duplicate-snippets rationale once (either the intro or the Explain section) and cut the other two occurrences — the intro paragraph, the second Quick Reference bullet, and the Explain section currently repeat the same idea.

Add a concrete mechanism for the Check step, e.g. a grep/curl one-liner or sitemap-crawl command to collect rendered `<meta name="description">` values across routes, and an explicit post-fix step to re-run it and confirm uniqueness.

Trim the Explain section to one sentence or move it into `references/rule.md`, since it mostly restates general SEO knowledge Claude already has.

DimensionReasoningScore

Conciseness

The Google-rewrites-snippets rationale is stated three times ("Google ignores them and generates its own snippet" in the intro, "Google may auto-generate snippets when descriptions are duplicated" in Quick Reference, and the whole Explain section), and that rationale is SEO knowledge Claude already has. This is more than the minor trimmable over-explanation of level 4, but the Check/Fix/Code Review sections themselves are lean, so it does not fall to level 2.

3 / 5

Actionability

The Fix section gives concrete, near-executable guidance ("pass a dynamic `description` prop through your SEO component", "disable site-wide description fallback in your SEO plugin (Yoast, RankMath)", "50–160 characters") plus example descriptions. It falls short of level 5 because the Check step ("Scan the HTML of every page") provides no concrete mechanism or command for performing the scan.

4 / 5

Workflow Clarity

The Check → Fix → Code Review sequence is clear and the Code Review section supplies a validation checkpoint ("Check that no two `<meta name="description">` tags... share identical `content` values"). It is not level 5 because that verification is not framed as an explicit post-fix re-check feedback loop for what is a batch edit across many pages, and not level 3 because a concrete checkpoint is present.

4 / 5

Progressive Disclosure

The body is a well-organized overview (Quick Reference, Check, Fix, Explain, Code Review) that delegates depth via a single clearly signaled, one-level-deep pointer: "For full implementation details, code examples, and framework-specific guidance, see `references/rule.md`" — a file that exists and itself contains no further nested skill references. This matches the level-5 anchor.

5 / 5

Total

16

/

20

Passed

Description

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

A strong third-person description with concrete, comprehensive actions and an explicit trigger clause. Its only weaknesses are the absence of the most natural user phrasings ("duplicate meta descriptions", "SEO") and the fusion of what and when into one clause rather than separate statements.

DimensionReasoningScore

Specificity

The description lists three concrete actions — "auditing a site's meta tag uniqueness", "generating page-specific meta descriptions", and "reviewing CMS templates that inject the same description globally" — which comprehensively cover the skill's check/fix/review capabilities. This matches the level-5 anchor (multiple specific concrete actions, comprehensive coverage) rather than level 4, since no capability of the skill is left uncovered.

5 / 5

Completeness

The "when" is explicit ("Use when auditing... generating... or reviewing...") and the embedded gerunds state the "what" concretely, but there is no standalone what-statement as in the level-5 example ("Extract text and tables from PDF files... Use when..."). It is above level 3 because both what and when are present and specific, just fused into a single clause structure.

4 / 5

Trigger Term Quality

Natural trigger phrases like "meta tag uniqueness", "page-specific meta descriptions", and "CMS templates" give good keyword coverage, but the most common user phrasings — "duplicate meta descriptions" and "SEO" — are absent. This fits the level-4 anchor (good coverage, a few natural terms missing) better than level 3, since coverage goes well beyond a single generic keyword.

4 / 5

Distinctiveness Conflict Risk

The description carves out a clear niche (meta description uniqueness in SEO/CMS contexts) with distinct triggers like "meta tag uniqueness" and "inject the same description globally", making it unlikely to fire for unrelated skills. Minimal conflict risk matches the level-5 anchor.

5 / 5

Total

18

/

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/duplicate-description/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.