Plan a short discovery call around the buyer's problem, decision process and next step without making it an interrogation. This download gives an assistant a concrete input, output and check, so its answer can be inspected rather than accepted on faith.
Download the free skill
A Markdown SKILL.md file. No sign-up. Read the inputs and boundaries before using it with your data.
Download SKILL.mdWhat to provide
Buyer role, stated reason for the call, known account facts from a permitted source, time available and product limitations.
What the assistant does
Choose six to eight open questions in a natural order: current process, trigger, impact, attempted fixes, success criteria, stakeholders, timeline and next step. Pair each with why it matters and what evidence would change the plan. Skip questions already answered in the thread.
The output you can check
The skill returns a table with these fields:
question | reason | known answer | follow-up if vague | note to confirm | not asked
A worked example
A fictional buyer says spreadsheet handoffs lose approvals. Ask "Where does the handoff usually stall?" before pitching automation. Do not infer budget or decision authority from a job title.
How to verify the result
Rehearse for the booked call length; check facts against the actual thread; capture only information shared with permission and leave unanswered fields blank.
Limits
The example is fictional. This skill does not invent search volume, customer evidence, prices or approvals. A plan is not a published page, a sent message or a change to an account. Missing source data stays marked as unknown.
Read the underlying method, or browse other sales skills. The keyword "sales discovery questions" had an estimated 260 US average monthly searches in a public keyword tool when this topic was chosen; this is directional demand, not a traffic promise.