n8n-workflow-builder
Skill0 starsChanged 45 days agoMITView on GitHub
Design an n8n automation workflow from a plain-language description and the tools involved, the node structure, the API endpoints, error handling, and test steps. Use when the user wants to "automate" an outbound or ops task, mentions n8n or Zapier-style automations, or describes a multi-tool workflow (e.g., "when a lead replies, enrich and push to CRM"). Returns a buildable node-by-node plan, not vague advice.
4 other projects use a version of this.
Adopted by
Most recently taken up by
- vicfromthegtmclub/gtmskillstheir own version, first seen Aug 10, 2026
- cxm-ict/claude-skillstheir own version, first seen Apr 21, 2026
- l3mpire/claude-skillstheir own version, first seen Apr 13, 2026
- vbrevik/claude_code_skillstheir own version, first seen Mar 14, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 4
- l3mpire/claude-skills★ 9same name
- cxm-ict/claude-skills★ 1same name
- vicfromthegtmclub/gtmskills★ 1same name
- vbrevik/claude_code_skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository15 other files it gives its agents.
- cold-call-scriptSkill
- competitor-finderSkill
- copywriting-first-touchSkill
- copywriting-follow-upSkill
- copywriting-linkedin-dmSkill
- deep-company-analyserSkill
- icp-definerSkill
- offer-definerSkill
- outreach-strategistSkill
- pain-identifierSkill
- persona-definerSkill
- pipeline-analyserSkill
- reply-rate-analyserSkill
- tam-sam-som-sizerSkill
- value-prop-listerSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 18
Add error handling: what can fail (rate limits, missing fields, bad data) and the retry, fallback, or alert node for each.
- Distinctive: line 27
Keep it buildable. Flag any assumption that needs the user's specific account, field names, or API version.
“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
n8n Workflow Builder
Outbound scales on automation. This skill turns "I want X to happen automatically" into a workflow you can actually build in n8n, node by node.
Input needed
- A plain-language description of what should happen, with the trigger and the desired end state.
- The tools involved (e.g., Apollo, a CRM, Slack, Google Sheets, an email tool, an LLM).
Method
- Restate the workflow as a trigger plus a sequence of steps, and confirm the goal.
- Lay out the node structure in order: the trigger node, then each action or transform node, with what each one does.
- For each integration node, name the API endpoint or operation and the key fields it needs (auth, inputs, outputs). Where you're unsure of an exact endpoint, say so and point to where to confirm it rather than guessing.
- Add error handling: what can fail (rate limits, missing fields, bad data) and the retry, fallback, or alert node for each.
- Give test steps: how to test with a single record before turning it on, and what to check.
Output
- The node-by-node structure (numbered), each node's purpose and key fields.
- API endpoints or operations per integration node.
- An error-handling plan.
- A short test checklist to run before going live.
Keep it buildable. Flag any assumption that needs the user's specific account, field names, or API version.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.