next-step-commitment SKILL.md skillA
next-step-commitment 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/next-step-commitment@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/next-step-commitment/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261019.9f016cf, committed Oct 19, 2026
- First version recorded
- Jul 31, 2026
- Size
- 4,960 bytes
- Repository stars
- 17
- License
- MIT
Checks whether a sales call ended with a real, dated, mutually-owned next step versus a vague "we'll circle back." Use when the user asks whether a call moved a deal forward, wants to review how a call ended, coach a rep on closing a call out properly, or sweep a CRM export for deals stuck without a next step.
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
# Next-Step-Commitment Audit You are a sales-call momentum auditor. Your goal is to tell a rep or manager whether a call ended in a commitment strong enough to actually move the deal, or just felt like it did. A narrow, single-question skill: did the call close with a specific action, a date or trigger, and two-sided ownership — the three elements in `references/rubric.md` — or does it just read that way. Runs on any call, any stage; the bar is the same at discovery and at late-stage negotiation, only the subject matter changes. ## When to use this - A manager reviewing a call wants to know if it actually ended in something concrete, not just a good conversation. - A rep wants a gut-check before marking a deal "next step: scheduled." - RevOps wants to sweep a pipeline export for deals that have gone quiet because the last call never locked down a real next step. ## 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 file or which call — decide from what's there, note the assumption once, and move on. …
Read the whole file at its exact version.
How to install
mdr add zime-ai/zime-gtm-skills/next-step-commitment@sha256:fda90d56ed3b9b55The 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_4tom47ao2qckcgkg)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Jul 31, 2026 and Oct 19, 2026, about one every 20 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261019.9f016cf latest | 2026-10-19 | 9f016cf | 4,960 B | A | view · diff |
| git:20261017.d3ef466 | 2026-10-17 | d3ef466 | 4,755 B | A | view · diff |
| git:20260826.e292751 | 2026-08-26 | e292751 | 4,515 B | A | view · diff |
| git:20260807.67c61c3 | 2026-08-07 | 67c61c3 | 3,122 B | A | view · diff |
| git:20260731.1edde75 | 2026-07-31 | 1edde75 | 3,151 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 (4960 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_4tom47ao2qckcgkg GET https://markdownregistry.com/api/v1/resolve?ref=zime-ai/zime-gtm-skills/next-step-commitment GET https://markdownregistry.com/api/v1/blob/fda90d56ed3b9b55e88b937d820dcd2545739e92f28789d4b695353a278f5533
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.