meeting-to-qualify SKILL.md skillA
meeting-to-qualify from zime-ai/zime-gtm-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add zime-ai/zime-gtm-skills/meeting-to-qualify@git:20261017.d3ef466Pins git:20261017.d3ef466 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- zime-ai/zime-gtm-skills
- Path
skills/meeting-to-qualify/SKILL.md- Versions recorded
- 4
- Latest version
- git:20261017.d3ef466, committed Oct 17, 2026
- First version recorded
- Jul 29, 2026
- Size
- 5,442 bytes
- Repository stars
- 17
- License
- MIT
Audits a qualification call transcript to assess whether a deal is real (problem urgency, authority, budget plausibility, timeline, fit, competition, engagement, next step) and credits only what the buyer said, or sweeps a CRM export for deals never properly qualified. Use when the user asks whether to invest further in a deal, to review a qualification call, or to find unqualified deals inflating the forecast.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# GTM Meeting-to-Qualify Audit You are a sales-call qualification auditor. Your goal is to turn a raw qualification call into a structured go/no-go read a rep or manager can act on immediately. Audits a qualification-stage call against eight dimensions that determine whether a deal is real and worth pursuing further — not a deep discovery pass, a go/no-go read. ## When to use this - A rep just had a first or second call and needs a structured read on whether to keep investing time in this deal. - A sales manager is reviewing forecast calls and wants to spot-check whether "qualified" deals actually got qualified. - RevOps wants to sweep a pipeline export for deals sitting in a qualified stage with no real evidence behind that label. ## 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 call, who's internal, or how to read an ambiguous moment — apply the default rule at the point it comes up, decide, and note the assumption once. - If the input isn't a qualification call, say so in one line and still …
Read the whole file at its exact version.
How to install
mdr add zime-ai/zime-gtm-skills/meeting-to-qualify@sha256:313b31e5cbc35602The line at the top of this page pins the label git:20261017.d3ef466, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_7ejapvjiw4wgl3ha)
0 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 4 versions of this file, between Jul 29, 2026 and Oct 17, 2026, about one every 27 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261017.d3ef466 latest | 2026-10-17 | d3ef466 | 5,442 B | A | view · diff |
| git:20260826.c66266a | 2026-08-26 | c66266a | 4,692 B | A | view · diff |
| git:20260731.1edde75 | 2026-07-31 | 1edde75 | 2,805 B | A | view · diff |
| git:20260729.ec77584 | 2026-07-29 | ec77584 | 2,759 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (5442 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
zime-ai/zime-gtm-skills · 17 stars · license MIT · pushed 2026-10-20 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_7ejapvjiw4wgl3ha GET https://markdownregistry.com/api/v1/resolve?ref=zime-ai/zime-gtm-skills/meeting-to-qualify GET https://markdownregistry.com/api/v1/blob/313b31e5cbc3560256b79841161089b080fda90006a598af4d735318397e269d
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.