CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

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

50%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 well-organized outline for an SEO keyword analysis skill that reads as a checklist of focus areas rather than an executable procedure. Its biggest defects are the broken reference to a nonexistent playbook file, missing execution detail (density formula, over-optimization thresholds), and boilerplate filler sections that add no value.

Suggestions

Fix the broken reference: 'resources/implementation-playbook.md' does not exist — either create the file (under references/) or remove the pointer.

Add concrete execution detail: the density formula ((keyword count / total words) x 100), explicit over-optimization thresholds that trigger warnings, and one worked example showing input content and the resulting Keyword Strategy Package.

Cut the tautological 'Use this skill when'/'Do not use' sections and the generic 'Clarify goals... Apply relevant best practices' bullets — they apply to any skill and earn no tokens.

DimensionReasoningScore

Conciseness

The core sections are lean, but padded boilerplate remains: tautological trigger sections ('Working on seo keyword strategist tasks or workflows'), generic instruction bullets ('Apply relevant best practices and validate outcomes'), a closing fluff line, and LSI-keyword guidance repeated across four sections. It avoids over-explaining known concepts, so it stays above anchor 2 but below anchor 4.

3 / 5

Actionability

Some concrete parameters exist (0.5-1.5% density target, '3-5 targets', '20-30 semantic variations', an output template), but key execution detail is missing: no density formula, no thresholds defining over-optimization, and 'Integration with SEO plugins' is a high-level hint rather than instruction. Guidance is present but incomplete, matching anchor 3.

3 / 5

Workflow Clarity

The 7-step Approach gives a clear sequence, but validation is only implicit ('Flag over-optimization issues', 'validate outcomes' with no mechanism or checkpoint). This is an analysis skill, so the destructive-operation cap does not apply, but the missing verification checkpoints hold it at anchor 3.

3 / 5

Progressive Disclosure

The body is well-sectioned and the reference is clearly signaled, but it points to 'resources/implementation-playbook.md', which does not exist in the bundle (no resources/ or references/ directory is present). The sole external pointer is broken, preventing a score of 4; the good section structure keeps it above anchor 2.

3 / 5

Total

12

/

20

Passed

Description

72%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 strong, specific description in third-person voice with an explicit proactive-use clause. Its main gaps are the missing 'SEO'/'search engine' trigger terms — the phrases users would most naturally say — and a generic rather than concrete 'when' clause.

Suggestions

Add the umbrella trigger terms users actually say — 'SEO', 'search engine', 'keyword research' — e.g. 'Use when the user mentions SEO, keyword density, or on-page optimization.'

Make the 'when' clause concrete: replace 'Use PROACTIVELY for content optimization' with specific trigger situations such as 'when reviewing or optimizing blog posts, landing pages, or marketing copy for search'.

Include the word 'SEO' at least once so the skill surfaces on the most common search-intent queries.

DimensionReasoningScore

Specificity

The description lists multiple concrete third-person actions — 'Analyzes keyword usage', 'calculates density', 'suggests semantic variations and LSI keywords', 'Prevents over-optimization' — covering the domain comprehensively, matching the top anchor.

5 / 5

Completeness

A clear 'what' is paired with an explicit when-clause ('Use PROACTIVELY for content optimization'), but the 'when' is generic rather than concrete trigger phrases like 'when the user mentions SEO or keyword density', so it does not reach anchor 5.

4 / 5

Trigger Term Quality

Relevant terms are present (keyword, density, LSI keywords, content optimization) but the most natural user phrases — 'SEO', 'search engine', 'keyword research' — are entirely absent. More than 'a few' natural terms are missing, so it sits below anchor 4.

3 / 5

Distinctiveness Conflict Risk

'keyword density' and 'LSI keywords' carve a distinct niche, but the broad phrase 'content optimization' creates minor overlap risk with general content-writing/editing skills.

4 / 5

Total

16

/

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

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

Path

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