executive-briefing SKILL.md skillA
executive-briefing 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/executive-briefing@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/executive-briefing/SKILL.md- Versions recorded
- 4
- Latest version
- git:20261017.d3ef466, committed Oct 17, 2026
- First version recorded
- Aug 14, 2026
- Size
- 5,901 bytes
- Repository stars
- 17
- License
- MIT
Writes the short brief a rep sends upward out of one deal, to their own exec or the buyer's exec sponsor, covering deal snapshot, status, what is at risk, and the ask, each claim cited to a quote or a CSV column and cell. Use when someone who will never read the transcript needs to act on one deal, when the user asks for an exec brief, a deal summary for leadership, or an escalation note, and not for a call-by-call digest or a whole-pipeline sweep.
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
# Executive Briefing You are a deal-intelligence writer. Write the short brief a rep sends upward out of one deal: what it is, where it stands, what's at risk, what's being asked for. This is a phase-2 deal-intelligence skill — it writes something forward, for an executive audience who wants status/risk/ask, not a rubric grade of the call. ## 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 risks or asks to include — apply the brief structure below and the `heard`/`inferred` tag on the ask, and report what the input actually supports. - If the deal value or close date isn't stated anywhere, say so explicitly rather than estimating it or asking the user to supply one. **Distinct from `deal-highlights`**: `deal-highlights` digests one call for a manager to skim (a list of moments — commitment, objection, buying signal, competitive mention, risk). This skill is deal-level, not call-level — if several calls on the same deal are given, it briefs the deal as a whole, read in order, not call-by-call — and decision-oriented …
Read the whole file at its exact version.
How to install
mdr add zime-ai/zime-gtm-skills/executive-briefing@sha256:dbdfa3e6b55f02e7The 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_fahogk3c6gqzrhr3)
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,901 B | A | view · diff |
| git:20260826.cea76d2 | 2026-08-26 | cea76d2 | 5,802 B | A | view · diff |
| git:20260826.0714e30 | 2026-08-26 | 0714e30 | 5,671 B | A | view · diff |
| git:20260814.a128131 | 2026-08-14 | a128131 | 4,576 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 (5901 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_fahogk3c6gqzrhr3 GET https://markdownregistry.com/api/v1/resolve?ref=zime-ai/zime-gtm-skills/executive-briefing GET https://markdownregistry.com/api/v1/blob/dbdfa3e6b55f02e75effaac371ff01057536f0a6c2117d301df6de5b2621e92e
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.
More from zime-ai/zime-gtm-skills
Every file in zime-ai/zime-gtm-skills