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

52%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/seo-keyword-strategist/SKILL.md

Quality

Content

46%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 skill body is well-structured and concise but largely template-generated and generic, offering little executable guidance — density thresholds are stated but no formula or tooling is given, and the output is a placeholder template. It reads more like a topic outline than an actionable procedure.

Suggestions

Make density calculation executable: provide the actual formula (uses / total words * 100) and a concrete example with numbers rather than just stating '0.5-1.5% density'.

Replace abstract Approach steps with concrete, copy-paste-ready instructions or a worked example (sample input content -> computed densities -> suggested LSI keywords).

Remove the generic boilerplate under 'Instructions' ('Clarify goals...', 'Apply relevant best practices...') which adds no skill-specific value.

Dimension	Reasoning	Score
Conciseness	The body is not padded with concept explanations Claude already knows, but generic boilerplate ('Clarify goals, constraints, and required inputs', 'Apply relevant best practices and validate outcomes') adds little value and could be trimmed.	3 / 5
Actionability	Guidance is high-level and abstract — 'Extract current keyword usage', 'Calculate keyword density percentages' — with no formulas, no code, no tools, and the output template uses placeholder tokens like '[keyword]', leaving the specific executable steps missing.	2 / 5
Workflow Clarity	A 7-step 'Approach' sequence is present, but it has no validation checkpoints or error-recovery feedback loops; the destructive/batch cap does not apply (this is an analysis task), so it lands at the 'steps listed, checkpoints missing' anchor.	3 / 5
Progressive Disclosure	A single short file (~85 lines) with clearly labeled sections (Focus Areas, Density Guidelines, Entity Analysis, Approach, Output) and good navigability; no external bundle files are referenced, so the simple-skill structure is largely appropriate.	4 / 5
	Total	12 / 20 Passed

Description

58%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 states concrete capabilities clearly but relies on a weak, directive 'when' clause ('Use PROACTIVELY') rather than natural, explicit trigger phrases. It is specific and distinct but incomplete on the invocation-guidance axis.

Suggestions

Replace 'Use PROACTIVELY for content optimization' with an explicit trigger clause naming natural phrases, e.g. 'Use when the user asks for SEO keyword research, keyword density analysis, or LSI/semantic keyword suggestions for content.'

Add the most common user-facing synonyms ('SEO', 'search ranking', 'keyword research') to broaden trigger-term coverage.

Consider mentioning entity/topical-authority analysis in the description since it is a focus area in the body.

Dimension	Reasoning	Score
Specificity	Names several concrete actions — 'Analyzes keyword usage', 'calculates density', 'suggests semantic variations and LSI keywords', 'Prevents over-optimization' — which is several specific actions with only minor gaps (e.g., entity analysis is omitted).	4 / 5
Completeness	The 'what' is clear (keyword analysis, density, LSI suggestions) but the 'when' is only weakly implied via 'Use PROACTIVELY for content optimization' rather than an explicit trigger clause, which caps completeness at 3.	3 / 5
Trigger Term Quality	Includes relevant terms ('keyword', 'density', 'LSI keywords', 'content optimization') but misses common natural phrases users say ('SEO', 'rank', 'search terms') and 'Use PROACTIVELY' is a directive rather than a natural trigger.	3 / 5
Distinctiveness Conflict Risk	The keyword-strategy / SEO-optimization niche is mostly distinct with only minor overlap risk against general content-writing or broader SEO skills.	4 / 5
	Total	14 / 20 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: rmyndharis/antigravity-skills
Path: skills/seo-keyword-strategist/SKILL.md
Commit: 3eff4af

Reviewed: 7 days ago

Table of Contents

Discovery Implementation Validation

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.