client-discovery
Skill1 starsChanged 4 months agoMITView on GitHub
Market research before any copy or strategy — mines customer voice (real reviews), competitors and a defensible differentiator, producing docs/discovery.md. Use PROACTIVELY when writing site/landing copy and docs/discovery.md does not exist, when the user asks for "discovery", "market research", "customer voice", or when the ABOUT.md brief is too shallow to support copy that converts.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- impeto-ai/claude-skills-impetotheir own version, first seen May 18, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- impeto-ai/claude-skills-impeto★ 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 repository3 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- design-directionSkill
- landing-blueprintSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
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 17
Read ABOUT.md: client, segment, audience, primary conversion, tone.
- Distinctive: line 18
Ask the user (AskUserQuestion, one round only):
- Distinctive: line 65
If no real differentiator exists, SAY SO in the document: the strategy becomes competing on clarity, proof and response speed — never …
≈ “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
Client discovery — raw material before copy
Killer copy is not born from imagination: it is born from the audience's real phrases, real
objections and a real differentiator. This skill turns the 5-line brief from ABOUT.md into
docs/discovery.md — the mandatory input for the copywriter and the landing blueprint.
Timebox: 60–90 min of research. Endless discovery is procrastination dressed up as diligence. Collect, synthesize, move on.
Step 0 — Inputs
- Read ABOUT.md: client, segment, audience, primary conversion, tone.
- Ask the user (AskUserQuestion, one round only):
- Who are the top 3 competitors? (if unknown, you find them in Step 2)
- Is there existing client material? (testimonials, surveys, sales-call recordings, current site)
- What does the client THINK their differentiator is?
Step 1 — Customer voice (the heart of the skill)
Mine LITERAL phrases from the audience. Sources, via WebSearch/WebFetch:
- The client's own reviews: Google Maps, Trustpilot, G2, app stores.
- Competitors' reviews (their unmet pains are your argument).
- Reddit, forums, YouTube comments in the niche — search "[niche] worth it", "[niche] experience", "how to solve [problem]".
- Market-specific sources: see
.claude/locales/<language>.mdwhen the project Language has one — it lists the review platforms and channels that matter in that market.
What to extract from each source (with literal quote + link):
- Pains — what they complain about, in their exact words ("slow to reply", "hidden pricing").
- Desires — the dream outcome, as they describe it.
- Objections — why they hesitate before buying ("will this work for my case?").
- Language — what they call things (does the audience say "consultation" or "assessment"? "site" or "page"?).
Golden rule: literal quote > paraphrase. The headline that converts has almost always already been written by a customer in a review.
Client with no online presence (new business)? Replace with a guided interview with the user: 5 questions — who is the ideal customer who would buy today; what have they tried before; what would make them say no; what do competitors promise; what concrete result in 90 days.
Step 2 — Competitors (3 to 5)
For each one, open the landing/site (Playwright if available, otherwise WebFetch) and record:
| Field | What to note |
| Hero promise | Literal headline |
| Offer and CTA | What they ask for and how |
| Social proof | Which kind they use (numbers, logos, testimonials) and how specific |
| Pricing | If visible, how much and how they anchor it |
| Apparent weakness | What's missing, what's generic, recurring complaint in the reviews |
Step 3 — Defensible differentiator
Cross-reference: what the client has × what the audience wants × what competitors don't deliver. A differentiator only counts if it passes the test: a competitor could NOT say the same sentence tomorrow. "Quality and service" fails; "48-hour delivery with tracking" passes.
If no real differentiator exists, SAY SO in the document: the strategy becomes competing on clarity, proof and response speed — never inventing a fake differentiator.
Output — docs/discovery.md (fixed format)
# Discovery — [client] ([date])
## Audience
Who they are + how they talk (3-5 lines, with the niche-term glossary)
## Pains (top 5, with literal quotes and source)
## Desires / dream outcome (with quotes)
## Objections (top 5) + honest answer to each
## Competitors (Step 2 table)
## Defensible differentiator (or "parity — compete on clarity and proof")
## Candidate copy angles (3, one paragraph each)Anti-patterns
- Inventing a pain or testimonial the research didn't find — the document only contains what has a source.
- Paraphrasing everything into "marketing language" — kills exactly the value of the research.
- Copying the strongest competitor's promise (if they already own it, you arrive second).
- Researching for 4 hours — timebox blown = synthesize with what you have and note the gaps.
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.

