competitor-analysis

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

Quality

66%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/competitor-analysis/SKILL.md

Quality

Content

72%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 content is well-structured and highly actionable with concrete tooling and a clear output format, with only minor redundancy and absent output-validation keeping it from the top tier.

Suggestions

Consolidate tool usage so each tool's purpose appears in one place, reducing the duplication between the MCP tools list and the workflow steps.

Add an explicit verification step to the workflow (e.g., cross-check keyword-theme claims against SERP evidence before producing the final plan) to strengthen workflow clarity.

Tighten the output-format section into a concise template so the expected deliverable is unambiguous.

Dimension	Reasoning	Score
Conciseness	The body is lean and free of concept over-explanation, but each MCP tool is named twice — once in the tools list and again in the workflow — which could be tightened.	2 / 3
Actionability	It names exact MCP tools and concrete filters (maxRank, minSearchVolume, excludeBrandTerms, resultTypes) plus a defined output table, giving fully actionable instruction-only guidance.	3 / 3
Workflow Clarity	The 10-step workflow is clearly sequenced with useful conditional branches, but it lacks an explicit validation/verification step for the analysis output, leaving checkpoints implicit.	2 / 3
Progressive Disclosure	The skill is a single, well-sectioned file with no nested or external references, and its size does not warrant splitting, matching the well-organized single-file anchor.	3 / 3
	Total	10 / 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 is specific and action-oriented but omits explicit 'when to use' trigger guidance and leans on some domain jargon, leaving it solidly mid-tier rather than exemplary.

Suggestions

Add an explicit 'Use when...' clause naming natural user triggers (e.g., 'Use when analyzing a specific competitor's keywords, backlinks, or content strategy').

Replace or supplement the jargon term 'organic footprint' with common phrasings a user would actually say, such as 'organic search traffic'.

Add a one-line disambiguator distinguishing this from the sibling competitive-landscape skill to reduce conflict risk.

Dimension	Reasoning	Score
Specificity	The description lists multiple concrete actions — 'organic footprint, ranking keywords, content themes, backlinks, and gaps' — rather than vague language, matching the top anchor.	3 / 3
Completeness	It clearly states what the skill does but lacks any 'Use when...' or equivalent explicit trigger guidance, which per the guidelines caps completeness at 2.	2 / 3
Trigger Term Quality	Terms like 'ranking keywords' and 'backlinks' are natural, but 'organic footprint' is jargon and common variations a user might say are missing, so it sits at the middle anchor.	2 / 3
Distinctiveness Conflict Risk	It targets a specific SEO competitor niche, but the body reveals a sibling 'competitive-landscape' skill, so overlap with similar skills remains a risk.	2 / 3
	Total	9 / 12 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: every-app/open-seo
Path: .agents/skills/competitor-analysis/SKILL.md
Commit: f569726

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.