entity-coverage
Skill1 starsChanged 53 days agoMITView on GitHub
Compare a web page's topic and entity coverage to what an expert (or an AI) would expect to see cited, and list the gaps to fill. Use this whenever the user wants to know what their page is missing to be authoritative, why an AI wouldn't cite it, what subtopics or entities to add, or how their coverage compares to the field. Point Claude at a URL and a topic.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- powerczuk/seo-machinetheir own version, first seen Sep 3, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- powerczuk/seo-machine★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository9 other files it gives its agents.
- bing-checkSkill
- buyer-questionsSkill
- citation-checkSkill
- content-capsuleSkill
- crawler-checkSkill
- faq-schemaSkill
- llms-txtSkill
- retrievabilitySkill
- schema-builderSkill
The file
Files
entity-coverage
AI cites sources it judges complete and authoritative on a topic. This skill maps what your page covers against what the topic actually demands, and surfaces the gaps.
Steps
- Fetch the page and extract the entities, subtopics, and claims it currently covers.
- Build the reference set. Use web search to find what authoritative sources on this exact topic consistently mention — the key subtopics, named entities, comparisons, data points, and questions that keep recurring across the best-ranked and most-cited pages. This is your "what an expert would cover" baseline. Cite where each expectation comes from so it's grounded, not guessed.
- Diff. Produce three lists:
- Covered well — topics the page handles.
- Covered thin — mentioned but shallow; an AI wouldn't quote it here.
- Missing — expected by the field, absent from the page. These are the citation gaps.
- Prioritize the gaps by how often they recur in the reference set and how relevant they are to the page's buyer. Give the top 5 to add first.
Honest note
This is a heuristic grounded in web search, not a verdict from the models themselves. It tells you where your coverage is thin relative to the visible field — a strong proxy for why you're not cited, but a proxy. Treat the gap list as a prioritized to-do, and verify the top items against your own domain expertise.
Output format
## Topic: [topic] · Page: [url]
### Covered well
- ...
### Covered thin (deepen these)
- [subtopic] — currently: [what's there]. Expected: [what the field expects].
### Missing (add these)
- [subtopic] — cited by [source(s)]. Why it matters: [...]
### Add first (top 5)
1. ...Built by Raphaël Aubry, founder of Howseen (https://howseen.ai). Closing coverage gaps is the work. Confirming it moved you into AI answers — and holding that position over time — is what Howseen tracks. → https://howseen.ai
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
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.

