Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/zime-ai/zime-gtm-skillsnpx agentmods add skills/zime-ai/zime-gtm-skills/executive-briefingWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/zime-ai/zime-gtm-skills/executive-briefing)<a href="https://agentmods.dev/skills/zime-ai/zime-gtm-skills/executive-briefing"><img src="https://agentmods.dev/badge/skills/zime-ai/zime-gtm-skills/executive-briefing/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/zime-ai/zime-gtm-skills/executive-briefing"><img src="https://agentmods.dev/badge/skills/zime-ai/zime-gtm-skills/executive-briefing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00086 | $0.01419 |
| Opus 5 | $0.00043 | $0.00709 |
| Sonnet 5 | $0.00017 | $0.00284 |
| Haiku 4.5 | $0.00009 | $0.00142 |
Grade A, and why
executive-briefing scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 12d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 132 lines — stays where its author put it; the contents beside it link to each section on GitHub.
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/inferredtag 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
for an executive audience, not an exhaustive moment list. Use
deal-highlights right after a single call; use executive-briefing when
someone above the deal needs to act on it.
When to use this
- A rep needs something to send their own manager or VP on where a deal stands, without the exec reading the transcript.
- A rep is prepping the buyer's exec sponsor for a check-in and needs a short, cited status they can forward as-is.
- A manager wants the risk and the ask on one specific deal, not a
pipeline-wide risk sweep (
deal-risk-digest) or a closed-deal postmortem (win-loss-brief).
Modes
Transcript mode (.txt, .vtt, .json, .md)
claude "run executive-briefing on ./calls/deal-checkin.txt"
If several transcripts from the same deal are given, read them in chronological order and brief the deal as a whole. Every claim cites the quote (and timestamp, if present) it came from.
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 12d ago First seen · 132 lines · 86 tokens per session scan A 9c784208da50
executive-briefing is a skill published in the GitHub repository zime-ai/zime-gtm-skills (14 stars, last pushed 17d ago), licensed MIT. It adds 86 tokens to every session and 1,419 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
go-to-market-playbook
A reusable Go-to-Market strategy template for both B2B and B2C launches. Covers positioning, messaging, ICP definition, channel selection, and competitive analysis frameworks. By @WeiYipei.
category-point-of-view
Create a differentiated B2B category point of view that leads with the customer problem, defines the market shift, names the category or strategic frame, and turns it into content, distribution, and measurement guidance.
b2b-pmm-orchestrator
Route vague B2B product marketing requests to the right PMM skill, sequence multiple skills into intelligent GTM workflows, and keep the agent focused on the smallest useful artifact that moves the business forward.
ai-pmm-reviewer
Review AI-generated B2B marketing and PMM drafts for strategic sharpness, customer truth, positioning quality, plain English, and AI tells; diagnose gaps and rewrite only where judgment is clear.
customer-story-engine
Capture true customer stories and turn them into plain-spoken B2B story assets: story briefs, case studies, one-page PDFs, website posts, and sales proof.
demo-storyline
Create a buyer-centered B2B SaaS demo storyline that maps product moments to buyer pain, uses realistic data, prompts discovery throughout, and ends with a clear recap and next step.