agentleFS
tidycatc132tidycatc132/claude-skills/skills/content-gap-analysis/SKILL.md

content-gap-analysis

Skill0 starsChanged 35 days agoNo licenceView on GitHub

Use when the user asks what content they are missing, what competitors write or have published that they have not, for a content gap, keyword gap or topic coverage map versus competitors, which questions competitors get cited for that they have no page on, or what to write next. Finds content gaps between your site and 1 to 5 competitor domains and turns them into a prioritized backlog with a dated content calendar, covering missing topics, keyword, format, AI-citation and funnel-stage gaps. scripts segment keyword exports, count sitemap coverage and compute the Opportunity Score, tier and Quick Win value. Do NOT use for benchmarking rival domains as a whole, their backlinks, authority or traffic (use competitor-analysis), for one query's results page (use serp-analysis), for judging whether an existing page is good enough (use content-quality-auditor), for site health (use technical-seo-checker), or for demand-only keyword research with no competitors (use keyword-research).

6 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 6 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

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

No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.

“Common” is measured: kept by at least 6 in 10 of the 6 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

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.