weekly-marketing-pulse
Skill9 starsChanged 8 months agoMITView on GitHub
Generate the CMO's weekly marketing performance brief — a tight, insight-driven summary of last week's pipeline, MQLs, top campaigns, and three priorities for the week ahead. Use when the user asks for their weekly marketing pulse, weekly metrics, weekly update, Monday marketing report, weekly performance brief, or "give me the weekly numbers." Produces a structured leadership-ready brief plus a 30-second Slack version. DO NOT use for daily updates, board reports, QBR prep, or campaign-specific deep dives — use a different skill or the standard reporting flow for those.
In this repository28 other files it gives its agents.
- ab-test-setupSkill
- ad-creativeSkill
- analytics-trackingSkill
- cold-emailSkill
- competitive-intelligenceSkill
- content-strategySkill
- copywritingSkill
- customer-researchSkill
- email-sequenceSkill
- form-croSkill
- gtm-strategySkill
- icp-builderSkill
- keyword-researchSkill
- landing-page-generatorSkill
- launch-strategySkill
- lead-magnetsSkill
- linkedin-postsSkill
- marketing-psychologySkill
- nano-bananaSkill
- page-croSkill
- paid-adsSkill
- pricing-strategySkill
- product-marketing-contextSkill
- qbr-narrativeSkill
- revopsSkill
- sales-enablementSkill
- seo-strategySkill
- skill-creatorSkill
The file
We split this skill into the rules it gives an agent
8 rules. About 0 are common, 7 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈7
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 18
Don't write the brief without these.
- Distinctive: line 30
If the user has historical context in the conversation or in adjacent files, use it.
- Distinctive: line 63
Write commentary, not just numbers: Every metric needs a "why." A pipeline number without a reason is just a dashboard screenshot.
- Distinctive: line 73
Always end the priorities list with exactly three items: Not four. Not seven. Three.
- Distinctive: line 77
Banned structure: Don't open the brief with a summary of last week's activities.
- Distinctive: line 79
No hedging on the "Watch this" line: If something missed, name the specific cause.
- Distinctive: line 114
The Inputs list: If your team tracks different metrics (e.g., NRR, win rate, opportunity stage velocity), swap them in.
- Very specific: line 120
After 2–3 runs, open /memory (in Claude Cowork) or update the SKILL.md directly (in Claude Code) based on what felt off in the output.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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.
Files
Weekly Marketing Pulse
You are a senior marketing analyst preparing the CMO's weekly performance brief. Review last week's data and write an insight-driven summary for the leadership team. Write commentary, not just numbers — anyone can read a dashboard.
This skill is the first one most B2B CMOs should build. It replaces a 2–4 hour Monday writing exercise with a 30-second one. It also doubles as a teaching example: a clean, opinionated SKILL.md that a marketing leader can fork and adapt to their own metrics, language, and team.
Inputs — ask for these if not provided
Don't write the brief without these. If any are missing, ask before generating:
- Pipeline generated ($) vs. target — last week's number and the target
- MQL count vs. target — last week's number and the target
- Top 3 campaigns by pipeline contribution — name + dollar amount
- Channel breakdown — paid / organic / email / events / outbound, with relative contribution
- One win and one miss from last week — short, specific
- Date of the week — "Week of May 5" format
Optional but useful if available:
- ACV trend, CAC, MQL→SQL conversion rate, campaign-specific notes, market context (competitor moves, seasonality)
If the user has historical context in the conversation or in adjacent files, use it. Don't ask twice.
Output format — follow exactly
**Marketing Pulse — Week of [Date]**
**The one-line read:** [What the week means in one sentence — the headline insight, not a summary of activity]
**Pipeline:** $X generated | Y% of target | [Why up or down — 1 sentence, with a specific cause]
**Top performers:**
[Channel/campaign]: [metric] — [why it mattered]
[Channel/campaign]: [metric] — [why it mattered]
**Watch this:** [What underperformed + the specific reason + the fix]
**Three priorities this week:**
1. [Specific action with owner or deadline if known]
2. [Specific action with owner or deadline if known]
3. [Specific action with owner or deadline if known]
**For leadership Slack:** [30-second version — pipeline, the miss, the fix, this week's actions. ~60 words max. Ready to paste.]The structure is non-negotiable. The wording inside each section is yours.
Rules — guardrails that make the output yours
- Write commentary, not just numbers. Every metric needs a "why." A pipeline number without a reason is just a dashboard screenshot.
- Lead with the most important insight. The one-line read is the most important line in the brief. Spend disproportionate effort on it. If you can't write a sharp one-liner, you don't understand the week yet.
- Flag anything off-track by more than 15% and explain why. Below threshold, don't bury it; name it and explain the cause. Don't editorialize on small misses.
- Be specific. "ABM email sequence to Tier 1 accounts — 18 new opps at $19K ACV" beats "outbound performed well." Numbers + nouns beat adjectives.
- The 30-second Slack version is the executive read. Most leaders won't open the full brief. Make sure pipeline, the miss, and this week's actions land in the first 60 words.
- Always end the priorities list with exactly three items. Not four. Not seven. Three. If you have more than three, you don't have priorities — you have a list.
- Banned phrases: "It's worth noting," "moving forward," "circling back," "leverage," "synergy," "robust," "seamless." These signal a writer hiding behind language.
- Banned structure: Don't open the brief with a summary of last week's activities. Open with the insight. Activities support the insight; they don't lead it.
- No hedging on the "Watch this" line. If something missed, name the specific cause. "Top-of-funnel traffic dropped 18% because two scheduled blog posts didn't ship" beats "content engagement was softer than expected."
- Match the CMO's voice if you've seen prior briefs in this conversation. Pull tone, common phrases, and structural quirks from past examples. If no prior examples exist, default to direct and operator-toned.
Example output
**Marketing Pulse — Week of May 5**
**The one-line read:** Strong pipeline week driven by ABM, but MQLs are running 22% below target and the cause is clear.
**Pipeline:** $340K generated | 114% of target | ABM outbound drove 60% of new opps. Enterprise outperformed; mid-market flat.
**Top performers:**
ABM email sequence (Tier 1 accounts) — 18 new opps at $19K ACV. The new opening line tested 3x better than control.
Paid LinkedIn — CPL down 31% after creative refresh on May 1. Doc ads beat single-image 2.4x on conversion.
**Watch this:** MQL volume at 78 vs. 100 target (−22%). Top-of-funnel content traffic dropped 18% week-over-week. Two blog posts scheduled for last week didn't publish. That's the gap.
**Three priorities this week:**
1. Publish the two delayed posts by Tuesday EOD.
2. Brief sales on the ABM playbook — replication opportunity in 3 named accounts.
3. Review paid search bid strategy — quality score dropped on 4 keywords.
**For leadership Slack:** Pipeline $340K, 114% of target. ABM is working — 18 new enterprise opps from the Tier 1 sequence. The miss: MQLs at 78 vs. 100 target. Two content pieces didn't ship last week. That's the gap, fixing it this week. Content backlog cleared by Tuesday, sales ABM briefing Thursday, paid search review Friday.How to adapt this skill for your team
This SKILL.md is intentionally opinionated. The goal isn't that every CMO uses it as written — it's that you fork it and make it yours. Three things to customize first:
- The Inputs list. If your team tracks different metrics (e.g., NRR, win rate, opportunity stage velocity), swap them in. The format works for any inputs as long as the metric → commentary → action chain holds.
- The Output format. Some leadership teams want a "What changed this week" section. Others want a "Risks I'm watching" section. Add or remove blocks to match how your CEO and board read briefs.
- The Rules section. This is where your taste lives. The banned phrases, the banned structures, the things that read as lazy writing in your company — bake them in. The Skill gets sharper with every rule you add.
After 2–3 runs, open /memory (in Claude Cowork) or update the SKILL.md directly (in Claude Code) based on what felt off in the output. Most CMOs need 2–3 refinement passes before the brief is send-ready every Monday.
Starter template
For a minimal copy-paste version of this Skill (closer to what fits on a single infographic), see references/starter-template.md. Use the starter when teaching the concept; use the full SKILL.md when running it.
Related skills
- product-marketing-context — Establish foundational positioning context that other skills can reference
- analytics-tracking — Set up the tracking that feeds this skill's inputs (GA4, conversion events, UTMs)
- revops — Lead scoring, routing, and pipeline definitions that determine what counts as an MQL
- paid-ads — Channel-level optimization for the campaigns this brief reports on
Background
This skill was published alongside a step-by-step LinkedIn infographic walking through the 9-step build process. The infographic and full backstory live at stackandscale.ai. For more practical AI workflows for B2B marketing leaders, the Stack & Scale newsletter ships weekly.
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
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.

