mcpbeat

Mega Campaign Generator

zapier/mega-campaign-generator

Build review-first outbound campaign packages from source context for marketing and sales teams.

1k tokens
context cost
the whole folder, loaded on every use
6
files
instructions only
0
copies elsewhere
how many repositories repackaged it
317
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/zapier/gtm-cheat-codes --skill mega-campaign-generator

The instruction itself

4 sections, as written by the author

Mega Campaign Generator

Use this skill to turn campaign context into a practical outbound package. It is a drafting orchestrator, not an autonomous campaign operator.

Workflow

  • Gather the best available context from user input, docs, CRM, meeting notes, and chat or collaboration tools threads.
  • Identify the audience, signal, offer, sender, channel mix, and closest reference examples.
  • Produce a strategy checkpoint before full copy.
  • After approval, draft subject lines, email steps, LinkedIn copy, and operator notes.
  • Clearly label assumptions and unsupported claims.

Zapier MCP And SDK Role

  • Use Zapier MCP to read approved docs, CRM context, campaign notes, collaboration threads, and reference assets.
  • Use Zapier SDK for campaign request intake, scheduled package generation, review routing, and tracker logging.
  • Keep sends, CRM writes, public posts, and customer claims human-approved.

Guardrails

  • Do not invent customer proof, usage data, executive participation, or operational support.
  • Do not send or schedule outreach without explicit human approval.
  • Avoid surveillance-style language when using product, page, or intent signals.
  • Keep the first output easy to review before expanding it into a full sequence.

How to use it

Copy the folder

Take zapier/mega-campaign-generator from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.