New: 97,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Official agent skill

Campaign Postmortem

by zapier in zapier/gtm-cheat-codes

Build sourced campaign retrospectives from goals, launch context, performance data, team feedback, and follow-up actions.

OfficialMITAuto-check passedDevOps & Cloud

Install Campaign Postmortem

skills CLI
$ npx skills add zapier/gtm-cheat-codes --skill campaign-postmortem -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install zapier/gtm-cheat-codes campaign-postmortem --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/zapier/gtm-cheat-codes.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/marketing/campaign-postmortem .claude/skills/campaign-postmortem && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
campaign-postmortem
GitHub stars
342
Token cost
~438 tokens
SKILL.md length
219 words
Files
6
Skills in repo
21
Repo updated
First seen
Licence
MIT

At a glance

Build sourced campaign retrospectives from goals, launch context, performance data, team feedback, and follow-up actions.

  • Works in 8 steps: Confirm campaign name, date range,… → Gather approved source material: brief,… → Build a timeline of major decisions,… → …
  • Tasks that involve Runbooks and postmortems
  • SKILL.md covers Use When, Workflow, Zapier MCP And SDK Role and Output Format, plus 1 more section
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Campaign Postmortem is an agent skill from zapier/gtm-cheat-codes, published by the product's own GitHub organization. Build sourced campaign retrospectives from goals, launch context, performance data, team feedback, and follow-up actions.

Its SKILL.md is about 440 tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files (for example `ONBOARDING-PROMPT.md`, `README.md` and `SCHEMA-MAP.md`).

It sits in DevOps & Cloud, covering Runbooks and postmortems, Retrospectives and Workflow automation. It works with Zapier. The repository describes itself as: A field guide for go to market teams using coding agents. Installable skills for campaign planning, CRM context, customer proof, and reviewable agent workflows. The licence is MIT.

When your agent uses it

  • Tasks that involve Runbooks and postmortems
  • Tasks that involve Retrospectives
  • Tasks that involve Workflow automation

Example prompts

  • “/campaign-postmortem”

Workflow steps

8 steps, taken from the first numbered list in SKILL.md.

  1. Confirm campaign name, date range, goals, channels, and audience.
  2. Gather approved source material: brief, launch plan, project notes, performance data, meeting notes, and team feedback.
  3. Build a timeline of major decisions, launch events, results, and follow-up actions.
  4. Compare goals to actual results with source references.
  5. Separate observations from interpretations.
  6. Identify what worked, what did not work, root causes, and open questions.
  7. Recommend what to repeat, change, or stop.
  8. Add an action register with owners, dates, and unresolved decisions when available.

What it can do on your machine

Read from SKILL.md and the folder at commit 022a288. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Campaign Postmortem loads about 438 tokens when it runs. Until then it costs about 35 tokens; SKILL.md has 219 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~35
When it runs · the whole SKILL.md, loaded when a task matches
~438

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from zapier/gtm-cheat-codes at commit 022a288, republished under its MIT licence (© zapier). 219 words, ~438 tokens.

Download SKILL.mdSave it as .claude/skills/campaign-postmortem/SKILL.md (or your agent's skills folder). This skill also uses 5 other files; get the full folder from GitHub.
name
campaign-postmortem
description
Build sourced campaign retrospectives from goals, launch context, performance data, team feedback, and follow-up actions.

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

  1. Confirm campaign name, date range, goals, channels, and audience.
  2. Gather approved source material: brief, launch plan, project notes, performance data, meeting notes, and team feedback.
  3. Build a timeline of major decisions, launch events, results, and follow-up actions.
  4. Compare goals to actual results with source references.
  5. Separate observations from interpretations.
  6. Identify what worked, what did not work, root causes, and open questions.
  7. Recommend what to repeat, change, or stop.
  8. 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.
  • Require human review before sharing broadly or updating source-of-truth records.

© zapier, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 5 other files in skills/marketing/campaign-postmortem of zapier/gtm-cheat-codes.

  • SKILL.md
  • ONBOARDING-PROMPT.md
  • README.md
  • SCHEMA-MAP.md
  • SETUP.md
  • metadata.yaml

Open the folder on GitHubat commit 022a288

Compare with similar skills

Campaign Postmortem next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Campaign Postmortem compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Campaign Postmortem this skillzapier/gtm-cheat-codes342—~438Automated safety check: PassMIT
Post Mortemalirezarezvani/claude-skills28k—~968Automated safety check: PassMIT
After Action Reportrampstackco/claude-skills9351 repos~2.5kAutomated safety check: PassMIT
Breach Patternsbriiirussell/cybersecurity-skills412—~3.5kAutomated safety check: NotesMIT
66 Crisis Playbook Globalminhnv0807/ai-business-skills608—~2.8kAutomated safety check: PassMIT
Incident RetrospectiveOpenHands/extensions157—~922Automated safety check: PassMIT

Similar skills

  • Post Mortem

    alirezarezvani/claude-skills

    /cs:post-mortem <decision — Honest retrospective on an executed decision, scored against original assumptions and dissent.

    28k GitHub stars~968 tokensUpdated 1 mo ago
    DevOps & CloudAuto-check passed

  • After Action Report

    rampstackco/claude-skills

    Run a structured after-action review (postmortem, retrospective) on a launch, incident, or completed project to capture timeline, root cause analysis, contributing factors, and actionable lessons.

    935 GitHub starsUsed in 1 repo~2.5k tokens
    Product & Project ManagementAuto-check passed

  • Breach Patterns

    briiirussell/cybersecurity-skills

    Learn from public breach disclosures — extract the audit question each one implies and check your own stack.

    412 GitHub stars~3.5k tokensUpdated 4 mo ago
    DatabasesAuto-check: notes

  • 66 Crisis Playbook Global

    minhnv0807/ai-business-skills

    A skill your agent uses when a brand faces a communications CRISIS or a campaign is failing in public — L1 to L5 severity classification, a first-four-hours process, response templates by type, an…

    608 GitHub stars~2.8k tokensUpdated 25 days ago
    Product & Project ManagementAuto-check passed

  • Incident Retrospective

    OpenHands/extensions

    Create an automation that drafts incident retrospectives. An agent skill from OpenHands/extensions.

    157 GitHub stars~922 tokensUpdated today
    Product & Project ManagementAuto-check passed

  • Report Generation

    seb1n/awesome-ai-agent-skills

    Generate professional reports — sprint retrospectives, financial summaries, analytics dashboards, and incident postmortems — from structured data with templates, charts, and multi-format output.

    206 GitHub stars~3.4k tokensUpdated 1 mo ago
    Documents & OfficeAuto-check passed

More from zapier/gtm-cheat-codes

All 21 skills in this repo

  • Customer Deck Builder

    zapier/gtm-cheat-codes

    Official

    Builds a tailored sales or customer success deck from approved CRM context and generates it in Gamma through Zapier MCP for calls like QBRs or renewals.

    342 GitHub stars~1.1k tokensUpdated 2 mo ago
    Auto-check passed

  • Customer Story Writer

    zapier/gtm-cheat-codes

    Official

    Drafts customer stories or metric-led story pages from approved transcripts, notes and quotes, keeping verified claims apart from ones that still need approval.

    342 GitHub stars~438 tokensUpdated 2 mo ago
    Auto-check passed

  • Customer Social Proof Finder

    zapier/gtm-cheat-codes

    Official

    Finds approved case studies, quotes, stats, logos and peer examples for campaigns, decks, emails and sales conversations, and flags anything that still needs approval.

    342 GitHub stars~468 tokensUpdated 2 mo ago
    Auto-check passed

  • Install Zapier

    zapier/gtm-cheat-codes

    Official

    Works out whether you need Zapier MCP, the SDK or the CLI, then walks through installing and verifying that one path step by step.

    342 GitHub stars~577 tokensUpdated 2 mo ago
    Auto-check passed

  • Media Inbox Triage

    zapier/gtm-cheat-codes

    Official

    Sorts a shared Gmail inbox for press, partnership and high-intent requests, scores urgency, suggests an owner and routes items through Zapier MCP for human review.

    342 GitHub stars~1.6k tokensUpdated 2 mo ago
    Auto-check passed

  • MCP Sheet Cache Bridge

    zapier/gtm-cheat-codes

    Official

    Designs an event-driven Google Sheets cache tab that mirrors a Zapier Tables source of truth, so spreadsheet-based tools keep working without direct API reads.

    342 GitHub stars~905 tokensUpdated 2 mo ago
    Auto-check passed

Works with

Categories

Questions about Campaign Postmortem

What does Campaign Postmortem do?

Build sourced campaign retrospectives from goals, launch context, performance data, team feedback, and follow-up actions. Campaign Postmortem is an agent skill from zapier/gtm-cheat-codes, published by the product's own GitHub organization. Build sourced campaign retrospectives from goals, launch context, performance data, team feedback, and follow-up actions.

When should I use Campaign Postmortem?

Campaign Postmortem fits situations like: tasks that involve Runbooks and postmortems; tasks that involve Retrospectives; tasks that involve Workflow automation.

How do I install Campaign Postmortem in Claude Code?

Run `npx skills add zapier/gtm-cheat-codes --skill campaign-postmortem -a claude-code`. Or copy the skill folder (skills/marketing/campaign-postmortem in zapier/gtm-cheat-codes) into .claude/skills/campaign-postmortem in your project. Claude Code loads it when a task matches its description.

How do I install Campaign Postmortem in Codex?

Run `npx skills add zapier/gtm-cheat-codes --skill campaign-postmortem -a codex`. Or copy the skill folder (skills/marketing/campaign-postmortem in zapier/gtm-cheat-codes) into .agents/skills/campaign-postmortem in your project. Codex loads it when a task matches its description.

Can I use Campaign Postmortem in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add zapier/gtm-cheat-codes --skill campaign-postmortem -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/campaign-postmortem, .gemini/skills/campaign-postmortem, .github/skills/campaign-postmortem and .opencode/skills/campaign-postmortem in your project.

What does Campaign Postmortem need to run?

SKILL.md names no scripts, command-line tools or credentials: Campaign Postmortem is instructions for the agent only.

Does Campaign Postmortem access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Campaign Postmortem safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Campaign Postmortem use?

Campaign Postmortem is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Campaign Postmortem use?

About 438 tokens (SKILL.md is roughly 1.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Campaign Postmortem?

Skills that share tags, products or a category with Campaign Postmortem: Post Mortem (alirezarezvani/claude-skills, 28k stars), After Action Report (rampstackco/claude-skills, 935 stars), Breach Patterns (briiirussell/cybersecurity-skills, 412 stars) and 66 Crisis Playbook Global (minhnv0807/ai-business-skills, 608 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Campaign Postmortem?

zapier (a GitHub organization, an official publisher) maintains it in zapier/gtm-cheat-codes, which has 342 GitHub stars. The repository holds 21 skills in this directory. The repository was last updated on July 13, 2026.

Source: zapier/gtm-cheat-codes on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.