mutual-action-plan SKILL.md skillA
mutual-action-plan 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/mutual-action-plan@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/mutual-action-plan/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261019.9f016cf, committed Oct 19, 2026
- First version recorded
- Aug 12, 2026
- Size
- 5,470 bytes
- Repository stars
- 17
- License
- MIT
Writes a mutual action plan out of what was actually said on a call, with milestones from today to signature, each with an owner on both sides and a date, or fills date and stage gaps from a CRM export row. Use when a rep asks for a mutual action plan, a close plan, or a signature path to send a prospect after a call, or when a manager wants to know whether a deal's stated next steps hang together as a plan.
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
# Mutual Action Plan You are a deal-intelligence writer. Write a mutual action plan out of what was actually said on a call: milestones from today to signature, each with an owner on both sides and a date. This is a phase-2 deal-intelligence skill — it writes something forward, it does not grade the call against a rubric the way `next-step-commitment` or `meddicc` do. ## 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 without stopping to ask which milestones to include — apply the `heard`/`inferred` test below to everything the call surfaced and report the result, including an all-inferred plan if that's what the call actually supports. - Don't invent a milestone the call never gestured toward, even to fill out a plan that looks sparse. ## When to use this - A rep just got off a call that covered next steps and wants a MAP to send the prospect, not a to-do list they invented themselves afterward. - A manager wants to check whether a deal's "next steps" actually hang together as milestones, or are one-sided promises dressed up as a plan. …
Read the whole file at its exact version.
How to install
mdr add zime-ai/zime-gtm-skills/mutual-action-plan@sha256:14f77ce74123a5a5The 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_wpu4btdimuzvudm5)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Aug 12, 2026 and Oct 19, 2026, about one every 17 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261019.9f016cf latest | 2026-10-19 | 9f016cf | 5,470 B | A | view · diff |
| git:20261017.d3ef466 | 2026-10-17 | d3ef466 | 5,265 B | A | view · diff |
| git:20260826.cea76d2 | 2026-08-26 | cea76d2 | 5,219 B | A | view · diff |
| git:20260826.bc39551 | 2026-08-26 | bc39551 | 5,088 B | A | view · diff |
| git:20260812.b22d344 | 2026-08-12 | b22d344 | 3,944 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 (5470 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_wpu4btdimuzvudm5 GET https://markdownregistry.com/api/v1/resolve?ref=zime-ai/zime-gtm-skills/mutual-action-plan GET https://markdownregistry.com/api/v1/blob/14f77ce74123a5a5964e3455f87a147056ce6485552d0e6d9695f93669341b55
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.