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.

48

Quality

51%

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/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

35%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This skill reads more like a role description or checklist overview than an actionable skill for Claude. It lacks concrete, executable guidance — no code for density calculation, no worked examples with real content, and no specific algorithms or tools. The content is padded with generic boilerplate and explanations of concepts Claude already knows, while missing the specific, actionable details that would make it useful.

Suggestions

Add a concrete, worked example showing actual content being analyzed with specific keyword density calculations, identified LSI keywords, and optimization recommendations — not just placeholder templates.

Remove generic boilerplate sections ('Use this skill when/Do not use this skill when', 'Clarify goals, constraints, and required inputs') and explanations of well-known SEO concepts that Claude already understands.

Provide executable code or a specific algorithm for calculating keyword density (e.g., a Python snippet or step-by-step formula) rather than just stating 'Calculate keyword density percentages'.

Add validation checkpoints in the workflow, such as: 'If primary keyword density exceeds 1.5%, identify specific sentences where keywords can be replaced with semantic variations' — concrete feedback loops rather than abstract flags.

DimensionReasoningScore

Conciseness

The skill contains significant padding: generic boilerplate sections ('Use this skill when', 'Do not use this skill when'), vague meta-instructions ('Clarify goals, constraints, and required inputs'), and explains concepts Claude already understands like what keyword density is and what LSI keywords are. The density guidelines and entity analysis framework are high-level descriptions rather than efficient, targeted instructions.

2 / 5

Actionability

The skill provides no executable code, no concrete commands, and no specific algorithms for calculating keyword density or generating LSI keywords. The 'Approach' section lists steps at a high level but doesn't explain how to actually perform them. The output template uses placeholders rather than worked examples. It reads more like a job description than actionable instructions.

2 / 5

Workflow Clarity

The 'Approach' section provides a 7-step sequence that is logically ordered, and the output section defines expected deliverables. However, there are no validation checkpoints, no feedback loops for when density is too high or too low, and no explicit error-handling steps for over-optimization detection beyond 'flag' it.

3 / 5

Progressive Disclosure

The skill references `resources/implementation-playbook.md` for detailed examples, which is good progressive disclosure. However, no bundle files are provided to verify this reference exists, and the main file itself contains content that could be better organized — the deliverables list, advanced recommendations, and platform integration sections feel like they belong in a separate reference file rather than inline.

3 / 5

Total

10

/

20

Passed

Description

67%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 does a reasonable job listing concrete capabilities around keyword analysis and optimization, establishing a clear domain. However, it lacks natural user-facing trigger terms (e.g., 'SEO', 'keyword research') and the 'when to use' guidance is too vague—'Use PROACTIVELY for content optimization' doesn't give Claude enough context to know when to select this skill over others.

Suggestions

Expand trigger terms to include natural user phrases like 'SEO', 'keyword research', 'keyword stuffing', 'on-page SEO', or 'search engine optimization'.

Replace the vague 'Use PROACTIVELY for content optimization' with specific trigger scenarios, e.g., 'Use when the user asks about keyword density, SEO optimization, keyword placement, or wants to improve content for search rankings'.

DimensionReasoningScore

Specificity

Lists several specific actions: analyzes keyword usage, calculates density, suggests semantic variations and LSI keywords, prevents over-optimization. Good coverage but could be more detailed about outputs or specific techniques.

4 / 5

Completeness

The 'what' is clearly stated with multiple concrete actions. The 'when' is present ('Use PROACTIVELY for content optimization') but is vague and lacks specific trigger scenarios—it doesn't describe what user requests or contexts should activate this skill.

4 / 5

Trigger Term Quality

Includes relevant terms like 'keyword', 'density', 'LSI keywords', 'semantic variations', and 'content optimization', but misses common user phrases like 'SEO', 'keyword stuffing', 'keyword research', or 'on-page optimization' that users would naturally say.

3 / 5

Distinctiveness Conflict Risk

The focus on keyword density analysis, LSI keywords, and semantic variations creates a fairly distinct niche in SEO/content optimization. Minor overlap risk with general content writing or SEO audit skills, but the specific mention of density calculation and LSI keywords helps differentiate.

4 / 5

Total

15

/

20

Passed

Validation

90%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

10

/

11

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.