CtrlK
BlogDocsLog inGet started
Tessl Logo

keyword-stuffing

Use when auditing content pages for over-optimisation, reviewing AI-generated content that may repeat target phrases excessively, or checking meta tags and alt text for unnatural keyword accumulation.

70

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

72%

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 well-organized, actionable instruction-only skill with a clean one-level reference to a real bundle file. Its main weaknesses are repeated facts across sections (hurting conciseness) and the absence of an explicit validation checkpoint in the audit/rewrite workflow (capping workflow clarity).

Suggestions

Deduplicate repeated facts: state the 2–3% density threshold once (in Check) and remove its restatement in Quick Reference; similarly consolidate the Panda/SpamBrain and 'natural language variation' mentions into one section.

Add an explicit validation checkpoint to the Fix workflow, e.g. after rewriting, re-run the density check from Code Review and confirm each flagged term now falls below the threshold before considering the page fixed.

DimensionReasoningScore

Conciseness

The body is mostly efficient with no padding of concepts Claude already knows, but key facts repeat across sections — the 2–3% density threshold appears in both Quick Reference and Check, 'natural language variation' recurs in Quick Reference/Fix/Explain, and Panda/SpamBrain repeat in Quick Reference and Explain. It is above the verbose anchor but below the lean one because of this verbatim redundancy.

2 / 3

Actionability

As an instruction-only skill it gives concrete, actionable guidance: explicit rewrite substitutions ('Instead of repeating "SEO best practices" 8 times, use: ...'), a specific alt-text replacement example, a DevTools CSS computed-styles check, and a Flesch Reading Ease test. Per scoring_notes, absent code is not penalized for instruction-only skills when guidance is this specific and copy-ready.

3 / 3

Workflow Clarity

Check (1–5 flagging criteria) and Fix (1–6 steps) are clearly numbered, but no explicit validation checkpoint or validate→fix→retry loop appears, so checkpoints are only implicit. It is not at 1 because the sequence is clear, and not at 3 because there is no explicit verification step.

2 / 3

Progressive Disclosure

The body serves as a concise overview and points to a single, clearly signaled one-level-deep reference ('see references/rule.md') that exists as a real 102-line file. Structure is well-organized into distinct sections matching the top anchor.

3 / 3

Total

10

/

12

Passed

Description

100%

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 well-crafted: it uses third person, names three concrete actions, leads with an explicit 'Use when...' trigger, and targets a distinct niche. Trigger terms are natural and varied, aligning closely with the rubric's high-quality examples.

DimensionReasoningScore

Specificity

Three concrete actions are named explicitly — 'auditing content pages for over-optimisation', 'reviewing AI-generated content that may repeat target phrases excessively', and 'checking meta tags and alt text for unnatural keyword accumulation'. This matches the top anchor listing multiple specific concrete actions rather than just naming a domain.

3 / 3

Completeness

It opens with an explicit 'Use when...' clause and embeds the what-it-does (audit/review/check) within the same sentence, clearly answering both what and when. It is not capped at 2 because an explicit trigger clause is present.

3 / 3

Trigger Term Quality

It uses natural terms a user would say — 'over-optimisation', 'AI-generated content', 'target phrases', 'meta tags', 'alt text', 'keyword accumulation' — covering common variations rather than relying on jargon.

3 / 3

Distinctiveness Conflict Risk

It targets a narrow SEO niche (keyword stuffing detection) with distinct triggers, making it unlikely to fire for unrelated skills. The specificity of the audit targets reduces overlap with generic content skills.

3 / 3

Total

12

/

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.