zapier/gtm-cheat-codes · Archived
Install and connect Zapier, routing to the right surface (MCP, SDK, or CLI) for what the person needs.
npx skills add zapier/gtm-cheat-codes --skill install-zapier
This repository is archived — consider an actively maintained alternative.
Prioritize inbound client calls by reading transcripts, classifying urgency, matching callers t…
5 installsAudit inbound lead handling and map the customer experience from source event to follow-up outc…
4 installsCoordinate opportunities and customer records across multiple CRMs while preserving attribution…
4 installsFind approved customer proof for campaigns, pages, decks, emails, and sales conversations. Use …
4 installsRelated neighbors and high-traction skills in the same topics — useful to compare before installing.
Install Codex skills into $CODEX_HOME/skills from a curated list or a GitHub repo path. Use whe…
3K installsInstall cuOpt for Python, C, or server via pip, conda, or Docker; verify the install. For build…
2.4K installsInstall and initialize the correct LaunchDarkly SDK during onboarding by running nested skills …
2.3K installsInstall and verify cuPyNumeric for Python — requirements, commands, verification. Source builds…
2K installsGuide installing Earth2Studio via uv or pip, selecting model extras, and configuring the enviro…
1.8K installsInstall Holoscan SDK via the NGC Docker container. Use for container-based installs; not for na…
1.8K installsOther skills from zapier/gtm-cheat-codes · top by installs.
npx skills add zapier/gtm-cheat-codes
Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.
main
Files included with this skill beyond the listing page.
SKILL.md
2,307 B
README.md
1,115 B
SUMMARY.md
355 B
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.
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.
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.
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.
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.