CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

Quality

71%

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

61%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 compact, well-sectioned overview with concrete instruction-style guidance and a properly signaled single reference. Weaknesses are systematic redundancy between the intro and Explain sections (plus duplication with the reference file) and an implicit rather than explicit evaluate->fix->verify workflow with no stated verification checkpoint.

Suggestions

Delete the near-verbatim duplicate of the intro paragraph in the Explain section, or collapse them into one; let references/rule.md carry the full E-E-A-T background.

Make the workflow explicit by linking the sections (e.g., 'After applying fixes, re-run the Check and Code Review checklist to confirm gaps are closed'), turning Check -> Fix -> verify into a real loop.

Trim the Explain section's re-teaching of what E-E-A-T stands for, since Claude already knows the acronym and its meaning.

DimensionReasoningScore

Conciseness

The body is mostly efficient, but the intro paragraph ('Google's Search Quality Rater Guidelines and Helpful Content system reward pages... low-quality pages are algorithmically suppressed site-wide') is repeated nearly verbatim in the Explain section, and Explain re-teaches E-E-A-T basics Claude already knows. The redundancy is systematic rather than a minor trim, so it sits at anchor 3 rather than 4.

3 / 5

Actionability

Fix gives a concrete numbered prescription ('Identify the primary search intent... (1) fully satisfy that intent, (2) add specific details, examples, or data... (4) add author byline with relevant credentials') and Code Review enumerates six checkable dimensions (word count, specificity, authorship, freshness, sources, originality). This is an instruction-only skill, so the absence of code is not penalized; minor gaps (e.g., no word-count thresholds inline) keep it at 4 rather than 5.

4 / 5

Workflow Clarity

Check, Fix, and Code Review form an implicit evaluate -> remediate -> verify sequence, but the sections are never connected as a sequence and the verification loop (re-check after fixing) is implicit. This matches the anchor 'steps listed but validation gaps; checkpoints missing or implicit' rather than the anchor 4 example with explicit validate/verify steps.

3 / 5

Progressive Disclosure

The ~45-line body is well-sectioned (Quick Reference, Check, Fix, Explain, Code Review) and points to a clearly signaled, one-level-deep reference (references/rule.md, confirmed to exist). It is not 5 because body content (the intro and E-E-A-T explanation) duplicates the reference's 'Why It Matters' and E-E-A-T sections instead of deferring all detail to the reference.

4 / 5

Total

14

/

20

Passed

Description

70%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 well-formed description with an explicit 'Use when' trigger and good natural page-type keywords. Its main weakness is a thin 'what' half: the capability is a single generic action ('evaluating') folded into the trigger clause rather than a list of concrete actions.

Suggestions

State the 'what' as its own concrete capability before the trigger, e.g., 'Audits content pages for E-E-A-T and thin-content signals and prescribes fixes. Use when...'

Add natural trigger synonyms users would say, such as 'content quality', 'thin content', or 'helpful content', to improve keyword coverage.

DimensionReasoningScore

Specificity

The description names the domain ('content pages for SEO quality') and a single action ('evaluating'), matching the anchor 'names domain and 1-2 concrete actions, but not comprehensive'. It does not list several concrete actions (e.g., what the evaluation covers or any fix/report capability), so it falls short of 4.

3 / 5

Completeness

The explicit 'Use when evaluating content pages for SEO quality' clause answers 'when' clearly, and the 'what' (evaluating content pages for SEO quality, applied to listed page types) is present. Not 5 because the 'what' is embedded in the trigger sentence rather than stated as its own concrete capability statement; not 3 because the 'when' is explicit, not weakly implied.

4 / 5

Trigger Term Quality

Natural page-type triggers are present ('blog posts', 'product descriptions', 'landing pages', 'organic search traffic') alongside 'SEO quality', giving good keyword coverage. Common variations users would say ('content quality', 'thin content', 'helpful content', 'E-E-A-T') are missing, so it is not the comprehensive anchor 5.

4 / 5

Distinctiveness Conflict Risk

The description carves a clear SEO content-quality niche with distinct page-type triggers, so it is mostly distinct. Minor overlap risk remains with sibling SEO-audit or content-writing skills that could also trigger on 'content' requests.

4 / 5

Total

15

/

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