competitor-finder
Skill0 starsChanged 47 days agoMITView on GitHub
Map the competitive landscape from competitor names and deal notes, what each alternative is strong and weak at, the landmine questions that expose their gaps, and scripts for handling them when a prospect raises them. Use when the user says "who do we compete with", "how do I handle [competitor]", "build a battlecard", or is prepping outreach or calls against known alternatives. Writes the landscape into outreach-brief.md. Always include "do nothing" as a competitor.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- vicfromthegtmclub/gtmskillstheir own version, first seen Aug 10, 2026
- l3mpire/claude-skillstheir own version, first seen Apr 13, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- l3mpire/claude-skills★ 9same name
- vicfromthegtmclub/gtmskills★ 1same 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 repository15 other files it gives its agents.
- cold-call-scriptSkill
- copywriting-first-touchSkill
- copywriting-follow-upSkill
- copywriting-linkedin-dmSkill
- deep-company-analyserSkill
- icp-definerSkill
- n8n-workflow-builderSkill
- offer-definerSkill
- outreach-strategistSkill
- pain-identifierSkill
- persona-definerSkill
- pipeline-analyserSkill
- reply-rate-analyserSkill
- tam-sam-som-sizerSkill
- value-prop-listerSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is 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.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 21
Always include do nothing / status quo as a competitor, because it's the one you lose to most.
- Very specific: line 24
Write into section 7 (Competitive landscape) of outreach-brief.md: a block per alternative with the four parts above.
≈ “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.
Files
Competitor Finder
Deals are won and lost against alternatives, including "do nothing." This skill maps the real competitive field and arms you with questions and handling, not trash-talk.
Input needed
- Names of competitors and alternatives, including spreadsheets, in-house builds, and the status quo.
- Deal notes where competitors came up, won or lost.
Method
For each alternative:
- What it's genuinely good at, be honest; pretending it's weak gets you caught.
- Where it falls short for your ICP specifically.
- A landmine question, a fair question you can plant that makes the prospect notice that gap themselves. That lands harder than you attacking it.
- Handling script, a short, calm response for when a prospect says "we're looking at [X]" or "we already use [X]."
Always include do nothing / status quo as a competitor, because it's the one you lose to most.
Output
Write into section 7 (Competitive landscape) of outreach-brief.md: a block per alternative with the four parts above.
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.