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 for content optimization.

Quality

70%

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

53%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 presents a coherent domain framework with concrete numeric targets and a well-specified output package, undermined by template boilerplate, redundant overlapping lists, and missing methodology for the core analytical steps. It reads as a scaffold that specifies what to produce but not how to perform or verify the key operations.

Suggestions

Delete the circular 'Use this skill when' / 'Do not use this skill when' / 'Instructions' boilerplate sections and merge Focus Areas, Approach, and Deliverables into one non-redundant flow.

Add concrete methodology for the core steps: the density formula, a technique for generating LSI keywords (e.g. co-occurrence extraction, related-search mining), and a worked example on a short sample paragraph.

Add a validation checkpoint to the workflow, e.g. "After suggesting placement, recompute density and revise until it falls within 0.5-1.5% with no stuffed sections."

DimensionReasoningScore

Conciseness

The circular boilerplate sections — "Working on seo keyword strategist tasks or workflows", "The task is unrelated to seo keyword strategist", "Clarify goals, constraints, and required inputs" — add no information, and Focus Areas, Approach, and Deliverables repeat the same items (density, LSI, over-optimization) three to four times. The core domain content is lean, so this is anchor 3 (mostly efficient but could be tightened) rather than anchor 2's pervasive padding.

3 / 5

Actionability

Concrete specs exist ("0.5-1.5% density", "20-30 semantic variations", "3-5 targets", and an output template), but the core value-adding operations have no method: how to generate LSI keywords, how to "Analyze competitor entity usage", and no worked example on real content. This matches anchor 3 (some concrete guidance but incomplete, missing key details); it is not anchor 4 because the gaps are central rather than minor.

3 / 5

Workflow Clarity

The 7-step Approach is clearly sequenced (extract → calculate → identify → determine intent → generate → distribute → flag), but there are no validation checkpoints (no re-check that suggested placement lands within 0.5-1.5%, no revise loop) and three competing step lists (Instructions, Entity Analysis Framework, Approach) dilute the sequence. This fits anchor 3 (sequence present, checkpoints missing); the destructive/batch cap does not apply since this is analysis-only.

3 / 5

Progressive Disclosure

There are no bundle files and none are needed at ~85 lines; sections are clearly headed and easy to navigate in a single file. Minor organization gaps — entity items ("Entity co-occurrence patterns") misfiled under Keyword Density Guidelines, and boilerplate sections diluting the structure — keep this at anchor 4 (good structure, minor gaps) rather than anchor 5's clean overview.

4 / 5

Total

13

/

20

Passed

Description

75%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 solid description that names the domain and several concrete capabilities in proper third-person voice, with an explicit Use clause. It is held back from excellent by a generic trigger clause and the absence of the most natural search terms (SEO, keyword research) and of the skill's full capability surface.

Suggestions

Make the 'when' clause concrete with trigger phrases, e.g. "Use when the user mentions SEO, keyword density, keyword stuffing, or asks to optimize content for search engines."

Add the natural trigger terms users actually say — "SEO", "keyword research", "search rankings" — alongside the existing LSI/semantic vocabulary.

Mention the entity analysis and search intent capabilities in the description so the 'what' fully covers what the skill does.

DimensionReasoningScore

Specificity

The description lists four concrete third-person actions — "Analyzes keyword usage", "calculates density", "suggests semantic variations and LSI keywords", "Prevents over-optimization" — but omits capabilities the skill actually performs (entity analysis, search intent) and "Prevents over-optimization" states an outcome rather than an action. This matches anchor 4 (several specific actions, minor gaps in coverage), falling short of anchor 5's comprehensiveness while clearly exceeding anchor 3's 1-2 actions.

4 / 5

Completeness

Both parts are explicitly present: a clear "what" (four named capabilities) and a "when" clause ("Use for content optimization"). The when is generic and lacks concrete trigger phrases, matching anchor 4 (both present, when could be more explicit) rather than anchor 5; the anchor-3 cap does not apply because an explicit Use clause exists.

4 / 5

Trigger Term Quality

Relevant keywords are present ("keyword usage", "density", "LSI keywords", "semantic variations", "content optimization") but the most natural user phrasings — "SEO", "keyword research", "search rankings" — are absent. This fits anchor 4 (good keyword coverage, a few natural terms missing) rather than anchor 3, since coverage goes well beyond a single domain mention.

4 / 5

Distinctiveness Conflict Risk

The capability list (density calculation, LSI keyword generation) carves out a clear niche, but the generic trigger "Use for content optimization" invites overlap with general content-writing or SEO skills. This matches anchor 4 (mostly distinct, minor overlap risk with closely related skills); it lacks anchor 5's distinct triggers.

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

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

rmyndharis/antigravity-skills

Path

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.