seo-competitor

Run a competitive SEO analysis comparing the user's site to chosen competitors across SERP overlap, content depth, backlink profiles, technical posture, and brand presence. Use this skill whenever the user wants to analyze competitors, find content gaps, identify backlink opportunities, understand why competitors outrank them, or benchmark against the rest of their category. Triggers on competitor analysis, competitive analysis, SERP analysis, content gap, backlink gap, why is X ranking, who is winning the SERP, beat my competitor, benchmark, market positioning. Also triggers when planning a content strategy and the question 'what are competitors doing' is implicit.

Quality

75%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/seo-competitor/SKILL.md

Quality

Discovery

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This is a strong, well-crafted skill description that clearly defines what the skill does (competitive SEO analysis across five specific dimensions), when to use it (with an explicit 'Use this skill whenever' clause), and includes rich natural trigger terms covering both formal and conversational phrasings. The description is comprehensive without being padded, and it carves out a distinct niche that minimizes conflict risk with adjacent skills.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions: 'SERP overlap, content depth, backlink profiles, technical posture, and brand presence' — these are distinct, concrete analysis dimensions rather than vague language.	3 / 3
Completeness	Clearly answers both 'what' (run competitive SEO analysis across five named dimensions) and 'when' (explicit 'Use this skill whenever...' clause plus a detailed 'Triggers on' list covering many scenarios).	3 / 3
Trigger Term Quality	Excellent coverage of natural trigger terms including both formal ('competitive analysis', 'SERP analysis', 'content gap', 'backlink gap') and conversational phrases ('why is X ranking', 'who is winning the SERP', 'beat my competitor'). Also includes implicit trigger scenarios.	3 / 3
Distinctiveness Conflict Risk	The description carves out a clear niche around competitive SEO analysis specifically, with distinct triggers like 'SERP overlap', 'backlink gap', and 'why is X ranking' that are unlikely to conflict with general SEO or content strategy skills.	3 / 3
	Total	12 / 12 Passed

Implementation

50%

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

This is a well-organized SEO competitor analysis skill with a solid conceptual framework (5 angles) and clear workflow structure. Its main weaknesses are the lack of concrete, executable guidance (no specific tool commands, API calls, or worked examples) and missing validation checkpoints in the workflow. The referenced bundle files don't exist, undermining the progressive disclosure strategy.

Suggestions

Add concrete, executable examples: specific Ahrefs/Semrush API queries or CLI commands, example MCP tool calls, or a worked mini-example showing how to pull and compare data for one angle.

Add validation checkpoints to the workflow, e.g., 'Verify you have ranking data for at least 80% of priority keywords before proceeding to scoring' or 'Cross-check content gap findings against live SERPs to confirm accuracy.'

Create the referenced bundle files (references/competitive-audit-template.md and references/content-gap-method.md) and move detailed per-angle bullet lists into them to slim down the main SKILL.md.

Trim explanatory bullets that describe well-known SEO concepts (Core Web Vitals components, what branded search volume is) to just the metric names or checklist items.

Dimension	Reasoning	Score
Conciseness	Generally efficient and well-structured, but some sections explain things Claude already knows (e.g., what Core Web Vitals are, what HTTPS is, what branded search volume means). The 5-angle framework descriptions are somewhat verbose with bullet lists that could be tighter checklists.	2 / 3
Actionability	Provides a clear framework and structured approach, but lacks concrete executable commands, code snippets, or specific tool queries. Guidance is directional ('pull the data', 'use a keyword tool') rather than copy-paste ready. No specific API calls, CLI commands, or example queries are provided.	2 / 3
Workflow Clarity	The 7-step workflow is clearly sequenced and logical, but lacks validation checkpoints. There's no explicit verification step (e.g., 'confirm data completeness before scoring', 'validate gap findings against actual SERPs'). For a multi-step analytical process, the absence of feedback loops or quality checks is a gap.	2 / 3
Progressive Disclosure	References two external files (competitive-audit-template.md and content-gap-method.md) which is good progressive disclosure design, but neither file exists in the bundle. The main SKILL.md also includes substantial inline detail for all 5 angles that could potentially be split into reference files, making the main file longer than necessary.	2 / 3
	Total	8 / 12 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Repository: rampstackco/claude-skills
Commit: 8e70d03

Reviewed: 4 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.