evaluation-pipeline-check SKILL.md skillA
evaluation-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/evaluation-pipeline-check@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/evaluation-pipeline-check/SKILL.md- Versions recorded
- 4
- Latest version
- git:20261017.d3ef466, committed Oct 17, 2026
- First version recorded
- Aug 10, 2026
- Size
- 4,811 bytes
- Repository stars
- 17
- License
- MIT
Sweeps a deal/pipeline export for technical evaluations running without defined success criteria, a technical champion, or an evaluation end date, and flags evaluations running long, stalled, or missing a security/procurement review relative to the export's own norms. Use when reviewing deals sitting in a technical evaluation stage, or auditing a pipeline export before a forecast call. Also use when the user asks which technical evaluations have no plan or are drifting.
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
# Evaluation Pipeline Check You are a pipeline-hygiene auditor. Your goal is to tell RevOps or a manager which technical evaluations are missing basic scaffolding — no criteria, no champion, no end date. Sweeps a deal export for evaluations that lack the shape a real technical evaluation needs: defined success criteria, a technical champion, and an end date. Distinct from `technical-discovery`, which audits a technical discovery *call* transcript — this skill never reads a call. It only asks whether the evaluation, as recorded in the CRM, has a shape at all. ## When to use this - A deal is sitting in "Technical Evaluation" and a manager wants a structural gut-check before the forecast call. - RevOps wants to sweep the pipeline for evaluations that have been open too long or gone quiet. - A rep wants to confirm their own evaluation deals aren't missing basic scaffolding (criteria, champion, end date) before a QBR. ## 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 — note an ambiguous column and move on, don't stop to ask. …
Read the whole file at its exact version.
How to install
mdr add zime-ai/zime-gtm-skills/evaluation-pipeline-check@sha256:69c3098a3878e5f9The 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_kfknni5pj7ogfnci)
0 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 4 versions of this file, between Aug 10, 2026 and Oct 17, 2026, about one every 23 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261017.d3ef466 latest | 2026-10-17 | d3ef466 | 4,811 B | A | view · diff |
| git:20260826.cea76d2 | 2026-08-26 | cea76d2 | 4,725 B | A | view · diff |
| git:20260826.36428e1 | 2026-08-26 | 36428e1 | 4,594 B | A | view · diff |
| git:20260810.5591440 | 2026-08-10 | 5591440 | 3,543 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 (4811 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_kfknni5pj7ogfnci GET https://markdownregistry.com/api/v1/resolve?ref=zime-ai/zime-gtm-skills/evaluation-pipeline-check GET https://markdownregistry.com/api/v1/blob/69c3098a3878e5f9dceff1c5e4a294b79bc26ad96559d2d9a98869fc1b2afdc0
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.