Turn a workflow idea into a build-ready automation prompt.
Turns a workflow idea into a build prompt with the trigger, ordered steps, data flow, branches, and error handling.
Inside: The trigger / steps / data-flow / branches / error-handling scaffold.
Install it in one line, or paste it in.
~/.claude/skills/ and runs automatically when it is relevant.Connect your context. Set it to your motion.
| Set this | What it is | Example |
|---|---|---|
| Target platform | The tool you will build in | n8nMakeZapier |
| Your apps | The services in your stack the workflow will touch | Your CRMyour emailyour sheet |
| Error policy | What should happen when a step fails | "Log it and notify medo not retry silently" |
Everything the skill does, in full.
Takes a workflow idea in plain words and returns a build prompt structured for an automation platform: the trigger, the steps in order, the data that moves between them, the branches, and the error handling. Automations break on the details. This pins them down before you build.
- 11. State the trigger precisely: what event starts this, and how often it can fire.
- List the steps in order, each as "take this, do that, pass this along."
- Name the data that moves between steps. The field that step 2 needs from step 1 is where automations break.
- Add the branches: "if the record already exists, update it; if not, create it."
- Add error handling: what happens when a step fails or returns nothing.
- Add a test plan: the one input you will run through it to confirm it works end to end.
Platform: n8n.
Trigger: webhook, fires when the website form is submitted. Expect { name,
email, company, message }.
Steps:
1. Look up the email in the CRM (search by email).
2. Branch:
- If found: update the record, append the message to notes.
- If not found: create a new lead with the form fields.
3. Post to Slack #leads: "New lead: {name} at {company}. {message}"
Error handling: if the CRM step fails, post to Slack #alerts with the error and
the raw payload. Do not drop the lead silently.
Test: submit one form with a known email and one with a new email. Confirm one
updates and one creates.
Where an operator takes this next.
Hand-building one automation proves the shape. Here's the operator version.
The prompt is the blueprint. The platform just needs it spelled out once.
Paste the build prompt into the platform's AI workflow builder so the trigger, branches, and error handling assemble themselves instead of you clicking through nodes one by one.
Keep the build prompt in a doc alongside the live automation, so when it breaks in six months you have the spec to rebuild from instead of reverse-engineering a tangle of nodes.
Once this one posts to Slack, add a second automation prompt that watches that channel and books a follow-up task in your CRM automatically.
One skill is the on-ramp.
A single skill does one job. Chained into a playbook, or run as a full build, it becomes a system. Here is where this one plugs in.