Skip to content
Automation
Skill

/executive-briefs

Use to craft concise revenue updates for executives and boards.

From plugin
gtm-agents
368200 skills200 agents199 commands
Install
$ npx -y skills add gtmagents/gtm-agents --skill executive-briefs --agent claude-code

How it fires

How this skill gets triggered: by you, by Claude, or both.

  • Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
  • You can call itInvoke it directly when you want it.
  • Slash command/executive-briefs

Context preview

The summary Claude sees to decide when to auto-load this skill.

Use to craft concise revenue updates for executives and boards.

SKILL.md

executive-briefs.SKILL.md
name: executive-briefs
description: Use to craft concise revenue updates for executives and boards.

Executive Brief System Skill

When to Use

  • Delivering forecast updates to ELT or board audiences.
  • Summarizing revenue risks/opportunities with clear asks.
  • Packaging meeting-ready decks or memos that pull from forecast + variance analysis outputs.

Framework

1. **Audience Lens** – capture what the audience cares about (growth, margin, cash, runway) and tailor tone. 2. **Story Arc** – set context, state the headline (ahead/behind), outline drivers, and present mitigation plan. 3. **Evidence Layer** – include key charts/tables with consistent formatting + footnotes. 4. **Decision & Ask** – specify what approval, resource shift, or unblock is needed. 5. **Appendix & Audit Trail** – link to deeper dashboards, logs, and forecast files for transparency.

Templates

  • One-slide executive summary (headline, numbers, drivers, actions).
  • Board memo outline (context, highlights, lowlights, requests).
  • Risk register snippet for ongoing tracking.

Tips

  • Use consistent metric definitions and color-coding to avoid confusion.
  • Keep main section under one page/slide, move detail to appendix.
  • Reference `variance-analysis` findings and `forecast-modeling` assumptions in footnotes.

---

Ships withgtm-agents

Free AI automation for sales, marketing, and growth teams. No coding required.

Get the whole plugin