CtrlK
BlogDocsLog inGet started
Tessl Logo

quality

Use when evaluating content pages for SEO quality. Applies to blog posts, product descriptions, landing pages, or any page expected to receive organic search traffic.

62

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/quality/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

57%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-organized, appropriately disclosed SEO-content skill whose body leans on a real one-level reference. Its weaknesses are conceptual redundancy with knowledge Claude already has, an abstract Check phase with deferred details, and a Check→Fix workflow that lacks a verification checkpoint.

Suggestions

Trim or remove the 'Explain' section's restatement of E-E-A-T and Google's ranking systems — Claude already knows these; keep only the non-obvious framing specific to this skill.

Add a verification step after 'Fix' (e.g., re-run the Check/Code Review checklist and confirm each previously-identified gap is resolved before finishing) to give the workflow an explicit validation loop.

Make the 'Check' step more concrete by tying it to the same named signals used in 'Code Review' (word count, specificity, authorship, freshness, sources, originality) instead of the generic 'Identify specific quality gaps' instruction.

DimensionReasoningScore

Conciseness

The 'Explain' section restates E-E-A-T ('Experience, Expertise, Authoritativeness, and Trustworthiness') and Google's ranking systems — concepts Claude already knows — and Quick Reference/Check/Fix/Explain/Code Review cover overlapping ground. This matches the score-2 anchor 'Mostly efficient but includes some unnecessary explanation'; it is not a 1 because the content is sectioned and reasonably tight rather than a padded wall of text.

2 / 3

Actionability

The Fix section gives 5 concrete steps and Code Review a 6-point checklist, but the Check step ('Identify specific quality gaps') is abstract evaluation direction and full implementation is deferred to references/rule.md. This matches 'Some concrete guidance but incomplete... missing key details'; it is not a 3 because the body is not self-contained actionable guidance and the Check phase stays abstract.

2 / 3

Workflow Clarity

A Check→Fix sequence is present, but there is no validation or verification checkpoint confirming the fixes actually raised content quality. This matches 'Steps listed but validation gaps; sequence present but checkpoints missing or implicit'; it is not a 3 because no explicit validate/re-check feedback loop is provided.

2 / 3

Progressive Disclosure

The body is a concise, well-sectioned overview (Quick Reference, Check, Fix, Explain, Code Review) with a single clearly signaled, one-level-deep reference ('see references/rule.md', which exists on disk). This matches the score-3 anchor 'Clear overview with well-signaled one-level-deep references'; it is not a 2 because the reference is genuinely one level deep and appropriately split, not nested or buried.

3 / 3

Total

9

/

12

Passed

Description

90%

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, well-structured description with an explicit 'Use when' trigger, natural SEO-domain keywords, and a clearly distinct niche. Its only weakness is specificity: it conveys a single concrete action (evaluating) rather than enumerating multiple specific actions.

DimensionReasoningScore

Specificity

The description names the domain ('SEO quality', 'content pages') and one concrete action ('evaluating'), but lists no second concrete action beyond evaluating — matching the score-2 anchor 'Names domain and some actions, but not comprehensive.' It is not a 3 because there is not a list of multiple specific concrete actions, only a single evaluating action.

2 / 3

Completeness

It opens with an explicit 'Use when evaluating content pages for SEO quality' trigger and states what the skill does (evaluating content pages for SEO quality), clearly answering both what and when. It is not a 2 because the 'when' is explicit via the 'Use when...' clause rather than merely implied.

3 / 3

Trigger Term Quality

'SEO quality', 'blog posts', 'product descriptions', 'landing pages', and 'organic search traffic' are natural terms an SEO-focused user would actually say, giving good coverage. It is not a 2 because it goes beyond a single relevant keyword to cover multiple common variations users would mention.

3 / 3

Distinctiveness Conflict Risk

'SEO quality' combined with specific page-type triggers (blog posts, product descriptions, landing pages) carves a clear niche unlikely to fire for unrelated skills. It is not a 2 because the SEO-quality scoping keeps it from broadly overlapping with general content-review skills.

3 / 3

Total

11

/

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.