GTM Cheat Codes skill
Zapier's GTM team skills for coding agents: marketing campaigns, lead work, customer stories and support tickets
- 351 ★ on the repository
- Last commit
- MIT
Broad access
Why this level
- Through Zapier MCP the skills work with CRMs, email and meeting recordings, that is with customer and personal data
- Some scenarios write to systems of record and send messages on your behalf
- Access to connected systems depends on your Zapier setup, so start with read access
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add skills/gtm-cheat-codesDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- Through Zapier MCP the skills work with CRMs, email and meeting recordings, that is with customer and personal data
- Some scenarios write to systems of record and send messages on your behalf
- Access to connected systems depends on your Zapier setup, so start with read access
This is third-party code. Review the repository files before installing.
What it does
GTM Cheat Codes collects the working skills Zapier's go-to-market teams use. They turn scattered context from CRMs, docs, chat and other systems into reviewable work products. The repository targets Codex, Claude Code, Cursor and similar environments, and the agent reaches systems through Zapier MCP or the Zapier SDK. Skills are grouped by area under `skills/`, from marketing and sales to support, legal operations and content. Marketing gets a campaign generator and campaign postmortems. Sales gets a search for missed or slow lead follow-up, target account ranking and outreach drafts. Other skills triage a shared press and partnerships inbox, build customer decks and sync opportunities across several CRMs. Each skill sits in its own folder with a README, SKILL.md, SETUP.md and a schema map. The registry/skills.csv registry describes each skill's purpose, the Zapier MCP role and approval gates. The principle is shared: conclusions cite sources, and messages, CRM edits and publications go through human approval.
Who it is for. For marketers, sellers, RevOps and support teams who automate repeatable work through a coding agent.
Good fit when
- After a campaign you need a sourced retro: what worked, what broke, what comes next
- A shared press and partnerships inbox must not miss urgent requests
- You want leads with missed or slow follow-up found and owner-ready actions produced
- You need a customer story draft built from approved interviews and quotes
- You want to set up Zapier and let the agent choose between MCP, the SDK and the CLI
Not a fit when
- You do not use Zapier: the skills assume access to systems through Zapier MCP and the SDK
- You want blind automation with no approvals: the repository requires human approval before sending and CRM writes
- You need a finished product with no adaptation: some skills are marked in the registry as ready for adaptation and must be fitted to your systems
- Customer data cannot be handed to an agent even in anonymized form
Example request
Read skills/marketing/campaign-postmortem/SKILL.md and build a postmortem of the spring campaign from the sheet data and team notes, with sources and next stepsLimitations
You need Zapier and the connected CRM, email, sheets and other systems listed in each skill's SETUP.md. Skill status in the registry varies, from ready for adaptation and a first source-backed version to helper and advanced patterns.
The authors advise treating CRM data, transcripts, emails, web pages and company notes as sensitive. They suggest sanitized data for examples and least-privilege access.
Whether Zapier is reachable from Russia has not been checked.
How to disable. Delete the skill folders you copied into the project skills directory or `~/.claude/skills/`. If you connected Zapier MCP, revoke access in Zapier settings and remove the server from the client configuration.
FAQ
Where do I start with the set?
Read `docs/vp-marketing-skill-breakdown.md`, which describes every skill in plain language. Then find the skill closest to your task in `registry/skills.csv`, open its folder and read the README, SKILL.md, SETUP.md and SCHEMA-MAP.md where present.
What does the install-zapier skill do?
It finds out what you need and walks you down the right path: Zapier MCP for connecting apps to Claude, ChatGPT or Cursor, the SDK for code or the CLI for the terminal. If you are unsure it suggests starting with MCP. After each step it verifies the connection works, beginning with read or draft actions.
How do I connect the set to Claude Code?
The repository has a plugin manifest `.claude-plugin/plugin.json` listing skill folders. The simplest route is to clone the repository and copy the folders you need from `skills/` into the project's `.claude/skills/` or `~/.claude/skills/`.
How do I find out which systems a skill needs?
Open SETUP.md in the skill's folder, then SCHEMA-MAP.md where present: the first covers connection setup, the second the data schema.
What is in the automations folder?
Templates for recurring processes, such as a daily lead audit and a weekly analysis of unconverted leads. You find the right template in the same registry/skills.csv registry.
Discussion
No questions or reviews yet.
Related
SkillsA skill that connects two Avito MCP servers: the official API for your own account and public search for competitor research
Marketplace seller skills on top of marketplaces-mcp-ru
seller-skills-ru
Six task-shaped skills instead of raw API methods: stock reconciliation, sales export, listings, unit economics, ads and supplier prices
YouGile cards from chat: a Hermes skill
yougile-cards
A skill for creating and managing YouGile cards via REST API v2 with a stdlib-only Python client, built for the Hermes agent
Telegram lead-qualification skill with amoCRM
Universal AI Sales Agent
Three skills and a reference Telegram lead-qualification agent: free-form dialog, 0-100 scoring, RAG over a client base, amoCRM write-back
A skill for agent work with the amoCRM API v4: search, create and update deals, contacts, companies, tasks and notes
Cold Outbound Skills
coldoutboundskills
31 skills for Claude Code on cold email: strategy, infrastructure, lead sourcing, copy and deliverability checks. Your own API keys are needed
Comparison with similar tools
Entries that share the main search query, and how they differ.
| Entry | Official | Authentication | Repository stars | Main difference |
|---|---|---|---|---|
| GTM Cheat Codes (this entry) | yes | 351 | ||
| Zapier MCP | yes | OAuth | 451 | the official Zapier MCP plugin giving an agent actions in thousands of apps |
| GTM Engineer Skills | no | 1,340 | skills for promoting a site in ChatGPT, Claude and Perplexity answers |
README in short
The description presents the repository as a starter kit and breaks business tasks into groups. A repository map, the way to work with the skill registry and a section on safety boundaries follow.
README badge
Original SKILL.md
--- name: install-zapier description: Install and connect Zapier, routing to the right surface (MCP, SDK, or CLI) for what the person needs. Use when someone says "install Zapier", "add Zapier", "connect Zapier", or "set up Zapier", or when they want an AI client (Claude, ChatGPT, Cursor) to use their apps, want to call Zapier from code, or want Zapier in the terminal. --- # Install Zapier Use this skill when a person says "install Zapier" and may not know which Zapier surface they need. Do not make them pick a product. Ask what they want to do, then walk them through the right path one step at a time. ## Step 1: Find The Right Path Ask one or two plain questions, then map the answer. | What they want | Path | Why | |---|---|---| | Claude, ChatGPT, or Cursor to use their apps now | Zapier MCP | Connect tools to an AI client, no code | | To build an app or agent in code | Zapier SDK | Call Zapier as a library: code, state, retries, schedules | | To drive Zapier from the terminal | Zapier CLI | Standalone global install; bundles the SDK | | Not sure | Start with Zapier MCP | Fastest path to a working agent | The SDK and CLI are separate installs. Pick the SDK for a code project, the CLI for terminal-only work. If they want an AI client now and durable workflows later, set up MCP first, then the SDK. ## App Connectors These three paths are how a person installs Zapier itself. Individual app connectors are a separate thing: per-app integration skills (for example Notion) that a person installs when they need a specific app. Point them to those only after the core install, and only for the app they named. See the note at the end of `INSTALL-PATHS.md`. ## Step 2: Walk The Chosen Path Open `INSTALL-PATHS.md` and follow the section for the chosen path. Do one step at a time. Confirm each step worked before moving to the next. ## Step 3: Verify Run the verify check at the end of the chosen path section before telling the person they are done. Confirm the connection works with a read-only or draft-only action first. ## Guardrails - Never have the person paste API keys or tokens into chat. Use the auth flows linked in each path. - Use least-privilege. Add only the tools the person actually needs. - Keep human approval before any send, post, CRM write, or publish.