n8n-subworkflows

Build reusable, composable n8n sub-workflows. Use when extracting shared logic, building anything multi-step or reused across workflows, or any workflow over ~10 nodes — and whenever the user mentions sub-workflows, Execute Workflow, reuse, shared/common logic, modular workflows, "Define Below" inputs, waitForSubWorkflow, mode each vs all, or exposing a workflow as an agent tool. Covers typed sub-workflow inputs, all-vs-each execution, verb-first naming for discovery, stateless vs stateful design, and splitting by input shape.

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

85%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The skill body is highly actionable and well-sequenced with concrete code and validation checkpoints, though it carries some motivational padding. Its main weakness is progressive disclosure: two referenced reference files are named but do not exist in the bundle, leaving dangling pointers.

Suggestions

Add the missing SUBWORKFLOW_PATTERNS.md and NAMING_AND_DISCOVERY.md to the references/ bundle, or remove the references and inline the essential content so no pointer is left dangling.

Trim narrative/motivational prose (e.g. 'badly underused', 'quietly drift apart', 'ambushes every caller') to tighten conciseness while keeping the actionable guidance intact.

If keeping the reference split, ensure each referenced file is one level deep and self-contained (no further indirection), and verify the paths resolve before shipping.

Dimension	Reasoning	Score
Conciseness	The body is mostly dense, domain-specific guidance, but carries motivational/narrative padding ('badly underused', 'quietly drift apart', 'ambushes every caller', 'earns its keep') that could be trimmed without losing actionable content.	4 / 5
Actionability	Provides copy-paste-ready executable content — the workflowInputs trigger JSON block, concrete MCP calls (n8n_list_workflows, n8n_get_workflow, n8n_test_workflow, validate_workflow), the mode all-vs-each table, and a decision tree covering common cases.	5 / 5
Workflow Clarity	Sequenced decision guidance, explicit contract rules, and a shipping checklist with validation checkpoints (validate_workflow, n8n_test_workflow) plus a field-rename feedback loop (migrate callers then verify); validation is present so no destructive/batch cap applies.	5 / 5
Progressive Disclosure	The reference table is well-signaled with 'Read when' guidance, but the referenced bundle files (SUBWORKFLOW_PATTERNS.md, NAMING_AND_DISCOVERY.md) are not present in references/, scripts/, or assets/, so the one-level-deep references do not resolve and the detailed content is unavailable.	3 / 5
	Total	17 / 20 Passed

Description

100%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is a strong, third-person statement that crisply states what the skill does and gives an exhaustive, natural-language trigger list. It is comprehensive, specific, and highly distinguishable from other skills.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete, domain-specific actions — 'typed sub-workflow inputs, all-vs-each execution, verb-first naming for discovery, stateless vs stateful design, and splitting by input shape' — with comprehensive coverage of the skill's capabilities.	5 / 5
Completeness	Explicitly answers both 'what' ('Build reusable, composable n8n sub-workflows... Covers typed sub-workflow inputs...') and 'when' ('Use when extracting shared logic... whenever the user mentions sub-workflows, Execute Workflow, reuse...') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Comprehensive natural trigger terms with synonyms: 'sub-workflows', 'Execute Workflow', 'reuse', 'shared/common logic', 'modular workflows', 'Define Below inputs', 'waitForSubWorkflow', 'mode each vs all', and 'exposing a workflow as an agent tool'.	5 / 5
Distinctiveness Conflict Risk	Occupies a clear n8n-sub-workflow niche with distinctive trigger terms (Execute Workflow, Define Below, waitForSubWorkflow, mode each vs all) that would not fire for unrelated skills.	5 / 5
	Total	20 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: czlonkowski/n8n-mcp
Path: data/skills/n8n-subworkflows/SKILL.md
Commit: fe3a4cb

Reviewed: 4 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.