competitor-analysis

Use when the user asks to "analyze competitors" or "竞品分析"; benchmarks competitor keywords, content, backlinks, AI citations, and traffic share into strengths, weaknesses, and an action plan. Not for a pairwise topic-coverage gap map — use content-gap-analysis. 竞品分析/竞争对手

Quality

85%

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

Quality

Content

78%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.

Well-structured content with concrete tooling commands, clear decision gates, and excellent progressive disclosure to verified bundle files. The main weaknesses are minor verbosity in the data-sources section and analysis steps that stay high-level rather than fully executable.

Suggestions

Tighten the "Zero-dependency competitor fetch (keyless)" paragraph into a compact command list; the rationale about robots.txt pre-flight and free-tier credits can move to the connector README.

Make the 8 numbered analysis steps more executable by adding the specific metric/source to capture for each (e.g. exact fields to pull per step) or by linking each step to its template in analysis-templates.md.

Add an explicit validation checkpoint after synthesis (e.g. verify every strength/weakness cites a labeled metric and named competitor before writing the report) to close the validate→fix→retry loop.

Dimension	Reasoning	Score
Conciseness	Mostly lean and task-oriented without explaining concepts Claude already knows, but the "Zero-dependency competitor fetch" paragraph and Data Sources block are denser than needed and could be tightened.	4 / 5
Actionability	Provides executable commands (firecrawl.py scrape/map/search with arguments), a labeling scheme, and a concrete save path, but the 8 numbered analysis steps remain somewhat high-level rather than fully executable.	4 / 5
Workflow Clarity	A clear 8-step sequence is reinforced by Decision Gates (stop/continue) and a "Done when" completion checklist, but there is no explicit validate→fix→retry feedback loop for the analysis output.	4 / 5
Progressive Disclosure	SKILL.md is an overview with one-level-deep, clearly signaled references (analysis-templates, battlecard-template, example-report, positioning-frameworks — all verified present) and a dedicated Reference Materials section, giving easy navigation.	5 / 5
	Total	17 / 20 Passed

Description

92%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 strong, specific description with explicit what/when trigger guidance and a clear disambiguation boundary against a related skill. The only gap is modest coverage of English trigger-term variations beyond "analyze competitors".

Dimension	Reasoning	Score
Specificity	Lists multiple concrete benchmarking actions ("competitor keywords, content, backlinks, AI citations, and traffic share") and concrete outputs ("strengths, weaknesses, and an action plan"), matching the comprehensive-coverage anchor.	5 / 5
Completeness	Explicitly answers both what (benchmarks into strengths/weaknesses/action plan) and when ("Use when the user asks to 'analyze competitors' or '竞品分析'") with concrete trigger phrases, matching the top anchor.	5 / 5
Trigger Term Quality	Includes natural triggers users would say ("analyze competitors", "竞品分析", "竞品分析/竞争对手") with bilingual synonyms, but a few common English variations like "competitor research" or "benchmark competitors" are absent.	4 / 5
Distinctiveness Conflict Risk	Clear competitor-SEO/GEO niche with an explicit negative boundary ("Not for a pairwise topic-coverage gap map — use content-gap-analysis") that disambiguates it from a sibling skill, giving minimal conflict risk.	5 / 5
	Total	19 / 20 Passed

Validation

75%

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

Validation for skill structure

Criteria	Description	Result
metadata_field	'metadata' should map string keys to string values	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
relative_links	Relative link issues: 14 suspicious	Warning
referenced_paths_exist	Referenced path issues: 1 missing, 1 deeper-than-1-level	Warning

	Total	12 / 16 Passed

Repository: aaron-he-zhu/aaron-marketing-skills
Path: seo-geo/survey/competitor-analysis/SKILL.md
Commit: 9df28a0

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.