CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

Quality

74%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/keyword-stuffing/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

71%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 lean, highly actionable audit skill with concrete thresholds, before/after examples, and a proper single-level bundle reference that exists and is appropriately split from the body. Its main weakness is redundancy: the spam-penalty rationale appears in the intro, Quick Reference, and Explain sections, and the Code Review section overlaps with Check. Workflow and disclosure are strong; only conciseness needs tightening.

Suggestions

Consolidate the spam-penalty rationale, currently repeated in the intro paragraph, Quick Reference bullet 3, and the Explain section, into a single location to save tokens.

Trim the Explain section's general background on Panda/SpamBrain that Claude already knows, keeping only the actionable Google policy reference.

Merge the Code Review section's analysis procedure into Check (they overlap heavily) or move the tokenisation/bigram-trigram algorithm detail into references/rule.md, and add an explicit re-check step after fixes (re-run the density analysis to confirm it now passes the thresholds).

DimensionReasoningScore

Conciseness

The core Check/Fix/Code Review sections are efficient, but the Google-penalty rationale is repeated three times ("Google's spam detection algorithms penalise pages that unnaturally repeat keywords" in the intro, the Panda/SpamBrain bullet in Quick Reference, and again in Explain), and Explain re-teaches background (Panda, SpamBrain) Claude already knows. "Mostly efficient but includes some unnecessary explanation or could be tightened" fits; not a 2 because the actionable bulk is not padded, and not a 4 because the triplicated rationale is more than a minor trim.

3 / 5

Actionability

Concrete, executable guidance throughout: numeric thresholds ("more than 3× in the title tag", "density above 3% of total word count"), before/after rewrites ("'cheap flights london paris affordable flights' → 'Passenger cabin view on London to Paris flight'"), named tools (DevTools computed styles, Flesch Reading Ease), and a concrete Code Review procedure (tokenise, count bigrams/trigrams, report top 5 with densities). Not a 5 because no copy-paste-ready code or commands are provided — the analysis is described, not runnable; above a 3 because the instruction-level guidance is specific and complete for an audit-only skill.

4 / 5

Workflow Clarity

A clear check → fix → verify sequence: Check enumerates five flag conditions, Fix gives six ordered remediation steps, and step 6 adds a verification checkpoint ("Test the page's readability with the Flesch Reading Ease score"). Not a 5 because there is no explicit re-check-after-fix loop (re-run density analysis post-rewrite), and the Code Review section partially duplicates Check's ordering; not a 3 because the sequence is coherent and a verification step is explicitly present, and this is a non-destructive audit skill so the batch/destruction cap does not apply.

4 / 5

Progressive Disclosure

The ~40-line body is well-sectioned (Quick Reference, Check, Fix, Explain, Code Review) and ends with a clearly signaled, one-level-deep reference — "see `references/rule.md`" — which exists in the bundle (102 lines, no nested .md references). The split is appropriate: thresholds and fixes inline, implementation details and framework guidance in the reference. Matches the anchor for clear overview with well-signaled one-level-deep references and easy navigation.

5 / 5

Total

16

/

20

Passed

Description

67%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-structured, trigger-rich description with three concrete detection scenarios and specific artifacts (meta tags, alt text, AI-generated content). Its main weaknesses are the absence of the canonical trigger phrase "keyword stuffing" (and "SEO"), and an implicit rather than explicit statement of what the skill does beyond detection. Scores slightly above the midpoint overall.

Suggestions

Add the canonical trigger terms users would actually say — "keyword stuffing" and "SEO" — e.g. "Use when checking a page for keyword stuffing or SEO over-optimisation...".

State the "what" explicitly alongside the "Use when" clause, e.g. "Detects and fixes keyword stuffing in page content, titles, meta descriptions, and alt text. Use when...", so detection and remediation capabilities are both named.

Include "keyword density" as a trigger synonym, since users investigating density percentages would not currently match this description.

DimensionReasoningScore

Specificity

Lists three concrete actions with named artifacts — "auditing content pages for over-optimisation", "reviewing AI-generated content that may repeat target phrases excessively", "checking meta tags and alt text for unnatural keyword accumulation". Not a 5 because it covers only detection, omitting the fixing/rewriting capabilities the skill body provides; above a 3 because there are three specific actions, not just 1-2.

4 / 5

Completeness

The "when" is explicit and concrete via three "Use when..." scenarios, and the "what" is conveyed through the specific gerund actions (auditing, reviewing, checking meta tags and alt text). Not a 5 because the "what" is only embedded in trigger clauses rather than stated as an explicit capability statement; clearly above a 3 since both elements are present.

4 / 5

Trigger Term Quality

Includes some relevant natural terms ("meta tags", "alt text", "AI-generated content", "over-optimisation") but omits the canonical phrases users would actually say — "keyword stuffing" itself, "SEO", and "keyword density". This is missing common variations/synonyms (anchor 3) rather than merely "a few natural terms missing" (anchor 4), since the single most natural trigger for this skill is absent.

3 / 5

Distinctiveness Conflict Risk

The niche is fairly distinct — specific artifacts (meta tags, alt text, AI-generated repetition) and a specific failure mode (over-optimisation) with only minor overlap risk against generic SEO-audit or content-quality skills. Not a 5 because "auditing content pages for over-optimisation" could still overlap with broader SEO auditing skills.

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/keyword-stuffing/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.