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).

70

Quality

86%

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.

A content-rich skill with excellent workflow validation guidance and genuinely useful batch/performance gotchas, undermined by verbosity and several low-value sections that restate generic n8n knowledge. The biggest concrete defect is that the five referenced detailed pattern files are not bundled, so progressive disclosure points to missing targets.

Suggestions

Remove or collapse the 'Pattern Statistics', 'Real Template Examples', and 'Summary' sections — the statistics are unsourced and the template/examples sections repeat information already covered in 'The 6 Core Patterns' and 'Pattern Selection Guide'.

Either ship the five referenced pattern files (webhook_processing.md, http_api_integration.md, database_operations.md, ai_agent_workflow.md, scheduled_tasks.md) in a references/ directory, or remove the links and inline the essential bits — currently the 'Detailed Pattern Files' section promises content that is not in the bundle.

Tighten 'Common Workflow Components' (Triggers/Data Sources/Transformation/Outputs) which describes n8n node categories Claude already knows; keep only non-obvious notes like the Error Handling specifics.

DimensionReasoningScore

Conciseness

The body is mostly efficient in its high-value sections (batch processing, performance, gotchas) but carries several padded or generic sections — 'Pattern Statistics', 'Real Template Examples' with vague 'Most common pattern' repeats, a restated 'Summary', and 'Common Workflow Components' that explains n8n basics Claude already knows — that could be trimmed.

3 / 5

Actionability

Strong concrete guidance throughout — executable code for dry-run verification, bidirectional threshold checks, webhook payload access, plus specific batchSize/batching rules and SplitInBatches wiring — but the pattern templates and 'Quick Start Examples' stay at a high-level sequence ('Webhook → Set → Slack') rather than copy-paste-ready workflows, leaving minor gaps.

4 / 5

Workflow Clarity

The 'validate, verify, test before activating' section is a textbook clear sequence with explicit validation gates, feedback loops ('fix every error and re-validate'), and a warning that validation passing is necessary not sufficient; the creation checklist reinforces it across planning/implementation/validation/deployment phases.

5 / 5

Progressive Disclosure

Good overall structure with clearly signaled one-level-deep references to five pattern files in a dedicated 'Detailed Pattern Files' section, but those referenced .md files are not present in the bundle (no references/ directory), so the navigation points to files that do not exist.

4 / 5

Total

16

/

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.

A strong, comprehensive description that clearly states what the skill does and gives rich, natural trigger phrases covering build/design/optimize scenarios. Its only weakness is verbosity — it runs long and could be tightened without losing trigger coverage.

Suggestions

Trim the trailing catalog clause ('Covers webhook, API, database, AI, batch processing, and scheduled automation architectures') since the preceding 'Use when' clause already enumerates these domains — it is redundant padding.

Consider condensing the three separate trigger sentences into two; the current density of 'Use when / Always consult / Also use when' risks the description reading as a list rather than a crisp statement.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions and domains — 'building new workflows, designing workflow structure, choosing workflow patterns, planning workflow architecture' plus 'webhook processing, HTTP API integration, database operations, AI agent workflows, batch processing, or scheduled tasks' — matching the comprehensive-coverage anchor.

5 / 5

Completeness

Explicitly answers both 'what' ('Proven workflow architectural patterns from real n8n workflows') and 'when' with three distinct trigger clauses ('Use when...', 'Always consult this skill when...', 'Also use when optimizing...'), matching the concrete-trigger-phrases anchor.

5 / 5

Trigger Term Quality

Comprehensive natural trigger phrases users would actually say — 'create, build, or design an n8n workflow', 'automate a process', 'connect services', 'optimize a slow workflow', 'speeding up large-item-count processing' — including synonyms and concrete parameter terms (node count, batchSize, all-items vs per-item).

5 / 5

Distinctiveness Conflict Risk

Scoped tightly to n8n workflow architecture with n8n-specific terminology (webhook, SplitInBatches, batchSize, all-items), giving it a clear niche and minimal overlap risk with other skills.

5 / 5

Total

20

/

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.

Validation14 / 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.