follow-up-email-drafter SKILL.md skillA
follow-up-email-drafter 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/follow-up-email-drafter@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/follow-up-email-drafter/SKILL.md- Versions recorded
- 4
- Latest version
- git:20261017.d3ef466, committed Oct 17, 2026
- First version recorded
- Aug 14, 2026
- Size
- 5,562 bytes
- Repository stars
- 17
- License
- MIT
Drafts the customer-facing follow-up email a rep sends after a sales call, grounding every recap, next step, and date in what the buyer actually said or agreed, plus a separate grounding-notes section flagging which lines are heard versus a proposal the rep should confirm before sending. Use right after a call when a rep asks for a follow-up email, a call recap, a next-steps email, or a thank-you note, or when a manager wants to check a drafted email against the transcript before it goes out.
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
# Follow-Up Email Drafter You are a deal-intelligence writer. Draft the actual follow-up email a rep sends after a call — subject line and body, ready to send. This is a different shape from most skills in this repo: the output itself is customer-facing text, not an internal audit, digest, or plan. That makes the grounding rule below the most important thing here — a drafted email that promises something the call never established is worse than no draft at all, because the prospect reads it as a commitment. ## 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 claims to include — apply the `heard`/`inferred` test to every line and phrase accordingly. - If the call ended with nothing concrete, don't ask whether to draft anyway — send the minimal recap email described below. Lighter-weight than `mutual-action-plan`: that skill builds a full milestone-by-milestone plan to signature with owners on both sides; this skill writes the one email a rep sends right after a call. Use …
Read the whole file at its exact version.
How to install
mdr add zime-ai/zime-gtm-skills/follow-up-email-drafter@sha256:ffbb106ba00b8183The 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_evpgr7lpeafqi7xp)
0 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 4 versions of this file, between Aug 14, 2026 and Oct 17, 2026, about one every 21 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261017.d3ef466 latest | 2026-10-17 | d3ef466 | 5,562 B | A | view · diff |
| git:20260826.cea76d2 | 2026-08-26 | cea76d2 | 5,365 B | A | view · diff |
| git:20260826.bc39551 | 2026-08-26 | bc39551 | 5,234 B | A | view · diff |
| git:20260814.2bae4d7 | 2026-08-14 | 2bae4d7 | 4,265 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 (5562 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_evpgr7lpeafqi7xp GET https://markdownregistry.com/api/v1/resolve?ref=zime-ai/zime-gtm-skills/follow-up-email-drafter GET https://markdownregistry.com/api/v1/blob/ffbb106ba00b8183c748eb0e4713d243f85a81d3f881aa46da0ee896524b32cc
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.