n8n-subworkflows
Skill0 starsChanged 2 months agoNo licenceView on GitHub
Use when building anything multi-step, anything that looks repeatable, anything the user mentions reusing, or any workflow with more than ~10 nodes. Triggers on "reuse", "I do this in another workflow", "extract", "modular", "shared logic", "subworkflow", multi-step builds, or any task that mentions logic the user has built before.
6 other projects use a version of this, 5 of them edited.
Adopted by
Most recently taken up by
- delorenj/skillsedited, first seen Nov 7, 2026
- Mfrostbutter/n8n-workflow-harnessedited, first seen Nov 1, 2026
- WilkoMarketing/antigravity-n8n-skillsedited, first seen Oct 6, 2026
- nomdedev/agent-manager-templateedited, first seen Sep 30, 2026
- czlonkowski/n8n-skillsedited, first seen Aug 29, 2026
- tmolavi/n8n-agent-skillstheir own version, first seen Aug 27, 2026
Used with
Projects with it also use n8n-code-tool, n8n-multi-instance and 8 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
czlonkowskiSkilln8n-code-tool
Write JavaScript or Python for the n8n Custom Code Tool (@n8n/n8n-nodes-langchain.toolCode) — the AI-agent-callable tool, NOT the workflow Code node. Use when building a Code Tool attached to an AI Agent, writing code that an LLM will invoke, parsing the `query` input, returning a string result, defining an input schema for structured arguments (specifyInputSchema, jsonSchemaExample, DynamicStructuredTool), or troubleshooting errors like \"Wrong output type returned\", \"No execution data available\", \"The response property should be a string, but it is an object\", \"Cannot assign to read only property 'name'\", or an AI agent that refuses to call the tool. Covers the critical differences between Code node and Code Tool: return format (string vs `[{json:{...}}]`), unavailability of `$fromAI`/`$input`/`$helpers` in the Code Tool sandbox, naming rules for AI invocation, and when to use `toolWorkflow`/HTTP Request Tool instead.
Also in 3 projects that use this
czlonkowskiSkilln8n-multi-instance
Use when an n8n-mcp account targets more than one n8n instance — i.e. the `n8n_instances` tool is available, the user mentions multiple n8n instances or environments (prod vs staging, several teams or clients), several agents or chats work on one account in parallel, a workflow / datatable / credential / execution call returns an unexpected NOT_FOUND or reads data you don't recognize, or a call is refused with `INSTANCE_AMBIGUOUS` or `INSTANCE_NOT_FOUND`. Covers naming the target instance on each call with the `instance` argument, setting the default with `switch`, verifying the target before high-stakes work — credential writes above all — and recovering from misroutes and fail-closes. Always consult this skill before operating on a specific instance, before any credential create/update/delete on a multi-instance account, or when a call hits the wrong/empty data or an instance error.
Also in 3 projects that use this
tygwanSkilln8n-code-javascript
Expert guidance for writing JavaScript in n8n Code nodes. Covers execution modes, data access patterns, return formats, and common pitfalls. Essential for n8n workflow automation with custom code.
Also in 3 projects that use this
tygwanSkilln8n-mcp-tools-expert
Master guide for using n8n-mcp MCP server tools to build workflows. Covers 40+ tools, node type formats, tool selection priority, validation workflows, and iterative building strategies.
Also in 3 projects that use this
- +2 more from czlonkowski
- +4 more from tygwan
Other versions6 projects use a version of this.
Word for word · 0
None found.
Edited · 5
- czlonkowski/n8n-skills★ 6.5k13% same
- WilkoMarketing/antigravity-n8n-skills★ 10613% same
- delorenj/skills★ 1713% same
- nomdedev/agent-manager-template★ 213% same
- Mfrostbutter/n8n-workflow-harness★ 013% same
Wrote their own version · 1
- tmolavi/n8n-agent-skills★ 1same 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 repository47 other files it gives its agents.
- .claude/skills/learn--project-mentor/CLAUDE.mdCLAUDE.md
- Agent DevelopmentSkill
- agnoSkill
- api-designerSkill
- devops-engineerSkill
- monitoring-expertSkill
- senior-architectSkill
- connect-appsSkill
- artifacts-builderSkill
- webapp-testingSkill
- pandas-proSkill
- postgres-proSkill
- sql-proSkill
- code-refactoring-refactor-cleanSkill
- python-proSkill
- security-reviewerSkill
- test-masterSkill
- typescript-proSkill
- ui-ux-expert-skillSkill
- project-mentorSkill
- skill-auditSkill
- meta--skill-lintSkill
- n8n-agentsSkill
- n8n-binary-and-dataSkill
- n8n-code-nodesSkill
- n8n-credentials-and-securitySkill
- n8n-data-tablesSkill
- n8n-debuggingSkill
- n8n-error-handlingSkill
- n8n-expressionsSkill
- n8n-extending-mcpSkill
- n8n-loopsSkill
- n8n-node-configurationSkill
- using-n8n-skillsSkill
- n8n-workflow-lifecycleSkill
- product-discoverySkill
- project-plannerSkill
- tools--cavecrewSkill
- tools--caveman-commitSkill
- tools--caveman-compressSkill
- tools--caveman-helpSkill
- tools--caveman-reviewSkill
- tools--cavemanSkill
- tools--caveman-statsSkill
- tools--codex-workflowSkill
- context7-mcpSkill
- graphifySkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
14 rules. 0 are common, 10 are distinctive, and 4 are very specific to this project.
0
Common
Most of the 6 edited versions we read keep these.
10
Distinctive
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
“Common” is measured: kept by at least 6 in 10 of the 6 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.
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.

