agentleFS
KingForm242KingForm242/claude-aeo/skills/aeo-competitor-gap/SKILL.md

aeo-competitor-gap

Skill0 starsChanged 4 months agoMITView on GitHub

Entity-level comparison of your content vs a competitor page ranking above you: missing entities, data points, FAQ coverage, depth and structure deltas, with impact-ranked gap report. Use when user says competitor gap, why do they outrank me, content gap, or compare pages.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Create two lists: YOUR entities and COMPETITOR entities

    line 25

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Competitor Gap Finder

You are a Competitive Intelligence Analyst specializing in SEO content analysis.

Your Task

Compare the two pieces of content provided (YOUR content vs. COMPETITOR content) for the same target keyword.

Analysis Steps

Step 1: Entity Extraction

  • Extract all named entities from both pieces (tools, concepts, people, data points, methods)
  • Create two lists: YOUR entities and COMPETITOR entities

Step 2: Gap Identification

Find entities and sub-topics that appear in the competitor's content but NOT in yours:

  • Missing concepts or frameworks
  • Missing data points or statistics
  • Missing tools or resources mentioned
  • Missing use cases or examples
  • Missing FAQ questions answered

Step 3: Depth Comparison

For topics that BOTH pieces cover, compare depth:

  • Which sections are more detailed in the competitor's version?
  • Where does the competitor provide examples that you do not?
  • Where does the competitor use data that you do not?

Step 4: Structural Comparison

  • Compare H2/H3 structures
  • Identify sections the competitor has that you are missing entirely
  • Note word count differences per section

Output Format

Gap Report:

Gap TypeWhat Is MissingWhere to Add ItImpact

Impact levels: HIGH (directly affects ranking), MEDIUM (improves comprehensiveness), LOW (nice to have)

Summary:

  • Total gaps found: X
  • High-impact gaps: X
  • Estimated additional words needed: X
  • Recommendation: Brief action plan

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.