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

71

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Advisory

Suggest reviewing before use

SKILL.md
Quality
Evals
Security

Quality

Content

77%

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

The body delivers genuinely expert, actionable n8n guidance — the validation lifecycle, SplitInBatches semantics, performance model, and integration gotchas are excellent. It is let down by length/filler (generic component lists, percentage statistics) and by progressive-disclosure gaps where referenced pattern files are missing and content that belongs in them is inlined.

Suggestions

Create the 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, so the 'Detailed Pattern Files' navigation actually resolves.

Trim the generic 'Common Workflow Components' and 'Pattern Statistics' sections — these are either common knowledge or unsourced figures — to tighten conciseness.

Move the inline 'Quick Start Examples', 'Real Template Examples', and per-pattern detail into the pattern reference files so SKILL.md stays a lean overview.

DimensionReasoningScore

Conciseness

Lean, high-value sections (the batchSize cost model, validation lifecycle, integration gotchas) earn their tokens, but the body is ~540 lines padded with generic 'Common Workflow Components' building blocks and a dubious 'Pattern Statistics' (e.g. 'Webhook - 35%') that reads as filler. Matches score-2 'mostly efficient but includes some unnecessary explanation', not score-3 'every token earns its place'.

2 / 3

Actionability

Provides executable JavaScript blocks (the dry-run verification snippet, the Math.abs threshold check), specific node/operation names ('NEVER use append', 'convertToGoogleDocument: true', 'values.update PUT'), and concrete MCP tool calls (validate_workflow, n8n_test_workflow, activateWorkflow). This is a pattern/instruction skill whose guidance is specific and actionable, meeting the score-3 bar.

3 / 3

Workflow Clarity

The 'validate, verify, test, activate' lifecycle is a clear four-gate sequence with explicit validation checkpoints, a fix-and-re-validate feedback loop, and a full creation checklist — exactly the score-3 anchor of 'clear sequence with explicit validation steps; feedback loops for error recovery; checklists'.

3 / 3

Progressive Disclosure

Pattern files are signaled with proper markdown links and a dedicated 'Detailed Pattern Files' section, but the referenced bundle files (webhook_processing.md, http_api_integration.md, etc.) do not exist in references/scripts/assets, and the 540-line body keeps statistics, component lists, and examples inline that would belong in those files. Matches score-2 'content that should be separate is inline', falling short of score-3 'appropriately split'.

2 / 3

Total

10

/

12

Passed

Description

100%

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 comprehensive and explicit, naming concrete capabilities, natural trigger terms, and clear when-to-use guidance scoped to the n8n-workflow niche. It is on the verbose/repetitive side (the 'Always consult ...' and 'Also use when ...' clauses restate the trigger), but every dimension maps cleanly to the top anchor.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'building new workflows, designing workflow structure, choosing workflow patterns, planning workflow architecture' plus enumerated domains (webhook, API, database, AI, batch, scheduled) and 'optimizing a slow workflow'. Matches the score-3 anchor of multiple specific concrete actions, not the score-2 'some actions' level.

3 / 3

Completeness

Explicitly answers both what ('Proven workflow architectural patterns from real n8n workflows') and when ('Use when ...', 'Always consult this skill when ...', 'Also use when ...'). Has explicit trigger guidance, satisfying the score-3 anchor rather than the score-2 'when only implied'.

3 / 3

Trigger Term Quality

Covers natural user phrasings — 'build ... an n8n workflow', 'automate a process', 'connect services', 'optimizing a slow workflow', 'speeding up large-item-count processing' — terms a user would actually say. Not the score-2 'some keywords missing variations' level.

3 / 3

Distinctiveness Conflict Risk

Scoped to a clear niche — n8n workflow architecture patterns — with n8n-specific triggers (webhook processing, SplitInBatches batchSize) unlikely to fire for unrelated skills. Distinct enough for the score-3 anchor.

3 / 3

Total

12

/

12

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 (547 lines); consider splitting into references/ and linking

Warning

relative_links

Relative link issues: 10 missing

Warning

Total

14

/

16

Passed

Repository
czlonkowski/n8n-skills
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.