CtrlK
BlogDocsLog inGet started
Tessl Logo

competitor-analysis

Analyze one competitor's organic footprint, ranking keywords, content themes, backlinks, and gaps.

70

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

The canonical home for this skill is competitor-analysis in every-app/open-seo

SKILL.md
Quality
Evals
Security

Quality

Content

100%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 is a dense, well-structured instruction set: a routed goal, concrete inputs, project-context integration with exact write-back payloads, a tool catalog tied to a 10-step sequenced workflow with validation and failure handling, a precise output format, and evidence/inference guardrails. No dimension shows a meaningful weakness.

DimensionReasoningScore

Conciseness

The body is lean and entirely project-specific: tool names, filters, payload formats, report structure, and guardrails, with zero padding or explanation of concepts Claude already knows (no definitions of backlinks, SERPs, or SEO basics). Every section instructs rather than describes.

5 / 5

Actionability

For an instruction-only skill the guidance is fully concrete: named MCP tools with purpose per call, exact filter parameters ("maxRank, minSearchVolume, excludeBrandTerms, resultTypes"), concrete project-context payloads (an "addCompetitors" upsert and an appendResearchLog summary format), and a section-by-section output specification. This matches the fully-executable anchor under the instruction-skill scoring note.

5 / 5

Workflow Clarity

The 10-step workflow is explicitly sequenced with conditional branches (comparison, local SEO, unclear overlap), pre-flight validation (check the research log before spending credits, reuse results under 30 days old), assumption validation (find_serp_competitors, get_serp_results for head-to-head SERPs), and explicit degradation/failure handling ("Continue without backlink evidence if it is unavailable"; stop if seo-report is unavailable). This is an read-only analysis, so no destructive-operation cap applies.

5 / 5

Progressive Disclosure

No bundle files exist, and none are needed: the skill is self-contained with well-organized sections and no bulk reference material inlined. Cross-references to sibling skills (competitive-landscape, seo-report, seo-project-setup) are one level deep and clearly signaled, satisfying the well-organized-sections standard for skills that need no external references.

5 / 5

Total

20

/

20

Passed

Description

71%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 is concise, third-person, and specific about what the skill analyzes, with strong domain keywords. Its main weakness is the missing 'Use when...' trigger clause, which caps completeness at 3 and slightly limits trigger-term quality and distinctiveness.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user names a competitor and wants an SEO comparison of keywords, content, or backlinks."

Include the natural term "SEO" (and optionally "SERP" or "search rankings") so users searching for SEO competitor analysis match this skill.

Add a differentiator against general competitive/market research, e.g. mentioning organic search specifically, to reduce overlap risk with non-SEO competitor skills.

DimensionReasoningScore

Specificity

"Analyze one competitor's organic footprint, ranking keywords, content themes, backlinks, and gaps" names the domain and enumerates five concrete analysis targets covering the full scope of a competitor analysis, matching the comprehensive-coverage anchor rather than the score-4 anchor's 'minor gaps in coverage'.

5 / 5

Completeness

The 'what' is clearly stated (analyze organic footprint, keywords, themes, backlinks, gaps), but there is no 'Use when...' clause or equivalent explicit trigger guidance; per the judging guidelines a missing 'when' clause caps completeness at 3.

3 / 5

Trigger Term Quality

Terms like "competitor", "ranking keywords", and "backlinks" are natural phrases users would say, giving good keyword coverage, but common variations such as "SEO", "search rankings", or "SERP" are missing, so it does not reach the score-5 synonym-and-extension comprehensiveness.

4 / 5

Distinctiveness Conflict Risk

SEO-specific terms ("organic footprint", "ranking keywords", "backlinks") carve out a clear niche that distinguishes it from general analysis skills, but without the word "SEO" there is minor overlap risk with generic competitive-research or business-analysis skills.

4 / 5

Total

16

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
every-app/open-seo
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.