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.

50

Quality

55%

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 ./skills/seo-keyword-strategist/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

50%Weight 40%Scale 1-3

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

The skill is organized and reasonably efficient, but its guidance leans abstract and lacks validation checkpoints, leaving Claude without concrete, verifiable execution steps.

Suggestions

Remove the generic boilerplate instructions (goals/best-practices/verification lines) that are not specific to keyword strategy.

Add concrete methods or worked examples for the abstract steps (e.g., how to compute density from word counts, how to derive LSI terms from entities).

Insert a validation step in the workflow to re-check keyword density and flag over-optimization before producing the final package.

DimensionReasoningScore

Conciseness

The body is mostly lean and does not explain SEO basics Claude already knows, but it carries generic boilerplate ('Clarify goals, constraints, and required inputs', 'Apply relevant best practices and validate outcomes', 'Provide actionable steps and verification') that adds no skill-specific value.

2 / 3

Actionability

There is some concrete guidance (0.5-1.5% density targets, an output template, a numbered approach), but much of it is abstract ('Identify primary entity relationships', 'Build topical authority signals') without specific, executable methods.

2 / 3

Workflow Clarity

The Approach section provides a clear 7-step sequence, but there are no validation checkpoints or feedback loops to confirm density or over-optimization findings before delivering output.

2 / 3

Progressive Disclosure

The content is well-sectioned into logical areas, but it is a single ~85-line monolithic body with no bundle files and content that could be split (entity framework, output templates) kept inline.

2 / 3

Total

8

/

12

Passed

Description

60%Weight 40%Scale 1-3

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 clearly conveys what the skill does through specific actions, but its trigger guidance is generic and lacks the natural user-facing phrasings that would make it both complete and conflict-resistant.

Suggestions

Replace 'Use PROACTIVELY for content optimization' with an explicit 'Use when...' clause listing natural triggers (e.g., SEO keyword research, keyword density, search ranking optimization).

Add common user terms like 'SEO', 'search ranking', and 'keyword research' to broaden natural trigger coverage.

Sharpen the trigger so it clearly excludes general content writing to reduce overlap with other skills.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions: 'Analyzes keyword usage', 'calculates density', 'suggests semantic variations and LSI keywords', and 'Prevents over-optimization', matching the multi-action anchor.

3 / 3

Completeness

The 'what' is clearly stated, but the 'when' is only implied via 'Use PROACTIVELY for content optimization' rather than an explicit 'Use when...' clause with concrete user triggers, capping completeness at 2 per the guideline.

2 / 3

Trigger Term Quality

Relevant domain terms appear (keyword, density, LSI keywords, content optimization) but common natural phrasings users would say (SEO, search ranking, keyword research) are missing, and 'Use PROACTIVELY for content optimization' is generic rather than a natural trigger list.

2 / 3

Distinctiveness Conflict Risk

The SEO keyword-strategy niche is reasonably specific, but the generic 'content optimization' trigger could overlap with broader content or writing-skills, so it is not a fully conflict-free niche.

2 / 3

Total

9

/

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