ericrisco/rsc-harness / skills/zapier
zapier
VerifiedUse 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 read or write action or firing a Catch Hook trigger across thousands of apps by natural language. Note there is no public API for creating or updating your own Zaps on a normal account, so say so and route onward. NOT deciding what a flow should be or its error and dedup design (that is `automation-flows`), NOT workflow CRUD, which `n8n` and `make` do support.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 11.0 KB |
| evals/README.md | markdown | 1.1 KB |
| evals/cases.yaml | config | 4.2 KB |
| references/programmatic-limits-and-partner-api.md | markdown | 3.6 KB |
| references/when-to-use-vs-n8n-make.md | markdown | 3.2 KB |
| references/zapier-mcp-tools.md | markdown | 4.9 KB |
evals/README.md
View on GitHub# Evals — zapier
`cases.yaml` has three groups. `should_trigger` covers the real Zapier MCP surface — Bearer connect, discover/enable/invoke of read and write actions, the 2-tasks-per-call cost question, and (crucially) the "is there an API to manage my Zaps?" prompt the skill must catch in order to answer honestly — with Spanish and Catalan phrasings. `should_not_trigger` routes adjacent asks to named siblings: flow design → automation-flows, programmatic workflow CRUD → n8n, operating Make's API → make, typed code client → api-connector-builder, inbound receiver → webhooks. The two `capability` scenarios assert the MCP connect/invoke flow (endpoint, Bearer, `.env`, discover→enable→invoke, write confirmation, 2-task cost, Enterprise-not-enforced) and the honest-boundary behavior (no public Zap-CRUD API → route to n8n/Make, don't fake one).
No automated runner. Score by judgement: feed each trigger/no-trigger prompt to the routing layer and confirm it activates or routes to the listed sibling; for each `capability`, have the skill respond and check every `must_include` bullet by hand.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| brainstormingobra/superpowersYou MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation). | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| brand-guidelinesanthropics/skillsApplies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| frontend-designanthropics/skillsGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| mcp-builderanthropics/skillsGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK). | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |