Pull salesforce opportunity context
Salesforce AI assistant is an Agent Skill: a written method your AI applies on demand, in Zealos or in any client that reads SKILL.md.
Salesforce AI assistant is an Agent Skill: a written method your AI applies on demand, in Zealos or in any client that reads SKILL.md.
Pulling opportunity context is a summarisation problem with a trap: the useful answer is what changed and what is missing, not a recitation of fields the reader can already see.
| name | meddicc |
|---|---|
| description | The MEDDICC qualification framework and what each letter requires before a deal can advance. Use when assessing deal health, preparing a forecast, writing a deal review, or deciding whether a deal is real. |
| allowed-tools | none — this skill adds judgement, not reach |
| compatibility | Zealos, Claude Code, Cursor, Codex and any client that reads SKILL.md |
| license | Free to use and edit |
--- name: meddicc description: The MEDDICC qualification framework and what each letter requires before a deal can advance. Use when assessing deal health, preparing a forecast, writing a deal review, or deciding whether a deal is real. --- # MEDDICC A deal is qualified when every letter has evidence, not a guess. Say which letters are unevidenced rather than filling them in optimistically — a confidently-wrong qualification is worse than an obviously incomplete one. | | Requires | |---|---| | **M**etrics | A number the buyer stated, in their units. "Two days per rep per week", not "efficiency gains". | | **E**conomic buyer | A named person who can sign without asking anyone. If we have not spoken to them, say so. | | **D**ecision criteria | What they will compare us on, in their words and their order. | | **D**ecision process | The actual steps: security review, legal, procurement, board. With dates. | | **I**dentify pain | What breaks if they do nothing. If nothing breaks, there is no deal. | | **C**hampion | Someone who sells internally when we are not in the room, and who has something to gain. Tested by asking them to do something. | | **C**ompetition | Including "do nothing" and "build it ourselves", which win more often than any vendor. | ## How to report For each letter: **evidenced** (quote the source — call, email, note), **assumed** (say so), or **missing**. Then state the single highest-value unknown and the question that resolves it. One question, not a list. ## Red flags - Champion who will not introduce you to the economic buyer. - Metrics we authored rather than heard. - A decision process with no dates. - "Everyone loves it" with no named detractor. There is always a detractor.
Before a call you get what moved and what is missing, instead of a record dump you have to read like a diff by eye.
Deal inspection stops requiring you to open six tabs per opportunity to work out whether the stage is real.
Inconsistencies between stage and close date surface as a list rather than as a surprise in the last week of the quarter.
Yes. Describe your objects and what they mean in the skill body — it is documentation the model reads, so it adapts to your org.
If the agent has write tools enabled. Pair it with a field-conventions skill so anything written follows your rules.
The connected user's permissions apply. A skill never changes access; it only decides what to do with what the agent can already see.
Post-call automation turns a recorded conversation into the three things that outlive it: the commitments each side made, the fields that changed, and the follow-up that has to go out today.
/call-recap-formatAn AI SDR agent is only as good as the definition of a good customer it is working from, which is why the fit criteria belong in a written skill rather than buried in a prompt nobody can find.
/our-icpCRM data hygiene survives AI only if one rule is written down first: a field left blank is a known unknown, while a field filled in by inference is an unknown unknown that will be reported on as fact.
/crm-field-conventionsQualification is a claim about evidence, not a score: a deal is qualified when every criterion has a source you can quote, and unevidenced criteria are named rather than filled in optimistically.
/meddiccA pipeline review is useful in proportion to how uncomfortable it is: the job is to find the deals that are slipping quietly, not to narrate the ones everybody already knows about.
/meddiccA pricing objection is almost never about price: it is a value problem, a comparison to something cheaper that does less, or an internal conversation the buyer has not told you about yet.
/objection-handling