63 Campaign Retrospective Global logo

63 Campaign Retrospective Global

Community
minhnv0807
63-campaign-retrospective-global

Use when a campaign has ENDED and the team needs a structured retrospective — a scorecard against target, what worked, what did not, and why with evidence, surprises, process review, lessons written back into the playbook and Brand Hub, and action items with owners. Trigger on 'campaign retrospective', 'campaign retro', 'post-mortem', 'campaign debrief', 'what worked and what did not', 'the campaign is over, what did we learn'. Also use when a campaign underdelivered and the team is arguing about why. Not for — a periodic performance report, see `07-marketing-report-global`; diagnosing live numbers mid-flight, see `03-performance-eval-global`; the next period ads plan, see `57-next-ads-plan-global`.

Overview

Publisherminhnv0807
Repositoryai-business-skills
Skill name63-campaign-retrospective-global
Stars
612
Forks
228
Bundled files
Instructions only
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by minhnv0807 on GitHub. Read the source before you install it.

Installation

Install the 63 Campaign Retrospective Global AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/minhnv0807/ai-business-skills/tree/master/skills/en/63-campaign-retrospective-global
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/minhnv0807/ai-business-skills.git /tmp/ai-business-skills
mkdir -p .claude/skills
cp -r /tmp/ai-business-skills/skills/en/63-campaign-retrospective-global .claude/skills/63-campaign-retrospective-global
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable 63 Campaign Retrospective Global in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads 63 Campaign Retrospective Global on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so 63 Campaign Retrospective Global is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Campaign Retrospective (Global)

A retrospective is not for assigning blame — it is how the team and the system get better after every campaign. The best insight comes from failure, but only if it is safe to speak honestly. A retro with no action is wasted time: every lesson must become one concrete change in the playbook, the Brand Hub, or the process.

Information gathering

Ask up to 4 questions:

  1. Which campaign, and over what dates? Name, start and end dates, original objective.
  2. Final data: revenue, leads, CPA, ROAS, spend — final numbers versus target. (If a report already exists from 07-marketing-report-global, use it as the input.)
  3. Who attends the retro? Content, performance, design, sales, leader?
  4. How long ago did the campaign end? Run the retro within 5 days of the end, while memory is fresh.

Principles

  1. Mandatory after every major campaign. No skipping because the team is busy. No retro means paying tuition without learning the lesson.
  2. Record only claims backed by data. "Creative A felt strong" is not an insight; "creative A hit $18 CPA against a $28 account average" is.
  3. No individual blame. Talk about systems and process. Everyone has the floor.
  4. Every lesson becomes one concrete change — to the playbook, a template, the Brand Hub, or a process — with an owner and a deadline.
  5. Document so it still makes sense in 6 months — and link the retro into the next campaign's brief.

Workflow

1. Prepare (before the session)

  • Pull final data: revenue, leads, CPA, ROAS, spend, timeline adherence, budget variance.
  • Send the data to the team before the meeting — the meeting is for discussion, not for reading numbers.
  • Book 60 minutes with a named facilitator (usually the leader). For distributed teams, pick a time that works across the relevant timezones and require written pre-reads from anyone who cannot attend live.

2. Campaign scorecard

KPITargetActual% achievedvs previous campaign
Revenue
Leads
CPA
ROAS
Spend
Timeline (on schedule?)
Budget (within plan?)

Overall verdict: Success (>90% of KPIs) / Mixed (60-90%) / Miss (<60%).

When comparing against category benchmarks, use the right region and industry row in references/benchmarks-global.md — and adjust for seasonality before declaring a CPA increase a failure, since Q4 media costs run materially above Q1.

3. What worked (repeat next time)

#What workedEvidence (numbers)Why it workedHow to apply next time
1
2
3

Name the winning patterns explicitly:

  • Content angle: which angle converted best
  • Creative format: video / image / carousel — which performed
  • Audience: which segment responded
  • Timing: which day or hour performed best
  • Channel: best CPA and ROAS

4. What did not work (avoid next time)

#What failedEvidenceRoot causeDecision: stop / fix / retest
1
2

Root cause must go past the symptom. "The ads were bad" is not a root cause; "audience overlapped with the previous campaign > frequency rose above 4 > CTR fell below 1%" is.

5. Surprises

  • Positive surprises: what beat expectations, by how much, why — what do you take from it?
  • Negative surprises: what came in worse, by how much, why — how do you prevent it?

6. Process and execution review

ItemAssessmentProblems hitImprovement
Brief quality
Timeline adherence
Team communication
Review and approval process
Launch-day execution
Data and tracking setup

Biggest process bottleneck: the single thing most worth fixing next time.

7. Team callouts

Record specific contributions: [Name] — [the specific contribution and its positive impact on the result]. Recognize publicly, correct privately.

8. Playbook and Brand Hub updates plus action items

Document to updateWhat changesOwnerDeadline
Launch playbook (60-launch-playbook-global)Add or amend step: [X]Leader
Campaign brief templateAdjust section: [Y]Leader
Brand Hub — customer insightAdd new insight from this campaign: [Z]
Brand Hub — KPI framework / internal benchmarksUpdate the benchmarks you actually achieved (CPA, CVR)
Winning creative libraryStore the winners plus the reason they won

Every action item needs an owner and a deadline — never "the whole team will handle it."

9. Input for the next campaign

  • 3 things to definitely repeat: 1... 2... 3...
  • 3 things to definitely do differently: 1... 2... 3...
  • Hypothesis to test next campaign: [hypothesis + how it will be measured]

Facilitation guide

  • Timing: within 5 days of campaign end.
  • Format: 60 minutes, full team, facilitator (leader): 10 min scorecard > 15 min what worked > 15 min what did not > 10 min process > 10 min action items and owners.
  • Ground rules: no individual blame, systems and process only; everyone speaks; constructive, not a venting session.
  • After: the leader publishes the document within 24 hours, shares it with the team and leadership, and links it into the next campaign brief.

Output structure

File name: campaign-retro-[campaign-name]-[YYYYMMDD].md — the 9 sections above: scorecard > what worked > what did not > surprises > process review > team callouts > playbook and Brand Hub updates > input for the next campaign > action items with owners.

Related skills

  • 07-marketing-report-global: the final report supplies the scorecard data.
  • 60-launch-playbook-global: execution lessons are written directly back into the playbook.
  • 02-campaign-brief-global: the "lessons from the previous campaign" section of a new brief comes from this retro.
  • 34-ai-marketing-os-global: new insights and real benchmarks are written into the Brand Hub.
  • 65-team-performance-review-global: team callouts and observations feed individual reviews at period end — keep the two documents separate.

Quality checklist

  • Retro run within 5 days of campaign end
  • Scorecard covers all KPIs against target with a Success/Mixed/Miss verdict
  • Every "what worked" and "what did not" entry has numeric evidence — no impressions
  • Failures trace to a real root cause, not a symptom
  • Benchmark comparisons adjusted for region, industry, and season
  • At least one playbook update and one Brand Hub update
  • Every action item has an owner and a deadline
  • 3 things to repeat, 3 things to change, and a hypothesis for next time
  • No individual blame anywhere in the document
  • Document shared within 24 hours and linked into the next campaign brief

Frequently asked questions

What does the 63 Campaign Retrospective Global AI skill do?

Use when a campaign has ENDED and the team needs a structured retrospective — a scorecard against target, what worked, what did not, and why with evidence, surprises, process review, lessons written back into the playbook and Brand Hub, and action items with owners. Trigger on 'campaign retrospective', 'campaign retro', 'post-mortem', 'campaign debrief', 'what worked and what did not', 'the campaign is over, what did we learn'. Also use when a campaign underdelivered and the team is arguing about why. Not for — a periodic performance report, see `07-marketing-report-global`; diagnosing live...

Why use 63 Campaign Retrospective Global on TypingMind?

Because you install it once and use it with any model. 63 Campaign Retrospective Global is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install 63 Campaign Retrospective Global in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/minhnv0807/ai-business-skills/tree/master/skills/en/63-campaign-retrospective-global. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use 63 Campaign Retrospective Global?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with 63 Campaign Retrospective Global?

As many as you like. As long as a model supports skills, you can use 63 Campaign Retrospective Global with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the 63 Campaign Retrospective Global AI skill free?

Yes. It is published on GitHub by minhnv0807 under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇