buyer-language-miner
Skill3 starsChanged 5 months agoMITView on GitHub
Mine reviews, threads, and support messages for the verbatim words buyers use about the problem you solve, organized into pains, triggers, desired outcomes, objections, and alternatives. Use before writing angles or copy; the best hooks are quotes.
In this repository15 other files it gives its agents.
- angle-writerSkill
- audience-builderSkill
- brand-readerSkill
- budget-pacerSkill
- catalog-commerceSkill
- competitor-ad-teardownSkill
- copy-formulasSkill
- creative-directorSkill
- daily-auditorSkill
- fatigue-detectorSkill
- lead-gen-builderSkill
- media-buyerSkill
- pain-to-promiseSkill
- performance-analystSkill
- pixel-conversionsSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 12
Before Angle Writer (its PAIN lines should come from here).
- Distinctive: line 13
Before writing any landing page or hook.
- Distinctive: line 36
Keep the source next to every quote.
- Distinctive: line 38
Do not mine only happy reviews.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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
Buyer Language Miner
Doctrine
The most persuasive line in your next ad has already been written, by a customer, in a review or a Reddit thread. Copy built from real buyer language outperforms invented copy because it passes the recognition test instantly: the reader thinks "that is exactly what I said." Marketers say "creative fatigue"; owners say "the exact same ads that cost $6.85 a lead now cost $30.90." Mine the second kind. This is also how you find the deeper pains buyers only admit anonymously.
When to use
- Before Angle Writer (its PAIN lines should come from here).
- Before writing any landing page or hook.
- Works with no MCP. Needs raw material: your reviews, competitor reviews, community threads, support emails, sales-call notes.
Run it
Mine this buyer language for my offer: [ONE-LINE OFFER + WHO YOU THINK IT IS FOR]
Raw material: [PASTE reviews / thread links / support emails / call notes. Include COMPETITOR reviews and community threads about the PROBLEM, not just about products.]
1. Extract verbatim quotes only (no paraphrasing) and sort into:
- TRIGGERS: the moment that started the search ("the day X happened...")
- PAINS: the problem in their words, especially emotional ("am I just stupid?")
- DESIRED OUTCOMES: what better looks like, in their words
- OBJECTIONS: why they hesitate or distrust ("everyone selling X says X works")
- ALTERNATIVES: what they do instead (DIY, a cheaper tool, nothing)
2. Mark the 5-10 BUYER-ISMS: the quotes so vivid they could be a hook or an on-image line as-is.
3. Note the words they NEVER use (jargon I should delete from my copy).
4. Map each strong pain quote to a possible angle: WHO said it, what PROMISE would answer it.Guardrails
- Verbatim means verbatim. A cleaned-up quote is a fabricated quote.
- Keep the source next to every quote. Public quotes can inspire copy; using someone's exact words in an ad may need permission and always needs judgment.
- Volume matters: one dramatic quote is an anecdote. Flag which pains repeat across many sources and which appeared once.
- Do not mine only happy reviews. Objections and alternatives are where the losing half of your funnel lives.
Good output looks like
Five labeled quote banks with sources, a starred buyer-ism shortlist, a jargon kill-list, and pain-to-angle mappings ready for Angle Writer.
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.

