CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

Quality

68%

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

78%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 body is a well-structured, actionable audit skill: concrete thresholds, a coherent Check/Fix/Explain/Code Review flow, and clean progressive disclosure to a real one-level reference file. Weaknesses are minor — some repetition of the word-count-isn't-everything point and no validation checkpoint for the batch fix operations.

DimensionReasoningScore

Conciseness

The body is lean and checklist-like with concrete thresholds, but the point that word count alone does not define thin content is repeated in the intro, Quick Reference bullets 1 and 4, and the Explain section, and the bullets restate Google Helpful Content guidance Claude already knows. This is 'efficient with minor instances of over-explanation that could be trimmed' rather than a 3, since the redundancy is limited and nothing is heavily padded.

4 / 5

Actionability

Guidance is concrete and executable for an instruction-only skill: "count visible body text words (excluding navigation, headers, footers)", "Flag pages under 200 words of unique body content", "compare depth to the top 3 ranking pages", "Add `noindex` to thin utility pages". It stops short of a 5 because no method or tool is given for actually counting words or comparing competitor depth — those steps are named but not carried out.

4 / 5

Workflow Clarity

A clear Check → Fix → Explain → Code Review sequence with explicit thresholds in the Check step and verification guidance in the Code Review section ("describe how to verify the final page output"). Not a 5 because the Fix step includes batch-ish site changes ("Remove or consolidate thin pages", "Add `noindex`") with no validation checkpoint after applying them.

4 / 5

Progressive Disclosure

The ~45-line body keeps an overview in SKILL.md with well-organized sections (Quick Reference, Check, Fix, Explain, Code Review) and a single, clearly signaled, one-level-deep pointer to `references/rule.md` ("For full implementation details, code examples, and framework-specific guidance, see references/rule.md"), which exists and contains the detailed rule content. This matches the anchor for a clear overview with well-signaled references.

5 / 5

Total

17

/

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 strong, natural trigger phrases for SEO contexts but fails at its core job: it never states what the skill does. It is two 'Use when' clauses with no capability statement, omits the skill's own topic terms (thin content, word count), and risks conflicting with sibling SEO ranking-diagnosis skills.

Suggestions

Lead with a 'what' statement in third person before the triggers, e.g. "Counts visible body-text words on key pages and flags thin content (<200 words) that risks underperforming in search."

Add the skill's central topic terms — "thin content", "word count", "SEO" — to the trigger clause so users asking about those match this skill instead of sibling SEO skills.

Fix the broken opening phrase "Use when applies to key landing pages" — replace it with a proper action verb ("Use when auditing key landing pages...") so the sentence describes a trigger context grammatically.

DimensionReasoningScore

Specificity

The description names the domain ("key landing pages, blog posts, product pages", "competitive queries", "Google Helpful Content update") but contains no capability actions at all — "Use when applies to" is not an action verb, and the skill never says what it does. This matches the anchor 'names the domain but actions are minimal or generic'; it is not a 3 because no concrete action like 'counts words' or 'flags thin pages' is ever stated, and not a 1 because the trigger contexts are concrete rather than purely abstract.

2 / 5

Completeness

Only 'when' is present, without any 'what': the description consists of two "Use when..." trigger clauses and never states what the skill actually does (assess word count / identify thin content). Anchor 2 explicitly covers 'only when is present without what'; it cannot be a 3 because that anchor requires a clear 'what', and the trigger detail, while explicit, does not substitute for a capability statement.

2 / 5

Trigger Term Quality

Good natural keyword coverage — "key landing pages", "blog posts", "product pages", "diagnosing poor rankings", "after a Google Helpful Content update" are phrases users would naturally say. It falls short of a 5 because the skill's central terms ("thin content", "word count", "SEO") are entirely absent, so a user asking about thin content or word count would not match this description.

4 / 5

Distinctiveness Conflict Risk

The description is somewhat specific to page-level SEO, but "diagnosing poor rankings" and "any page targeting competitive queries" would equally trigger sibling SEO skills (backlinks, metadata, content quality), and the missing 'what' removes the main disambiguator. It overlaps with similar skills without being clearly distinct, matching anchor 3.

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.

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/word-count/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.