SkillCompetitor Gap Audit
Turn your own competitor notes into one ranked gap report: what rivals offer that you do not, ordered by a documented score — plus the features only you have.
Works with: Claude Code, Codex, Cursor, Muse · Version 1.0.0 · Needs: Your notes: mine.txt (your features) and competitors.txt ([Competitor] blocks with features and optional review-mention counts).
Get this Skill with Premium See plans
Preview
Sample output
An example of what this Skill produces. Sample content, shown for illustration.
Competitor Gap Audit report — sample Your features: 3 | Competitors audited: 2 | Gaps found: 3 Gaps, ranked: 1. SSO login — score 37 (2 competitors, 17 mentions); 2. Mobile app — score 30 (1 competitor, 20 mentions); 3. Slack integration — score 18 (1 competitor, 8 mentions). Your edges: Dark mode, API access. Covered: CSV export (case-insensitive match against a competitor's 'csv export'). Errors: 0. Warnings: 0.
What you get
- A ranked gap report: score, competitor count, and review mentions per gap
- Your edges: features no competitor in your notes has
- Covered features you share with at least one competitor
- Every input error and warning named in the report
About this Skill
Reads two plain-text files you write — mine.txt (your features, one per line) and competitors.txt (one [Name] block per rival, each feature with an optional review-mention count) — and produces gap-report.md: gaps ranked by score (review mentions + 10 per competitor offering the feature), your edges, covered features, and every input error and warning. Matching is case-insensitive; duplicates keep their first spelling; dropped lines are named, never hidden. Local-only, standard library only; nothing is scraped or inferred — a gap is a prompt to investigate, not proof users want it.
Try it
Audit my product against Acme and Beta from these notes — what gaps should I investigate first?Good fit
- Deciding what to build next from evidence you collected
- Turning a pile of competitor screenshots and reviews into one triage list
- Checking a launch checklist against named rivals before shipping
Not for
- Scraping competitor sites or reviews — you supply the notes
- Proving users want a gap feature — a high score means rivals offer it, not demand
- Judging the whole market — rivals you did not write down do not appear
How to install
- Copy the install prompt into your agent:
Read https://skillu.dev/install/agent.md, then install the Competitor Gap Audit skill (competitor-gap-audit). - Or download the Skill package from this page after launch and place its folder in your agent’s skills directory.
- Call it with a slash command, e.g.
/competitor-gap-audit, and describe what you want in plain words.
FAQ
How is a gap scored?
Score = review mentions + 10 per competitor offering the feature. A gap ranks higher when more rivals offer it and reviewers mention it more. It is a triage order for investigation, not a demand forecast.
What happens if my notes have errors?
The report still runs on the usable parts and lists every problem: lines before any [Competitor] block, non-numeric mention counts, duplicate blocks and features, and competitors with no usable lines. Dropped lines are named, never silently ignored.