won-pipeline-check SKILL.md skillA
won-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/won-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/won-pipeline-check/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261019.9f016cf, committed Oct 19, 2026
- First version recorded
- Aug 10, 2026
- Size
- 4,850 bytes
- Repository stars
- 17
- License
- MIT
Sweeps a closed-won deal export for missing handoff and record data the post-sale team needs — CS owner, kickoff date, signed value/term, contract reference, and date/stage consistency. Use when a deal desk or RevOps person wants to check closed-won deals before they hand off to onboarding/CS, or audit a pipeline export for won deals with incomplete records. Also use when the user asks which closed-won deals have incomplete handoff records.
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
# Won Pipeline Check You are a pipeline-hygiene auditor. Sweep a deal export for closed-won deals missing the data the next team needs to run the handoff. This is hygiene at the funnel *exit*, not a post-sale health read — `customer-success` and `churn-prevention` audit what happens after the handoff; this skill only asks whether the handoff has the data to happen. There is no transcript mode: this is a structural export sweep, not a call-quality audit. ## 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 stage label counts as "Won" or how to treat a missing column; apply the defaults below, decide, and note the assumption once. - If the in-scope filter returns zero Won-pipeline rows, say so plainly and stop rather than forcing a check onto rows that don't exist. ## When to use this - A deal desk or RevOps person wants to check closed-won deals before they hand off to onboarding/CS. - A CS lead wants a list of recently-won deals missing the fields their team …
Read the whole file at its exact version.
How to install
mdr add zime-ai/zime-gtm-skills/won-pipeline-check@sha256:4ee3c1d523621e01The 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_zqkyvenuql5e5wfc)
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 | 4,850 B | A | view · diff |
| git:20261017.d3ef466 | 2026-10-17 | d3ef466 | 4,627 B | A | view · diff |
| git:20260826.cea76d2 | 2026-08-26 | cea76d2 | 4,543 B | A | view · diff |
| git:20260826.73731d0 | 2026-08-26 | 73731d0 | 4,412 B | A | view · diff |
| git:20260810.5591440 | 2026-08-10 | 5591440 | 3,384 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 (4850 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_zqkyvenuql5e5wfc GET https://markdownregistry.com/api/v1/resolve?ref=zime-ai/zime-gtm-skills/won-pipeline-check GET https://markdownregistry.com/api/v1/blob/4ee3c1d523621e015f5b5032429391608d1c20ea202a62a9c14804d6f35eb890
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.