agentleFS
kochellenk-afkkochellenk-afk/claude-marketing-skills/skills/executive-summary-generator/SKILL.md

executive-summary-generator

Skill0 starsChanged 4 months agoMITView on GitHub

Produce a one-page executive summary of Google Ads performance for CMOs, CEOs, and non-marketing stakeholders. Frames metrics in business outcome language (revenue, cost, growth) rather than PPC jargon. Use this skill when a user needs to brief leadership, asks for a one-pager, mentions reporting to a CEO/CFO/board, asks for a non-technical summary, or wants to translate Google Ads results into business impact. Trigger on phrases like "executive summary", "one-pager", "report for the CEO", "leadership update", "for the board", "non-technical summary", "business impact", or any C-level/leadership reporting request.

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. poorvith-mp/skills-sales-support★ 0same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository6 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

8 rules. About 0 are common, 8 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈8

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If revenue tracking isn't in place, ask whether the user has approximate revenue per conversion that can be used.

    line 35
  2. Distinctive:

    If the user just said "exec summary", respond:

    line 41
  3. Distinctive:

    Avoid: Impressions, clicks, CTR, CPC, Quality Score, IS, conv.

    line 93
  4. Distinctive:

    If there's no notable risk, skip this line.

    line 101
  5. Distinctive:

    If the user says "for a board deck" or "as a slide", produce a PowerPoint single slide using the pptx skill.

    line 107
  6. Distinctive:

    If the period had a lot happening, that's a sign you need to cut more, not stretch the summary.

    line 113
  7. Distinctive:

    Don't use PPC jargon: No CPA, CPC, CTR, IS, ROAS without translation.

    line 117
  8. Distinctive:

    Don't bury bad results: If the period missed plan, lead with the gap, then explain it.

    line 119

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Executive Summary Generator

A skill for producing one-page Google Ads summaries for non-marketing leadership.

What this skill does

Translates Google Ads performance data into a single page tailored for a CMO, CEO, CFO, or board. Removes PPC jargon, frames metrics as business outcomes, and answers the three questions every executive asks:

  1. Are we growing?
  2. Is it efficient?
  3. What should we do next?

How this differs from the weekly digest

SkillAudienceLengthDetail
weekly-performance-digestPPC team + adjacent stakeholders~600 wordsTactical, multi-section
executive-summary-generator (this)C-suite, board, finance~300 words / 1 pageStrategic, 3 questions answered

The exec summary cuts more, frames everything in dollars-and-growth, and never assumes the reader knows what CPA means.

Required inputs

  1. Reporting period - typically a month or quarter; ask if unclear
  2. Total spend, conversions, and revenue for the period
  3. Comparable prior period - same month last year, prior quarter, or prior month (specify which)
  4. Annual goal context - revenue target, growth target, CAC target - whatever the leadership team uses
  5. Major changes during the period - campaign launches, budget shifts, team changes - for the narrative arc

If revenue tracking isn't in place, ask whether the user has approximate revenue per conversion that can be used. Without revenue context, the summary can only speak to cost and volume - which is often insufficient for leadership.

Workflow

Step 1: Gather context

If the user just said "exec summary", respond:

To make this useful for your leadership, I need:

  1. Reporting period - month, quarter, or custom range
  2. Comparison period - same month last year, prior quarter, or prior month?
  3. Top-line numbers - total spend, conversions, revenue (if tracked) for both periods
  4. The growth target this period was meant to hit - leadership cares about variance to plan
  5. The 1–2 biggest changes you made this period - narrative arc matters
  6. Anything specific you know leadership is asking about - sometimes there's a topic they want addressed

Step 2: Compute the three answer numbers

For "are we growing?":

  • Revenue period-over-period (% and absolute $)
  • Conversions / new customers period-over-period
  • One context number: market growth rate, prior trend, or industry benchmark if available

For "is it efficient?":

  • ROAS this period vs. prior
  • Cost per acquisition this period vs. prior
  • Blended marketing efficiency if available (Google Ads as % of total marketing)

For "what should we do next?":

  • Two strategic recommendations (investment, reallocation, or pause decisions)
  • Each with expected business impact in dollars

Step 3: Write the narrative

Length: 250–350 words. Structure:

[Opening sentence: result vs. plan]
[Growth narrative: numbers + driver]
[Efficiency narrative: cost + comparison]
[Forward look: 1–2 strategic recommendations]
[One-line context: what shifted in the market or our approach]

The opening sentence is critical. Not "Q2 had mixed results." Better: "Q2 delivered $1.4M in revenue (15% above plan) while reducing customer acquisition cost 12%."

Step 4: Build the data block

Below the narrative, a small results table - 5–7 rows max. Only metrics that matter at the executive level:

MetricThis periodPriorΔ
Revenue$X.XM$X.XM+X%
New customersXXXXXX+X%
Customer acquisition cost$X$X-X%
Marketing investment$XXXk$XXXk+X%
Return on ad spendX.XxX.Xx+X%

Avoid: Impressions, clicks, CTR, CPC, Quality Score, IS, conv. rate. These belong in the team-level digest, not the executive summary.

Step 5: One-line risks/watch-outs

Below the table, ONE LINE on what could change the picture next period:

"Watch: rising auction competition has pushed CPC up 8% over the last 30 days; if it continues, Q3 efficiency may compress 5–7%."

If there's no notable risk, skip this line.

Output format

Markdown by default. Optimized for paste-into-email or paste-into-Slack.

If the user says "for a board deck" or "as a slide", produce a PowerPoint single slide using the pptx skill. If they say "for the monthly business review document", produce a Word doc page using the docx skill.

Length discipline

Hard cap: 350 words for the narrative. The data table is separate.

If the period had a lot happening, that's a sign you need to cut more, not stretch the summary. The exec summary's job is to surface the 3 things leadership needs; everything else lives in the underlying digest.

What this skill must NOT do

  • Don't use PPC jargon. No CPA, CPC, CTR, IS, ROAS without translation. Even "ROAS" should be "return on ad spend" in the narrative; fine in the table.
  • Don't include tactical detail. "We added 47 negative keywords" is irrelevant at the C-level. The C-level cares about the result of those negatives, not the action itself.
  • Don't bury bad results. If the period missed plan, lead with the gap, then explain it. Leadership's #1 complaint about marketing reports is sandbagging.
  • Don't recommend more than 2 strategic actions. Three or more dilutes attention.
  • Don't pad. Empty phrases like "we continue to optimize" add nothing. Cut.
  • Don't speculate beyond what data supports. "We expect Q3 to be even stronger" is a marketing pitch, not a report. Frame forward-looks with numbers and ranges.

Reference files

  • references/exec-frame-templates.md - opening-sentence formulas and narrative archetypes
  • references/translation-glossary.md - PPC jargon → exec language mapping

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.