prospect-pipeline-check SKILL.md skillA
prospect-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/prospect-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/prospect-pipeline-check/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261019.9f016cf, committed Oct 19, 2026
- First version recorded
- Aug 10, 2026
- Size
- 5,283 bytes
- Repository stars
- 17
- License
- MIT
Sweeps a CRM pipeline export for prospect-stage deals with no real two-way engagement from the prospect side — the earliest "is this even a deal" gate, before budget, buyer, or pain are even in scope. Use when auditing a prospect-stage pipeline for zombie deals a rep is carrying forward on outbound activity alone, or before a pipeline review to separate real opportunities from unanswered outreach. Also use when the user asks which prospect-stage deals are zombies or have no real engagement.
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 Prospect Pipeline Check You are a pipeline-hygiene auditor. Your goal is to tell RevOps or a manager which prospect-stage deals have no real prospect on the other end. Sweeps a deal/pipeline export for prospect-stage deals that have no real two-way engagement — no reply, no meeting, no inbound signal from the prospect, only rep-side outbound. This is the earliest gate in the deal lifecycle: it never asks about budget, buyer, or pain (that's `qualify-pipeline-check`'s job). It only asks whether a human on the other side has engaged at all. Runs entirely on the file (or connector rows) you give it — no network calls, no credentials, nothing leaves your machine beyond an already-connected CRM tool. ## When to use this - RevOps or a sales manager wants to find prospect-stage deals a rep is carrying forward on outbound activity alone, with no prospect response. - Before a pipeline review, to separate deals with real two-way signal from ones that are really just unanswered sequences sitting in a stage. - A rep wants a gut-check on their own prospect list before it goes stale. ## 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/prospect-pipeline-check@sha256:cb7c115680a9f478The 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_qppnaghmnbxfzlow)
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,283 B | A | view · diff |
| git:20261017.d3ef466 | 2026-10-17 | d3ef466 | 5,068 B | A | view · diff |
| git:20260826.cea76d2 | 2026-08-26 | cea76d2 | 4,974 B | A | view · diff |
| git:20260826.36428e1 | 2026-08-26 | 36428e1 | 4,843 B | A | view · diff |
| git:20260810.5591440 | 2026-08-10 | 5591440 | 3,821 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 (5283 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_qppnaghmnbxfzlow GET https://markdownregistry.com/api/v1/resolve?ref=zime-ai/zime-gtm-skills/prospect-pipeline-check GET https://markdownregistry.com/api/v1/blob/cb7c115680a9f478e7c46226737f5751a605c903739f44ee2fb5f867b1dfbbd7
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.