CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

meta-description

Use when auditing page metadata or generating descriptions for new pages. Applies to every page that should receive organic search traffic.

Quality

72%

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/meta-description/SKILL.md
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 lean, well-structured body with actionable check/fix guidance and exemplary progressive disclosure to a real one-level reference. The main weaknesses are internal duplication and an internal contradiction between the 'Check' (120–160) and 'Code Review' (70–160) sections on the length criterion.

Suggestions

Merge 'Check' and 'Code Review' into one section — they duplicate each other and conflict on the length range (120–160 vs 70–160 characters).

State the 'not a ranking factor but improves CTR' point once (intro or Quick Reference) instead of three times across the body.

Add a brief post-fix re-validation step ('re-check length and uniqueness after writing the description') to close the workflow's feedback loop.

DimensionReasoningScore

Conciseness

The body is short and mostly tight, but 'Check' and 'Code Review' substantially duplicate each other, and the 'not a ranking factor but improves CTR' point is stated three times (intro, Quick Reference, Explain). This is more than anchor 4's 'minor instances that could be trimmed', fitting 'mostly efficient but could be tightened'.

3 / 5

Actionability

Concrete, executable guidance throughout: exact tag and location ('<meta name='description' content='...'> tag in <head>'), exact length range ('between 120 and 160 characters'), uniqueness and CTA criteria. Minor gap: 'Code Review' contradicts the rest with 'between 70 and 160 characters', leaving the bound ambiguous.

4 / 5

Workflow Clarity

The Check (validation) → Fix sequence with enumerated verification criteria fits 'clear sequence with most checkpoints present'. The simple-skill exception cannot grant a 5 because the single action is ambiguous — the two check sections give conflicting length bounds (120–160 vs 70–160) — and there is no post-fix re-validation step.

4 / 5

Progressive Disclosure

Under 50 lines with well-organized sections and a single clearly signaled, one-level-deep pointer ('For full implementation details, code examples, and framework-specific guidance, see references/rule.md' — verified to exist with no nested references). Content is appropriately split: overview/check/fix inline, code examples, framework guidance, and verification steps in the reference.

5 / 5

Total

16

/

20

Passed

Description

62%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 serviceable description with both a 'Use when' trigger and an applicability statement, but it under-specifies what the skill actually does and misses the most natural trigger terms ('meta description', 'SEO'). Distinctiveness is adequate though 'page metadata' is broader than the skill's true scope.

Suggestions

State the core function explicitly, e.g. 'Checks each page for a unique 120–160 character meta description and writes one when missing' — this adds specificity and separates 'what' from 'when'.

Include the natural trigger terms users would actually say: 'meta description', 'SEO', 'search results snippet'.

Narrow 'auditing page metadata' to 'auditing meta descriptions' to reduce overlap risk with sibling metadata skills (title tags, Open Graph).

DimensionReasoningScore

Specificity

Names the domain ('page metadata') and exactly two concrete actions ('auditing page metadata', 'generating descriptions for new pages'), but coverage is not comprehensive — the actual work of the skill (length, uniqueness, CTA criteria for meta descriptions) is never named.

3 / 5

Completeness

Both 'what' ('auditing page metadata or generating descriptions') and 'when' ('Use when...') are present with a concrete applicability clause. Not a 5 because the what is folded into the when-clause and the core function (checking/writing unique 120–160 character meta descriptions) is never explicitly stated as a capability.

4 / 5

Trigger Term Quality

Some relevant keywords exist ('page metadata', 'descriptions', 'organic search traffic'), but the most natural phrases a user would say — 'meta description', 'SEO', 'search snippet' — are missing. Fits 'some relevant keywords but missing common variations or synonyms' rather than anchor 4's fuller coverage.

3 / 5

Distinctiveness Conflict Risk

'Meta description / organic search traffic' framing carves a mostly distinct SEO niche, but 'auditing page metadata' is broader than meta descriptions alone and could overlap with closely related skills (title tags, Open Graph, other metadata rules). Not 5's 'clear niche with minimal conflict risk', but clearly above anchor 3.

4 / 5

Total

14

/

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