CtrlK
BlogDocsLog inGet started
Tessl Logo

word-count

Use when applies to key landing pages, blog posts, product pages, and any page targeting competitive queries. Use when diagnosing poor rankings or after a Google Helpful Content update.

52

Quality

58%

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

Quality

Content

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

The content is a lean, well-structured overview with concrete actionable guidance and a clean one-level-deep reference to rule.md. Its main weakness is the lack of explicit validation/verification checkpoints in the Check→Fix workflow.

Suggestions

Add an explicit verification step after Fix, e.g. 'Re-count body words on flagged pages to confirm they now exceed the threshold and re-compare depth to the top 3 ranking pages.'

Specify a concrete way to count visible body words (e.g. a command or selector excluding nav/header/footer) so the Check step is fully executable.

DimensionReasoningScore

Conciseness

The body is efficient with well-scoped sections, though the intro sentence and the 'Explain' section restate concepts (e.g. why word count alone is invalid) that could be trimmed slightly.

4 / 5

Actionability

It gives concrete actionable guidance — 'Flag pages under 200 words of unique body content', 'compare depth to the top 3 ranking pages', 'Add noindex' — and as an instruction-only skill the absence of code is acceptable; minor gaps remain in specifying word-count tooling.

4 / 5

Workflow Clarity

The Check→Fix→Explain→Code Review sections give a rough sequence, but there are no explicit validation checkpoints (e.g. 're-check word count after expansion' or 'confirm rankings/depth improved'), leaving checkpoints implicit.

3 / 5

Progressive Disclosure

The body is a clear, well-sectioned overview that points one level deep to references/rule.md for full implementation details, with the reference clearly signaled at the end and the bundle file present.

5 / 5

Total

16

/

20

Passed

Description

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

The description has decent natural trigger terms but is missing any statement of what the skill actually does, and its opening phrasing ('Use when applies to') is grammatically broken and action-less. It needs a concrete third-person 'what' clause to reach completeness.

Suggestions

Add a 'what' clause stating the skill's concrete actions, e.g. 'Audits key pages for thin content, flags pages under ~200 words, and recommends expansion or noindex strategies.'

Fix the broken opening 'Use when applies to' by leading with a third-person verb describing the skill's function.

Consolidate the two 'Use when' clauses into a single tighter trigger list to reduce redundancy.

DimensionReasoningScore

Specificity

The description names the SEO domain ('key landing pages, blog posts, product pages') but states no concrete actions — there is no verb describing what the skill does, only 'Use when applies to', which is even thinner than the anchor 'Processes PDF files'.

2 / 5

Completeness

It provides only 'when' guidance (two 'Use when...' clauses) with no 'what' clause describing the skill's function, matching the anchor 'only when is present without what'.

2 / 5

Trigger Term Quality

It includes natural SEO terms a user would actually say — 'landing pages', 'blog posts', 'product pages', 'competitive queries', 'poor rankings', 'Google Helpful Content update' — giving good keyword coverage with only a few synonyms missing.

4 / 5

Distinctiveness Conflict Risk

The Helpful Content update and page-type triggers are somewhat specific, but the skill is one of many SEO checklist rules and could overlap with sibling SEO skills targeting similar pages.

3 / 5

Total

11

/

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.

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.