create-zap-templatelisted
Install: claude install-skill zapier/awesome-zaps
# Create a Zap template
One source in, one zap folder out, ready for a pull request to [zapier/awesome-zaps](https://github.com/zapier/awesome-zaps). Anyone can then install it by telling their agent "Build me this Zap, read how here: <folder link>".
## Before you start
- **Zapier MCP** connected in this session. Without it, stop and tell the user.
- **A local clone of awesome-zaps.** Read its `AGENTS.md` (the Workflows and Documentation sections) and `CONTRIBUTING.md` first. They own the format and win wherever this skill disagrees.
- **Examples:** the zaps in `zaps/`. Read a few, including one that uses the same apps if there is one.
## 1. Get the source
**From a zapier.com automation page:** every page under `zapier.com/automations/...` has a Markdown build recipe at the same URL plus `.md` (`curl -sL "<page-url>.md"`). Build only its spec; its Customize section becomes Notes in the SKILL.md, not code. `zapier.com/templates/...` pages have no recipe: find the matching `zapier.com/automations` page, or ask the user to pick one that has it.
**From a Zap the user already runs:** read it from their account. A workflow: `get_workflow`, and take `workflow.ts`, the trigger and the connections from its current version. A classic Zap: ask the user for its editor link, then `import_zap_to_workflow` with `private: true` and read the converted draft. Every ID in it belongs to the user; step 3 replaces each one.
Name the folder after what the Zap does, verb first, in kebab-case