CtrlK
BlogDocsLog inGet started
Tessl Logo

meta-description

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

64

Quality

76%

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

85%

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 lean, well-structured overview that delegates detail to a real one-level reference and gives concrete, actionable check/fix guidance. Its main weakness is redundancy across the intro, Quick Reference, and Explain sections plus overlap between Check and Code Review.

Suggestions

Collapse the repeated 'not a ranking factor but improves CTR' point into a single mention.

Merge or differentiate the Check and Code Review sections to remove duplicated verification steps.

Reconcile the conflicting length ranges (120–160 in Check vs 70–160 in Code Review) so the validation criterion is consistent.

DimensionReasoningScore

Conciseness

Mostly efficient and well-sectioned, but the 'not a ranking factor / click-through rate' point is repeated in the intro, Quick Reference, and Explain, and the Check and Code Review sections overlap substantially, so it could be tightened.

2 / 3

Actionability

Provides a copy-paste tag template ('<meta name=\'description\' content=\'...\'>'), a concrete length range, and a specific 5-point Code Review checklist — fully actionable guidance for an instruction skill.

3 / 3

Workflow Clarity

A simple single-task skill with an unambiguous Check → Fix sequence and an explicit validation/flagging step ('Flag pages where it is missing, duplicated, or outside the recommended length').

3 / 3

Progressive Disclosure

Short, well-organized overview with a single clearly-signaled one-level-deep reference ('see references/rule.md') that exists and holds the detailed code examples.

3 / 3

Total

11

/

12

Passed

Description

67%

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 concise, third-person, and answers both what and when with an explicit trigger clause. It is held back by limited trigger-term coverage and a domain scope broad enough to risk overlap with sibling SEO skills.

Suggestions

Add natural trigger terms users actually say, e.g. 'meta description', 'SEO snippet', or 'search result description'.

Narrow the domain from 'page metadata' to 'meta description tags' to reduce conflict risk with title-tag or Open Graph skills.

DimensionReasoningScore

Specificity

Names the domain ('page metadata', 'descriptions') and two actions ('auditing', 'generating') but is not comprehensive, matching the 'names domain and some actions' anchor.

2 / 3

Completeness

Explicitly states what it does ('auditing page metadata or generating descriptions') and when to use it via an explicit 'Use when...' / 'Applies to...' clause, answering both what and when.

3 / 3

Trigger Term Quality

Includes 'page metadata' and 'descriptions' but omits natural variations users would say like 'meta description', 'SEO', or 'search snippet', fitting 'some relevant keywords but missing common variations'.

2 / 3

Distinctiveness Conflict Risk

'Page metadata' is somewhat broad and could overlap with adjacent SEO skills (title tags, open graph), fitting 'somewhat specific but could still overlap with similar skills'.

2 / 3

Total

9

/

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.