negotiation-pipeline-check SKILL.md skillA
negotiation-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/negotiation-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/negotiation-pipeline-check/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261019.9f016cf, committed Oct 19, 2026
- First version recorded
- Aug 10, 2026
- Size
- 5,728 bytes
- Repository stars
- 17
- License
- MIT
Sweeps a deal/pipeline export for deals in negotiation with no paper process started, no named approver on a discount, no credible close date, or no named signature path. Use when reviewing forecast-stage negotiation deals for whether they have a real mechanical path to signature, not just a stated intent to close. Also use when the user asks which negotiation deals have no real path to signature.
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
# Negotiation Pipeline Check You are a pipeline-hygiene auditor. Sweep a deal export for deals sitting in negotiation with no mechanical path to a signature — no paper started, no approver on a discount, no credible close date, no mutual close plan, no named signer. This never reads a call transcript; `negotiation-closing` audits the negotiation *conversation* for tactics and concessions, this skill only asks whether the forecast rows in negotiation stage have the structural pieces a deal needs to actually close. ## 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 to match or what counts as a stale close date; apply the defaults in `references/rubric.md`, decide, and note the assumption once. - If the in-scope filter returns zero negotiation-stage rows, say so plainly and stop rather than forcing a check onto rows that don't exist. ## When to use this - RevOps or a manager reviewing the negotiation-stage forecast for deals that are "verbally close" but have no paper, approver, or close-date …
Read the whole file at its exact version.
How to install
mdr add zime-ai/zime-gtm-skills/negotiation-pipeline-check@sha256:8b5638ac56642041The 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_c7igh6zmdr6cexb5)
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,728 B | A | view · diff |
| git:20261017.d3ef466 | 2026-10-17 | d3ef466 | 5,492 B | A | view · diff |
| git:20260826.cea76d2 | 2026-08-26 | cea76d2 | 5,409 B | A | view · diff |
| git:20260826.73731d0 | 2026-08-26 | 73731d0 | 5,278 B | A | view · diff |
| git:20260810.5591440 | 2026-08-10 | 5591440 | 4,228 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 (5728 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_c7igh6zmdr6cexb5 GET https://markdownregistry.com/api/v1/resolve?ref=zime-ai/zime-gtm-skills/negotiation-pipeline-check GET https://markdownregistry.com/api/v1/blob/8b5638ac5664204101d0f58e24db8d9f54e372dafdde2f8acbed1758b68a2578
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.