pain-identifier
Skill0 starsChanged 47 days agoMITView on GitHub
Identify the top 5 buyer pains in the buyer's own language, ranked by urgency and frequency, pulled from won-deal call notes and records of prior outreach attempts. Use when the user wants "what actually hurts our buyer", "what pains should I lead with", "why do people buy this", or is about to write copy and needs the real pain to hook on. Writes the ranked pains into outreach-brief.md; these become the hooks for every cold email and call.
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
- competitor-finderSkill
- copywriting-first-touchSkill
- copywriting-follow-upSkill
- copywriting-linkedin-dmSkill
- deep-company-analyserSkill
- icp-definerSkill
- n8n-workflow-builderSkill
- offer-definerSkill
- outreach-strategistSkill
- 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
3 rules. About 0 are common, 1 is distinctive, and 2 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.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 14
If evidence is thin, say so and draw on the personas in outreach-brief.md, but mark guessed pains as unverified.
- Distinctive: line 20
Keep one verbatim line of buyer language per pain.
- Very specific: line 23
Write into section 6 (Top pains) of outreach-brief.md: the top 5 pains, ranked, each with the buyer's own words and a note on urgency and …
≈ “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
Pain Identifier
People don't buy features, they buy their way out of pain. This skill finds the real pains in the words buyers actually use, and ranks them so you lead with the one that bites hardest.
Input needed
- Won-deal call notes or transcripts, where the buyer described their problem.
- Notes from prior outreach: what got replies and what got ignored.
If evidence is thin, say so and draw on the personas in outreach-brief.md, but mark guessed pains as unverified.
Method
- Pull every moment a buyer described a problem, a frustration, a workaround, or a cost. Capture their exact words.
- Cluster into distinct pains and merge duplicates.
- Rank by urgency (how much it hurts, how soon) and frequency (how often it comes up). The top of the list is what you hook on.
- Keep one verbatim line of buyer language per pain.
Output
Write into section 6 (Top pains) of outreach-brief.md: the top 5 pains, ranked, each with the buyer's own words and a note on urgency and frequency. Lead-gen copy should open on pain #1 unless you have a sharper signal.
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.