Design reusable n8n sub-workflows with explicit input/output contracts.
npx skills add https://github.com/n8n-io/skills --skill n8n-subworkflows
Please help me install this Agent Skill. Skill: n8n-subworkflows Source: https://github.com/n8n-io/skills/tree/main/skills/n8n-subworkflows Command: npx skills add https://github.com/n8n-io/skills --skill n8n-subworkflows
This Skill helps you design multi-step n8n logic as reusable sub-workflows, so you stop duplicating workflows and instead build well-discoverable, composable building blocks.
Subworkflow: prefixing and search queries to reuse existing logic instead of recreating it.Execute Workflow Trigger with Define Below typed fields for agent/tool wiring, and use passthrough only for true binary or intentional zero-input cases.mode: 'each' with fire-and-forget parallelization.Use the sub-workflow guidance to decide whether to extract a chunk, then create the sub-workflow with a Subworkflow: verb-first name and a description that states inputs, outputs, and keywords for future search.
High-intent search queries and answers about installing and using this skill.
To create reusable n8n sub-workflows, use the Execute Workflow Trigger with Define Below typed fields to enforce explicit input and output contracts, enabling composable and discoverable workflow building blocks.
The best way to run parallel fire-and-forget tasks in n8n is by applying the mode: 'each' pattern within your sub-workflow orchestration, allowing simultaneous processing while tracking stateless or stateful executions safely.
The Execute Workflow Trigger handles typed inputs for agent tools by using the Define Below option, which provides a strict schema that supports accurate parameter filling when the sub-workflow is called as an agent tool.
You should use passthrough mode in an n8n sub-workflow only for true binary data passing or intentional zero-input cases, preferring typed Define Below fields for standard agent tool wiring and explicit contracts.
n8n sub-workflows fail to show up in agent search queries when they lack consistent verb-first naming with a Subworkflow: prefix and descriptions containing relevant keywords, which are required for MCP search discovery.
You extract multi-step n8n logic into a composable orchestration pattern by isolating coherent chunks of five or more nodes into a sub-workflow, then calling them linearly via the Execute Workflow node with safe waitForSubWorkflow behavior.
icednutGenerate unit and integration test scenarios from n8n workflow design documents.
OnClickListener2048Design, build, test, and deploy MCP servers with TypeScript or Python.
pokgakList, update, trigger, and retry n8n workflow executions via API.
multiplex-aiGuide a five-step research-before-coding workflow to find existing tools.