Content Gap Analysis
Compare your content coverage with competitors to prioritize missing topics, keyword opportunities, and editorial work.
The skill discloses inputs, optional external fetching, metric labels, and memory writes, and requires robots.txt compliance; however, it does not clearly specify user confirmation, rollback, sensitive-data boundaries, or recovery within this skill, so 11 points are deducted.
The procedure, stop conditions, output contract, and Estimated/N/A failure feedback are coherent; however, it depends on CLAUDE_PLUGIN_ROOT, Firecrawl, and shared scripts, and the supplied tests do not cover this skill's key paths, so 12 points are deducted within the static cap.
Triggers, competitor-relative scope, inputs, outputs, and the non-fit boundary for raw keyword-demand discovery are clear; evidence is limited for content-inventory variability, tool reachability, host differences, and complete mainland-China usability, so 5 points are deducted.
The skill provides frontmatter, versioning, Apache-2.0 licensing, quick starts, a contract, progressive workflow steps, templates, examples, limitations, and a next-skill handoff; maintenance ownership, changelog evidence, and update responsibility are not sufficiently clear, so 5 points are deducted.
The contract targets a prioritized gap brief with evidence, calendar entries, and metrics, and the templates are directly usable for structuring delivery; however, results depend on user data or external tools, and the supplied example and frameworks are not real execution evidence, so 9 points are deducted.
Metric provenance labels and the requirement to attach competitor and evidence details provide some auditability; however, there are no real execution records, independent corroboration, or dedicated tests covering this skill's key paths, so 6 points are deducted.
- Confirm authorization, privacy, and terms before using Firecrawl or other crawling integrations; overseas services may be unreachable from mainland-China networks.
- Memory writes create cross-session persistence; confirm scope, sensitive-data handling, and backup or rollback procedures before use.
- Retain sources for traffic, search volume, rankings, and AI-citation metrics, and do not present model estimates as measured data.
What does this skill do, and when should you use it?
This SEO/GEO survey skill analyzes content gaps relative to competitor websites. It identifies missing topics, keywords, formats, audience-journey coverage, and GEO opportunities such as definitions, Q&A, and comparison content. It produces an executive summary, prioritized Quick Wins / Strategic Builds / Long-term gaps, a dated calendar for Quick Wins, and success metrics. It requires competitor domains plus your own site or content inventory; demand-only keyword discovery belongs to keyword-research.
Reads your domain, competitor domains, topic or content-type focus, audience, business goals, and any supplied or tool-retrieved content inventory; audits your existing pages and compares competitor volume, formats, topic coverage, and unique assets; identifies keyword, topic-cluster, format, audience-journey, and GEO/AI gaps; prioritizes each gap with the covering competitor, metric labeling, and rationale; produces an executive summary, prioritized gap list, content calendar, and success metrics; and writes a reusable research summary to the specified memory/research/ path.
- A SaaS marketing team wants to compare its site with one to three close competitors before planning the next article batch.
- A content lead has an inventory of existing pages and needs to find competitor-covered topics and keywords that are missing from the site.
- An SEO team wants to identify content competitors published in the last six months that it has not covered.
- A GEO lead wants to find definition, Q&A, and comparison content competitors receive AI citations for.
- An editorial team needs to turn the highest-priority gaps into dated Quick Win assignments.
What are this skill's strengths and limitations?
- Requires every prioritized gap to name the competitor covering it and explain the evidence and business rationale.
- Covers keywords, topic clusters, content formats, audience journey stages, and GEO/AI content opportunities.
- Separates recommendations into Quick Wins, Strategic Builds, and Long-term work, with dated entries for Quick Wins.
- Can proceed without optional tools while labeling unavailable data as Estimated or N/A.
- Supports Claude Code and compatible Agent Skills hosts and uses the Apache-2.0 license.
- Cannot perform competitor-relative gap analysis without competitor domains.
- Cannot reliably establish missing coverage without your own site or content inventory.
- Traffic, volume, and trend evidence may be Estimated or N/A when connectors or exports are unavailable.
- The source provides no standalone test results, complete platform matrix, or full example-report contents for this skill.
- It does not perform raw keyword-demand discovery; the repository's keyword-research skill is the stated alternative.
How do you install this skill?
Install the repository collection first. In Claude Code, run /plugin marketplace add aaron-he-zhu/aaron-marketing-skills, then /plugin install aaron-marketing@aaron. On other Agent Skills-compatible hosts, run npx skills add aaron-he-zhu/aaron-marketing-skills, or clone it with git clone https://github.com/aaron-he-zhu/aaron-marketing-skills. The source does not document a dedicated generic-host installation command for this individual skill.
How do you use this skill?
Provide your site domain, one to three competitor domains, and optionally the topic scope, content types, audience, business goals, and current content inventory. Example: Find content gaps between my site https://example.com and https://competitor.com. You can also ask: What content am I missing compared to my top 3 competitors? If competitor domains or your own coverage data are unavailable, the skill asks for them instead of switching silently to demand-only keyword research.
How does this skill compare with similar options?
Compared with the repository's keyword-research skill, this skill finds competitor-relative coverage gaps; keyword-research is the stated option for demand-side keyword discovery.