MCP Urgent Caller Triage
zapier/gtm-cheat-codes
Prioritize inbound client calls by reading transcripts, classifying urgency, matching callers to legal client and matter context, and preparing a callback list for human review.
Explore what Zapier MCP can do for the user — interview them about their role and the apps they live in, suggest specific use cases as on-demand prompts, then walk them through enabling the actions…
$ npx skills add zapier/zapier-mcp --skill zapier-explore -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install zapier/zapier-mcp zapier-explore --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/zapier/zapier-mcp.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/zapier/skills/zapier-explore .claude/skills/zapier-explore && rm -rf skills-srcUse ~/.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/
Install the "zapier-explore" agent skill from https://github.com/zapier/zapier-mcp/tree/main/plugins/zapier/skills/zapier-explore into .claude/skills/zapier-explore/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "zapier-explore", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/zapier/zapier-mcp/tree/main/plugins/zapier/skills/zapier-exploreType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add zapier/zapier-mcp --skill zapier-explore -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install zapier/zapier-mcp zapier-explore --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/zapier/zapier-mcp.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/zapier/skills/zapier-explore .agents/skills/zapier-explore && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "zapier-explore" agent skill from https://github.com/zapier/zapier-mcp/tree/main/plugins/zapier/skills/zapier-explore into .agents/skills/zapier-explore/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "zapier-explore", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add zapier/zapier-mcp --skill zapier-explore -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install zapier/zapier-mcp zapier-explore --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/zapier/zapier-mcp.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/zapier/skills/zapier-explore .cursor/skills/zapier-explore && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "zapier-explore" agent skill from https://github.com/zapier/zapier-mcp/tree/main/plugins/zapier/skills/zapier-explore into .cursor/skills/zapier-explore/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "zapier-explore", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/zapier/zapier-mcp.git --path plugins/zapier/skills/zapier-explore--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add zapier/zapier-mcp --skill zapier-explore -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install zapier/zapier-mcp zapier-explore --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/zapier/zapier-mcp.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/zapier/skills/zapier-explore .gemini/skills/zapier-explore && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "zapier-explore" agent skill from https://github.com/zapier/zapier-mcp/tree/main/plugins/zapier/skills/zapier-explore into .gemini/skills/zapier-explore/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "zapier-explore", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install zapier/zapier-mcp zapier-exploreInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add zapier/zapier-mcp --skill zapier-explore -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/zapier/zapier-mcp.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/zapier/skills/zapier-explore .github/skills/zapier-explore && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "zapier-explore" agent skill from https://github.com/zapier/zapier-mcp/tree/main/plugins/zapier/skills/zapier-explore into .github/skills/zapier-explore/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "zapier-explore", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add zapier/zapier-mcp --skill zapier-explore -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install zapier/zapier-mcp zapier-explore --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/zapier/zapier-mcp.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/zapier/skills/zapier-explore .opencode/skills/zapier-explore && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "zapier-explore" agent skill from https://github.com/zapier/zapier-mcp/tree/main/plugins/zapier/skills/zapier-explore into .opencode/skills/zapier-explore/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "zapier-explore", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
zapier-exploreExplore what Zapier MCP can do for the user — interview them about their role and the apps they live in, suggest specific use cases as on-demand prompts, then walk them through enabling the actions…
Zapier Explore is an agent skill from zapier/zapier-mcp, published by the product's own GitHub organization. Explore what Zapier MCP can do for the user — interview them about their role and the apps they live in, suggest specific use cases as on-demand prompts, then walk them through enabling the actions to make those use cases real. The natural next step after zapier-demo. Use when the user asks "what else can Zapier do for me", "set up more tools", "add a starter pack for my role", "what should I enable next", "suggest workflows", "help me figure out what to do with Zapier", "I don't know where to start", or "give me…
Its SKILL.md is about 4k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Productivity & Automation, covering Workflow automation. It works with Zapier and Model Context Protocol. The repository describes itself as: Official plugin distribution for the hosted Zapier MCP server. Install it in your AI client and connect to thousands of apps. The licence is MIT.
6 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit 5360f15. It shows what the files ask for, not the result of running them.
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.
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.
Links to these hosts (documentation or services it may open):
docs.zapier.commcp.zapier.comzapier.comFrom URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Zapier Explore loads about 4k tokens when it runs. Until then it costs about 138 tokens; SKILL.md has 2,160 words of instructions outside code blocks.
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.
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.
The full file from zapier/zapier-mcp at commit 5360f15, republished under its MIT licence (© zapier). 2,160 words, ~3,991 tokens.
.claude/skills/zapier-explore/SKILL.md (or your agent's skills folder).Help the user expand beyond the first action — figure out what Zapier MCP can do for them based on their role and apps, then walk them through enabling a starter set of actions tailored to that work.
This is the natural follow-on to zapier-demo. Demo proves one action works; explore turns that into a real toolkit for the user's day-to-day.
For how the Zapier MCP server itself works, see docs.zapier.com/mcp.
If the user hasn't run their first action yet, route to zapier-demo first — explore works best after a win.
Keep it short — two or three questions, not a survey. Adapt follow-ups based on answers.
Open with:
"Let's figure out what to add to your Zapier toolkit. Quick context first — what do you do for work, and what apps are you in every day?"
Listen for:
If they give you only role or only apps, ask one follow-up. If they give you both, optionally ask:
"Is there a task you keep redoing manually that you'd love to delegate?"
Don't push past three questions. Move on with what you've got.
Pick the role library below that best matches the user's answers (multiple is fine — combine for hybrid roles). For each, surface 4–6 use cases tailored to the apps they mentioned. If they named an app you don't have in the library, default to the closest equivalent (e.g., "Outlook" → use the Gmail patterns; "Monday.com" → use the Asana patterns).
For each use case, output:
Format as a short prose block per use case, not a table. Don't list more than 6 use cases at once. If you have more, present them in waves — give 4, see if any land, then offer "want more?"
For the use cases the user reacts to ("yes that one"), produce a consolidated enable list grouped by app:
"To make those work, you'll need to enable:
- Slack: Send Channel Message, Find Message
- Jira: Find Issue by Key, Create Issue
- Google Calendar: Find Events"
Cross-reference the Recommended actions by app table below to fill any gaps — aim for 2–4 actions per app (1–2 search, 1–2 write).
Direct the user to their Zapier dashboard:
get_configuration_url tool, call it first and give them the direct link.Then tell them what to do:
"Open [that link], find your server, and add the actions in the list above. You'll also need to connect each app's account when prompted (OAuth). Come back and say done when everything is added."
Wait for confirmation. If they hit issues:
Re-inspect the available Zapier MCP tools and confirm the new actions are present. If anything is missing, troubleshoot with the user — most often a client reload is enough.
Once everything is enabled, name the win and offer a natural next step:
"You're set up with [N] tools across [App list]. Try one now — say something like '[example prompt tailored to their setup]' and I'll run it. Or run /zapier-status anytime to check the health of your tools."
Don't read the user every use case verbatim. Pick the most relevant ones for their context and present them as natural recommendations.
Use this as the reference when building the enable list in Step 3. Aim for 2–4 actions per app — one or two search actions and one or two write actions.
| App | Search actions | Write actions |
|---|---|---|
| Slack | Find Message, Get Message | Send Channel Message |
| Gmail | Find Email | Send Email, Create Draft |
| Google Calendar | Find Events | Create Detailed Event |
| Google Docs | Get Document Content | Create Document |
| Google Sheets | Get Data Range, Lookup Row | Add Row |
| Jira | Find Issue by Key, Find Issues via JQL | Create Issue |
| Linear | Find Issue | Create Issue |
| GitLab | Find Merge Requests | (read-heavy by nature) |
| GitHub | Find Issue, Find Pull Request | Create Issue |
| HubSpot | Find Contact, Find Company | Create Contact |
| Notion | Find Page, Find Database Item | Create Page |
| Zoom | Find Meeting | (read-heavy) |
| Coda | Find Row | Create Row |
| Airtable | Find Record | Create Record |
discover_zapier_actions is exposed by the server): if the user names something you're unsure about, you can silently call discover_zapier_actions to verify before recommending. Don't surface that detail unless the user asks.When presenting a use case, use this shape — short prose, not a table row:
[What the use case does, in plain language]
Say to me: "[exact prompt in quotes]". I'll [what the action does in one line].
Actions to enable: [App]: [Action], [Action]
Concrete, never abstract. Avoid "Zapier can help you streamline your workflow." Say instead "Try saying to me: 'Find the latest 3 Slack messages from #product-feedback' and I'll pull them for you." Show, don't pitch.
© zapier, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in plugins/zapier/skills/zapier-explore of zapier/zapier-mcp.
Open the folder on GitHubat commit 5360f15
Zapier Explore 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Zapier Explore this skillzapier/zapier-mcp | 428 | — | ~4k | Automated safety check: Pass | MIT | |
| MCP Urgent Caller Triagezapier/gtm-cheat-codes | 342 | — | ~1k | Automated safety check: Pass | MIT | |
| Zapierasgeirtj/system_prompts_leaks | 69k | — | ~328 | Automated safety check: Pass | CC0-1.0 | |
| N8nericrisco/rsc-harness | 167 | — | ~2.6k | Automated safety check: Notes | MIT | |
| Zapierericrisco/rsc-harness | 167 | — | ~2.8k | Automated safety check: Notes | MIT | |
| Zapier Workflowsdavila7/claude-code-templates | 32k | 2 repos | ~4.9k | Automated safety check: Pass | MIT |
zapier/gtm-cheat-codes
Prioritize inbound client calls by reading transcripts, classifying urgency, matching callers to legal client and matter context, and preparing a callback list for human review.
asgeirtj/system_prompts_leaks
Connect Muse to actions across apps through Zapier's official MCP server.
ericrisco/rsc-harness
A skill your agent uses when operating a live n8n instance programmatically — its REST API ({host}/api/v1, X-N8N-API-KEY) or the n8n-mcp server — to create, validate, test, activate, update, delete…
ericrisco/rsc-harness
A skill your agent uses when operating Zapier from an agent through the official hosted Zapier MCP server — connecting with a bearer key, discovering an app's actions, enabling one, and invoking a…
davila7/claude-code-templates
Manage and trigger pre-built Zapier workflows and MCP tool orchestration.
apify/agent-skills
Guides designing and building an official Apify integration for a company's product: workflow-automation apps, AI agent plugins, AI framework packages or direct API clients.
zapier/zapier-mcp
Walk a new user through setting up their first Zapier action and running it live — the smallest possible win.
zapier/zapier-mcp
Check the health of your Zapier MCP setup. An agent skill from zapier/zapier-mcp.
zapier/zapier-mcp
Onboard a new user to Zapier MCP — introduce what it can do, walk through authentication, and route into the right flow based on the state of their setup.
Works with
Categories
Explore what Zapier MCP can do for the user — interview them about their role and the apps they live in, suggest specific use cases as on-demand prompts, then walk them through enabling the actions…. Zapier Explore is an agent skill from zapier/zapier-mcp, published by the product's own GitHub organization. Explore what Zapier MCP can do for the user — interview them about their role and the apps they live in, suggest specific use cases as on-demand prompts, then walk them through enabling the actions to make those use cases real.
Zapier Explore fits situations like: the user asks what else can Zapier do for me; set up more tools; add a starter pack for my role; what should I enable next.
Run `npx skills add zapier/zapier-mcp --skill zapier-explore -a claude-code`. Or copy the skill folder (plugins/zapier/skills/zapier-explore in zapier/zapier-mcp) into .claude/skills/zapier-explore in your project. Claude Code loads it when a task matches its description.
Run `npx skills add zapier/zapier-mcp --skill zapier-explore -a codex`. Or copy the skill folder (plugins/zapier/skills/zapier-explore in zapier/zapier-mcp) into .agents/skills/zapier-explore in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add zapier/zapier-mcp --skill zapier-explore -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/zapier-explore, .gemini/skills/zapier-explore, .github/skills/zapier-explore and .opencode/skills/zapier-explore in your project.
SKILL.md names no scripts, command-line tools or credentials: Zapier Explore is instructions for the agent only.
SKILL.md names 3 domains. As links in the text: docs.zapier.com, mcp.zapier.com and zapier.com. This is read from the text; nothing was executed.
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.
Zapier Explore is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 4k tokens (SKILL.md is roughly 16k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Zapier Explore: MCP Urgent Caller Triage (zapier/gtm-cheat-codes, 342 stars), Zapier (asgeirtj/system_prompts_leaks, 69k stars), N8n (ericrisco/rsc-harness, 167 stars) and Zapier (ericrisco/rsc-harness, 167 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
zapier (a GitHub organization, an official publisher) maintains it in zapier/zapier-mcp, which has 428 GitHub stars. The repository holds 4 skills in this directory. The repository was last updated on July 29, 2026.
Source: zapier/zapier-mcp on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.