qualify-pipeline-check SKILL.md skillA
qualify-pipeline-check 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/qualify-pipeline-check@git:20261019.9f016cfPins git:20261019.9f016cf 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/qualify-pipeline-check/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261019.9f016cf, committed Oct 19, 2026
- First version recorded
- Aug 10, 2026
- Size
- 5,738 bytes
- Repository stars
- 17
- License
- MIT
Sweeps a CRM/pipeline export for deals that advanced past the Qualify stage without the facts that stage is supposed to establish — economic buyer, pain, budget signal, a close date consistent with the procurement cycle, a next step, and a qualification-framework record. Use when RevOps or a manager wants to audit the Qualify pipeline for deals advanced on hope rather than evidence. Does not read call transcripts — that's `meeting-to-qualify` (audits the qualification call itself) or…
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
# Qualify Pipeline Check You are a pipeline-hygiene auditor. Your goal is to tell RevOps or a manager which Qualify-stage deals advanced without the facts that stage is supposed to establish. Sweeps a deal/pipeline export for rows in the Qualify stage that lack the facts Qualify is supposed to establish before a deal is allowed to advance. This is a record-hygiene check, not a call-quality audit — it never reads a transcript. Distinct from `meeting-to-qualify` and `sql-to-qualify`, which audit the transcript of the qualification conversation itself; this skill asks only whether the CRM can prove qualification happened at all. ## When to use this - RevOps wants a periodic sweep of the Qualify stage for deals that drifted forward without the underlying facts ever being captured. - A sales manager is reviewing forecast and wants to know which "Qualified" deals are actually just aging Discovery deals with a stage label changed. - Before a pipeline review, to flag deals that will not survive real scrutiny on economic buyer, budget, or next step. ## Before you start - If `.agents/gtm-context.md` (or `.claude/gtm-context.md`) exists, read it …
Read the whole file at its exact version.
How to install
mdr add zime-ai/zime-gtm-skills/qualify-pipeline-check@sha256:8ce7e7816fbfde76The line at the top of this page pins the label git:20261019.9f016cf, 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_nfi7bdvgpkossaep)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Aug 10, 2026 and Oct 19, 2026, about one every 17 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261019.9f016cf latest | 2026-10-19 | 9f016cf | 5,738 B | A | view · diff |
| git:20261017.d3ef466 | 2026-10-17 | d3ef466 | 5,529 B | A | view · diff |
| git:20260826.cea76d2 | 2026-08-26 | cea76d2 | 5,443 B | A | view · diff |
| git:20260826.36428e1 | 2026-08-26 | 36428e1 | 5,312 B | A | view · diff |
| git:20260810.5591440 | 2026-08-10 | 5591440 | 4,253 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 (5738 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_nfi7bdvgpkossaep GET https://markdownregistry.com/api/v1/resolve?ref=zime-ai/zime-gtm-skills/qualify-pipeline-check GET https://markdownregistry.com/api/v1/blob/8ce7e7816fbfde76b8731f4f6cd3291bb7363a332abd26320d3eb5e74baf10ac
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.