CtrlK
BlogDocsLog inGet started
Tessl Logo

seo-keyword-strategist

Analyzes keyword usage in provided content, calculates density, suggests semantic variations and LSI keywords based on the topic. Prevents over-optimization. Use PROACTIVELY for content optimization.

55

Quality

62%

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 ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/seo-keyword-strategist/SKILL.md

The canonical home for this skill is seo-keyword-strategist in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

57%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 well-organized and reasonably lean, with a clear analysis sequence and a useful output template. It is held back by missing validation checkpoints, abstract rather than executable density/LSI guidance, and a broken reference path.

Suggestions

Add explicit validation steps to the workflow, e.g. verify computed density against the 0.5-1.5% target and flag any over-optimization before finalizing output.

Fix the reference path to match the bundle (use 'references/implementation-playbook.md' or create the referenced file), or remove the reference if no detail file exists.

Provide a concrete method or small code snippet for calculating keyword density and extracting LSI candidates so guidance is directly executable.

DimensionReasoningScore

Conciseness

Sections are short bullet lists and mostly token-efficient, though Focus Areas, Entity Analysis, and Approach overlap conceptually and the density guidelines mildly restate known practice; minor trimming would reach 5.

4 / 5

Actionability

Provides specific density targets (0.5-1.5%), a numbered approach, and an output template with quantities, but no concrete method or code to compute density or generate LSI keywords, leaving key execution details implicit.

3 / 5

Workflow Clarity

The Approach section gives a clear 7-step sequence, but there are no explicit validation/verification checkpoints for a batch analysis task; 'validate outcomes' is vague, so the cap applies.

3 / 5

Progressive Disclosure

Content is well-organized into short sections, but the single reference points to 'resources/implementation-playbook.md' which does not exist in the bundle, so navigation is not clearly valid.

3 / 5

Total

13

/

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.

The description is specific and distinguishable, naming several concrete actions and an explicit (if generic) trigger clause. Its main weakness is trigger-term quality: the phrasing leans on jargon and the awkward 'Use PROACTIVELY' rather than natural user language.

Suggestions

Rewrite the trigger clause as a natural 'Use when...' sentence listing phrases users actually say, e.g. 'Use when optimizing content for SEO, researching keywords, or checking keyword density.'

Add common synonyms and terms users employ (SEO, search ranking, keyword research, on-page optimization) to broaden trigger coverage.

Replace the directive 'Use PROACTIVELY for content optimization' with concrete trigger conditions to lift completeness toward 5.

DimensionReasoningScore

Specificity

Lists several concrete actions ('Analyzes keyword usage,' 'calculates density,' 'suggests semantic variations and LSI keywords,' 'Prevents over-optimization') with only minor coverage gaps, fitting the 'several specific actions' anchor above the midpoint.

4 / 5

Completeness

Has a clear 'what' (the enumerated actions) and an explicit 'when' clause ('Use PROACTIVELY for content optimization'), but the 'when' is generic rather than tied to concrete trigger phrases, sitting between the 3 and 5 anchors.

4 / 5

Trigger Term Quality

Relevant keywords (keyword density, LSI keywords, content optimization) are present but common natural phrasings users say (SEO, search ranking, keyword research) and synonyms are missing, and 'Use PROACTIVELY' is non-natural phrasing.

3 / 5

Distinctiveness Conflict Risk

Carves a clear SEO-keyword-strategy niche with mostly distinct triggers and only minor overlap risk with general content-editing 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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
administrakt0r/AI-Agents-Safe-Coding-Skills
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.