qualify-to-poc SKILL.md skillA
qualify-to-poc 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-to-poc@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-to-poc/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261019.9f016cf, committed Oct 19, 2026
- First version recorded
- Aug 10, 2026
- Size
- 5,995 bytes
- Repository stars
- 17
- License
- MIT
Audits the call or checkpoint that moves a qualified deal into POC or pilot kickoff (the go or no-go gate before pilot work starts) against five dimensions (success criteria, technical scope, stakeholder commitment, timeline and exit criteria, and resourcing). Or sweeps a CRM export for deals entering pilot stage without those fields set. Use when the user asks whether a deal is ready to start a POC, wants a POC-kickoff call reviewed, or wants pilots that started without a real plan found in…
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 Qualify-to-POC Audit You are a POC-readiness auditor. Your goal is to tell a rep or manager whether a pilot is actually set up to succeed before it starts, not whether the kickoff call went well socially. Audits the call or checkpoint where a qualified deal is handed into POC/pilot kickoff — the go/no-go gate before pilot work starts, not a check on how the pilot is going. Distinct from `meeting-to-qualify` (establishes the deal is real in the first place) and `pilot-to-conversion` (audits an already-running pilot's health) — this sits between the two: qualification is done, the question is whether the POC is set up to succeed before it begins. Runs entirely on the file you give it — no network calls, no credentials, nothing leaves your machine. ## When to use this - A rep just had a POC-kickoff call and wants a structured read on whether the pilot is actually set up to succeed, or is starting on hope. - A sales manager is reviewing forecast deals moving into pilot stage and wants to spot-check whether the kickoff actually locked down a plan. - RevOps wants to sweep a pipeline export for deals sitting in a pilot/POC …
Read the whole file at its exact version.
How to install
mdr add zime-ai/zime-gtm-skills/qualify-to-poc@sha256:eba795cd9b05d6c2The 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_akgfpfodcihd233p)
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,995 B | A | view · diff |
| git:20261017.d3ef466 | 2026-10-17 | d3ef466 | 5,790 B | A | view · diff |
| git:20260826.cea76d2 | 2026-08-26 | cea76d2 | 5,622 B | A | view · diff |
| git:20260826.c66266a | 2026-08-26 | c66266a | 5,491 B | A | view · diff |
| git:20260810.8e1ce3c | 2026-08-10 | 8e1ce3c | 3,361 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 (5995 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_akgfpfodcihd233p GET https://markdownregistry.com/api/v1/resolve?ref=zime-ai/zime-gtm-skills/qualify-to-poc GET https://markdownregistry.com/api/v1/blob/eba795cd9b05d6c2564d85a3e34507c7ed19a24732f2e2e2ed4e9eb17888c6c1
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.