Build sourced campaign retrospectives from goals, launch context, performance data, team feedback, and follow-up actions.
SkillScore96Maintained
Automatic
◆Marketing & Content pack
Last verified 8/21/2026
What it changes
Passed 24 of 25 test cases with the skill, and 19 of 25 without it.
Without skill76%
With skill96%
Checks it passed that the model alone missed
Assigns reviewer routing to Zapier SDK
Explicitly labels performance metrics as missing data
Identifies campaign performance statistics as missing data
and 5 more in the full report
5 fixed19 passed either way1 still failing0 broke
Pass-rate lift
+20 pp
Tokens
-17%
Agent turns
0%
Response time
-36%
Model gemini-3.6-flashMeasured 8/21/2026v124 of 25 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 5 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 5
Prompt
We want to set up automated workflows for our quarterly campaign retrospectives. Which component should handle gathering approved campaign documentation versus routing reviewer approvals and logging follow-up actions?
What was checked, without and with the skill
Checked
Without skill
With skill
Assigns gathering approved campaign documentation to Zapier MCP
Missed
Passed
Assigns reviewer routing to Zapier SDK
Missed
Passed
case-19 · gemini-3.6-flash · 8/21/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md41 linessingle file
Campaign Postmortem
Use When
A marketing team needs to understand what happened in a campaign and turn the learning into better next-cycle decisions.
Workflow
Confirm campaign name, date range, goals, channels, and audience.
Gather approved source material: brief, launch plan, project notes, performance data, meeting notes, and team feedback.
Build a timeline of major decisions, launch events, results, and follow-up actions.
Compare goals to actual results with source references.
Separate observations from interpretations.
Identify what worked, what did not work, root causes, and open questions.
Recommend what to repeat, change, or stop.
Add an action register with owners, dates, and unresolved decisions when available.
Zapier MCP And SDK Role
Use Zapier MCP to gather approved campaign docs, conversations, dashboards, CRM context, meeting notes, and tracker state.
Use Zapier SDK for retro intake, scheduled reminders, reviewer routing, action logging, and follow-up tracking.
Keep metrics, claims, and broad sharing review-gated.
Output Format
Executive summary
Source list
Campaign timeline
Goal vs. actuals
What worked
What did not work
Root causes and caveats
Repeat / change / stop
Action register
Guardrails
Never invent metrics, attribution, causes, or owner commitments.
Label missing data and conflicting evidence.
Keep the retro focused on systems, decisions, and process, not personal blame.
Draft customer stories from approved transcripts, notes, briefs, quotes, and proof points. Use for narrative customer stories, campaign stories, and metric-forward customer story pages.