Install any skill in seconds. Free to start, no credit card required.
Get Started Free →mohitagw15856/client-discovery
Run a consulting client discovery session — uncover the real problem, scope, and decision process.
Passed 12 of 22 test cases with the skill, and 4 of 22 without it.
and 18 more in the full report
10 fixed2 passed either way8 still failing2 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 10 test cases the skill fixed. Same model, same prompt, with and without the skill.
I'm a freelance UX strategist meeting with an e-commerce company that says they want a complete store redesign after finding me on LinkedIn. I need to figure out project scope and whether to bid on this. Can you generate a complete discovery meeting plan for me? It should lay out the primary meeting goal, diagnostic questions to dig past the initial request into the actual problem, key qualification checks like budget and authority, success criteria, warning signs to watch out for, and a strategy for closing the call.
| Checked | Without skill | With skill |
|---|---|---|
| The response includes the top-level heading formatted exactly as ### Discovery Plan: [prospect name or placeholder]. | Missed | Passed |
| The response explicitly states the call objective is to qualify and uncover the real problem rather than pitch a solution. | Passed | Passed |
| The response includes the question asking what happens if they do nothing. | Missed | Passed |
The instructions your model reads when the skill loads.
The brief a client gives you is rarely the real problem — and the difference is where good consulting (and accurate scoping) lives. This skill preps a discovery session that gets beneath the stated ask to the actual problem, qualifies whether it's a fit (budget, authority, timeline), and pins the success criteria — so you scope and price accurately and write a proposal that lands.
Ask for these only if they aren't already provided:
1. The goal of the call — qualify + uncover the real problem + earn the right to propose. Not to pitch.
2. Get to the real problem — questions that move past the symptom to the cause and the stakes:
3. Qualify (fit) — surface, tactfully:
4. Success criteria — the concrete outcome that = success, in their terms. (This becomes the proposal's objectives.)
5. Red flags — watch for: no budget/authority, "just exploring," scope that balloons mid-call, shopping many vendors on price, unrealistic timeline. Note how to handle each.
6. Close & next step — how to summarise what you heard (confirm understanding) and set up the proposal ("I'll send a proposal with options by [date]").
test cases passed, vs 4 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.