CtrlK
BlogDocsLog inGet started
Tessl Logo

n8n-workflow-patterns

Proven workflow architectural patterns from real n8n workflows. Use when building new workflows, designing workflow structure, choosing workflow patterns, planning workflow architecture, or asking about webhook processing, HTTP API integration, database operations, AI agent workflows, batch processing, or scheduled tasks. Always consult this skill when the user asks to create, build, or design an n8n workflow, automate a process, or connect services — even if they don't explicitly mention 'patterns'. Covers webhook, API, database, AI, batch processing, and scheduled automation architectures. Also use when optimizing a slow workflow or speeding up large-item-count processing (node count, batchSize, all-items vs per-item).

67

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Critical

Do not install without reviewing

The canonical home for this skill is n8n-workflow-patterns in czlonkowski/n8n-skills

SKILL.md
Quality
Evals
Security

Quality

Content

73%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 body is exceptionally actionable and its multi-step workflows (build → validate → verify → test → activate) are exemplary, but it fails at its own architecture: it advertises five detailed pattern files that are missing from the bundle, while inlining hundreds of lines of that detail directly. Combined with triple-listing of the patterns and several restatement sections, the token budget is noticeably overdrawn.

Suggestions

Ship the five referenced pattern files (webhook_processing.md, http_api_integration.md, database_operations.md, ai_agent_workflow.md, scheduled_tasks.md) or remove the dead links — every 'Detailed Pattern Files' and 'Core Patterns' link currently resolves to nothing.

Consolidate the three enumerations of the six patterns ('The 6 Core Patterns', 'Pattern Selection Guide', 'Detailed Pattern Files') into a single pattern-selection section, and cut 'Pattern Statistics' and 'Real Template Examples', which restate earlier content without adding operational guidance.

Move the fully-inlined Batch Processing pattern, Quick Start Examples, and Integration-Specific Gotchas into the pattern/reference files they describe, leaving SKILL.md as a lean overview with one-level-deep links.

DimensionReasoningScore

Conciseness

The core sections (lifecycle gates, batch processing, performance, integration gotchas) are dense and lean, but the document repeats itself: the six patterns are enumerated three times ("The 6 Core Patterns", "Pattern Selection Guide", "Detailed Pattern Files"), and "Pattern Statistics", "Real Template Examples", "Best Practices", and "Summary/Next Steps" largely restate earlier content. Not 2 because the majority of the body is genuinely efficient expert knowledge; not 4 because the redundant listings and restatement sections are a real, trimmable token cost.

3 / 5

Actionability

Fully concrete throughout: exact commands ("Run validate_workflow on the full JSON", "n8n_get_workflow({ id })", "activateWorkflow operation"), copy-paste code (the Math.abs threshold check, the dry-run tolerance snippet), specific wiring rules ("Always add a Limit 1 node after the done output"), and precise numbers ("~0.8 ms/iteration", "batchSize=1000", the uc?id= download URL format). The common cases are covered with executable guidance.

5 / 5

Workflow Clarity

The "validate, verify, test before activating" section gives a clearly sequenced four-gate process with explicit feedback loops ("Fix every error and re-validate") and a warning about real side effects during testing; the phased creation checklist (Planning → Implementation → Validation → Deployment) reinforces it. Batch and live-deployment operations have validation checkpoints, so no cap applies.

5 / 5

Progressive Disclosure

The five pattern-file links ([webhook_processing.md](webhook_processing.md) etc.) are clearly signaled and one level deep, but none of the referenced files exist in the bundle — every "Detailed Pattern Files" link is dead. Meanwhile ~540 lines of detail (the fully inlined Batch Processing pattern, quick-start examples, template examples, gotchas) sit in SKILL.md itself, i.e., content that clearly belongs in separate files is inlined. Not 1 because the document itself is well-sectioned and navigable, not a wall of text.

2 / 5

Total

15

/

20

Passed

Description

91%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.

A strong description: explicit what and when, dense with natural trigger terms including performance-tuning triggers, and clearly n8n-specific. Minor weaknesses are mild redundancy across its three trigger sentences (near-synonyms like "building/designing/planning") and an over-broad "always consult... even if they don't mention 'patterns'" clause that slightly inflates conflict risk.

DimensionReasoningScore

Specificity

Quotes like "Proven workflow architectural patterns from real n8n workflows", "Covers webhook, API, database, AI, batch processing, and scheduled automation architectures", and "optimizing a slow workflow... (node count, batchSize, all-items vs per-item)" list several specific, concrete coverage areas. Not 5 because it names domains/architectures rather than concrete action verbs (extract, fill, merge), leaving minor gaps in what the skill actually does; well above 3's "1-2 concrete actions".

4 / 5

Completeness

Explicitly answers both: what ("Proven workflow architectural patterns from real n8n workflows... Covers webhook, API, database, AI, batch processing, and scheduled automation architectures") and when ("Use when building new workflows... Always consult this skill when the user asks to create, build, or design an n8n workflow"), with concrete trigger phrases throughout.

5 / 5

Trigger Term Quality

Comprehensive natural-term coverage including synonyms: "building new workflows", "webhook processing", "HTTP API integration", "database operations", "AI agent workflows", "batch processing", "scheduled tasks", "automate a process", "connect services", "slow workflow", and "batchSize" — exactly the phrases a user would say when needing this skill.

5 / 5

Distinctiveness Conflict Risk

The n8n niche is clear ("n8n workflow", "batchSize", "webhook processing") and unlikely to trigger for unrelated skills. Not 5 because "Always consult this skill when the user asks to... automate a process, or connect services — even if they don't explicitly mention 'patterns'" drops the n8n qualifier, an aggressive catch-all that could grab generic automation/integration requests belonging to sibling skills.

4 / 5

Total

18

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (548 lines); consider splitting into references/ and linking

Warning

relative_links

Relative link issues: 10 missing

Warning

Total

14

/

16

Passed

Repository
czlonkowski/n8n-mcp
Reviewed

Table of Contents

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.