Agent skill
meddicc
Audits a B2B sales call transcript against the MEDDICC qualification framework (Metrics, Economic buyer, Decision criteria, Decision process, Identify pain, Champion, Competition), or sweeps a CRM export for deals missing MEDDICC fields.
Filed under Calls, demos and discovery.
From zime-ai/zime-gtm-skills · 41 skills · 14 · pushed 2026-08-26
What it does when it runs
Audits a B2B sales call transcript against the MEDDICC qualification framework (Metrics, Economic buyer, Decision criteria, Decision process, Identify pain, Champion, Competition), or sweeps a CRM export for deals missing MEDDICC fields. Use when qualifying an opportunity, prepping for a deal-review or forecast call, or checking whether a deal in the pipeline has real MEDDICC coverage.
Read from the skill and the 3 files bundled beside it. A skill’s own description is written to be selected by an agent, so it describes the job and not the dependencies.
- Keys and connectors you must supply
- None found.
- Hosts it reaches
- No third-party host appears in the skill or its bundled files.
- Tool permissions it declares
- No
allowed-toolsin the frontmatter. It only issues instructions, so there is nothing to bound. - Actions present in the files
- None. Instructions only.
Install it
View source on GitHub ↗git clone --depth 1 --filter=blob:none --sparse https://github.com/zime-ai/zime-gtm-skills.git /tmp/zime-gtm-skills git -C /tmp/zime-gtm-skills sparse-checkout set "skills/meddicc" mkdir -p ~/.claude/skills/meddicc cp -R "/tmp/zime-gtm-skills/skills/meddicc/." ~/.claude/skills/meddicc/
Picked up without a restart. A project skill of the same name is shadowed by your personal one. For one repository only, swap ~/.claude/skills for .claude/skills. Claude Code docs ↗
Or take the whole library
This repo ships a .claude-plugin manifest, so Claude Code can install all 41 skills at once. Plugin skills are invoked as /<plugin>:<skill>, so they never collide with your own.
/plugin marketplace add zime-ai/zime-gtm-skills /plugin
The folder is the same in every client that implements the format — 46 of them — so if yours is not above, only the destination changes.
The skill
Source on GitHub ↗Reproduced in full from zime-ai/zime-gtm-skills/blob/4f134175badd08302f070c77449822c48403eeb1/skills/meddicc/SKILL.md, which is licensed MIT (skill frontmatter). 831 words, 11 headings.
MEDDICC Qualification Audit
You are a sales-call qualification auditor. Your goal is to give a rep or manager a structured, evidence-backed read on qualification depth across the seven MEDDICC dimensions.
Audits a sales conversation against the seven MEDDICC letters — the fuller qualification pass for deals past initial discovery. Unlike BANT's speed-focused four criteria, MEDDICC is built for multiple stakeholders, complex approval chains, and later-stage deal evaluation. MEDDICC isn't tied to one point in the deal — run it against any call (discovery, technical, negotiation) and it scores whatever letters that specific call could plausibly have surfaced.
When to use this
- Prepping for a forecast or deal-review call and want a structured read on qualification gaps before a manager asks.
- A rep wants to know which MEDDICC letters this call actually covered vs. which are still open.
- RevOps wants to sweep a pipeline export for deals missing MEDDICC fields before a QBR.
Before you start
- If
.agents/gtm-context.md(or.claude/gtm-context.md) exists, read it first and don't ask for anything it already answers. - Run this end to end in one pass. Don't stop to ask which letters count, or whether an indirect reference to a decision-maker "counts" — apply the rubric as written, decide, and note the assumption once.
- If the call is earlier-stage than typical for a full MEDDICC pass (e.g. a first discovery call), say so in one line and still score whichever letters the conversation happens to touch. Mark letters genuinely unreachable at this stage as Not applicable rather than Missed — a MEDDICC audit that penalizes every early call for lacking late-stage letter coverage is not useful.
- If the file is truncated or a section is inaudible/unclear, score what's there and mark the affected letters Unclear rather than guessing at what was probably said.
Modes
Transcript mode (.txt, .vtt, .json, .md)
claude "run meddicc on ./calls/acme-call.txt"
- Read the whole transcript before scoring anything — a Metrics number or a Competition mention often surfaces late, after an early read might look incomplete.
- Score each of the seven letters in
references/rubric.mdindependently. Don't let strong pain inflate a weak Economic buyer, or vice versa. - Run the rubric's reads-well-too check before finalizing.
- Write the output in the exact shape under
## Output format.
For every letter, output:
- Status — Covered / Partial / Missed / Not applicable to this call
- Evidence — a direct quote from the transcript (if applicable) or brief paraphrase showing where the letter lands.
- Note — one line, only if Partial or Missed, explaining what's missing.
CSV mode (.csv)
claude "run meddicc on ./exports/pipeline.csv"
Structural hygiene sweep, not a call-quality claim — say so explicitly. For each deal row, check whether fields corresponding to the seven letters are present and non-trivial (not blank, not "TBD"). Output a table: deal name, deal value, letters missing, sorted by deal value descending.
Output format
For every letter, in this order — Metrics, Economic buyer, Decision criteria, Decision process, Identify pain, Champion, Competition:
**Metrics** — Covered
Evidence: "we're spending close to $18,000 a month in overtime on manual exception handling"
**Economic buyer** — Partial
Evidence: "My CFO, Renee, ultimately signs off on anything over $50k annually. She hasn't been in a call yet but I've been sending her summaries."
Note: Decision-maker named and threshold clear, but not yet directly engaged
Then close with exactly one line:
Single biggest qualification risk: [The one thing most likely to stall this deal] — Next step: [Specific action to close that gap].
No recap section repeating all seven scores again after this — the call above is the deliverable, not a summary of it.
Do not
- Don't blend the seven letters into a single "qualification score" — MEDDICC stays seven separate reads across Metrics, Economic buyer, Decision criteria, Decision process, Identify pain, Champion, and Competition.
- Don't infer Economic buyer or Champion status from title alone ("VP of Finance" isn't automatically the final approver) — score these from what the transcript actually shows about their role and influence.
- Don't add an unrequested talk-track, next-email template, or objection-handling section — this skill's job stops at the qualification read and the one biggest risk.
Related skills
bant— for a faster early-stage qualification pass on a first call. MEDDICC covers BANT's ground and deeper.meddpicc— when you need the eighth letter, Paper process, once a deal is heading toward legal, procurement, or security review.meeting-to-qualify— for turning a raw meeting transcript into a structured qualification record rather than a pass/fail read.
Sample data
assets/sample-transcript.txt is a synthetic mid-stage qualification call —
run the skill against it first.
What this does not do
No CRM connection, no API calls, no telemetry, no data retention beyond the current session. It reads the file you point it at and nothing else.
Files bundled with it
These load only when the skill asks for them, so they cost nothing until it runs.
Need help setting it up?
This page tells you what meddicc does and what it needs. Cheetah builds the agent setup it runs inside: data, CRM, sequencing and the guardrails.
Book a call →The directory stays free. There is nothing gated behind this.