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

64

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/n8n-workflow-patterns/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

70%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 thorough, actionable skill body with excellent workflow gating and validation guidance. Its weak spots are cross-sectional redundancy that hurts conciseness and pattern detail files that are referenced but missing from the bundle.

Suggestions

Either include the five referenced pattern .md files in the bundle (references/) or remove the "Detailed Pattern Files" section and fold the essential per-pattern detail inline so no links dangle.

Collapse the repeated pattern enumerations ("The 6 Core Patterns", "Pattern Selection Guide", "Real Template Examples") into a single section to remove redundancy and recover token budget.

Drop or relocate the un-sourced "Pattern Statistics" percentages; without provenance they read as padding and risk being time-sensitive.

DimensionReasoningScore

Conciseness

Mostly useful n8n-specific material, but the six patterns are enumerated across three-plus sections ("The 6 Core Patterns", "Pattern Selection Guide", "Detailed Pattern Files", "Real Template Examples") with repeated descriptions, and the "Pattern Statistics" percentages add padding that could be tightened.

3 / 5

Actionability

Provides executable JS expressions ({{$json.body.email}}, the Math.abs bidirectional threshold check, the jmespath one-liner, the dry-run verification snippet) and concrete commands (validate_workflow, n8n_test_workflow, activateWorkflow), with only minor gaps in the step-list Quick Start examples.

4 / 5

Workflow Clarity

The four-gate lifecycle ("validate, verify, test before activating") supplies explicit validation checkpoints and feedback loops ("Fix every error and re-validate"), and the Planning/Implementation/Validation/Deployment checklist sequences the whole process; validation is present for batch operations so the destructive/batch cap does not apply.

5 / 5

Progressive Disclosure

The overview is well-structured with clearly signaled one-level-deep links to pattern detail files, but the referenced files (webhook_processing.md, http_api_integration.md, database_operations.md, ai_agent_workflow.md, scheduled_tasks.md) are not present in the bundle, so the disclosure is broken in practice.

3 / 5

Total

15

/

20

Passed

Description

87%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 with explicit what/when guidance and rich natural trigger terms. Its main weakness is an over-broad always-consult clause that raises conflict risk against the other n8n skills in the same ecosystem.

Suggestions

Soften "Always consult this skill when the user asks to create, build, or design an n8n workflow... even if they don't explicitly mention 'patterns'" to scope the skill to architecture/pattern decisions, leaving node config and tool lookup to its sibling skills.

Lead with the distinctive niche (architectural pattern selection) before enumerating the six pattern domains to sharpen distinguishability.

DimensionReasoningScore

Specificity

Lists several concrete actions ("building new workflows, designing workflow structure, choosing workflow patterns", "optimizing a slow workflow or speeding up large-item-count processing (node count, batchSize, all-items vs per-item)") and covers six pattern domains, but the actions are somewhat generic verbs tied to domains rather than distinct concrete operations, so it stops short of a 5.

4 / 5

Completeness

Clearly answers both what ("Proven workflow architectural patterns from real n8n workflows... Covers webhook, API, database, AI, batch processing, and scheduled automation architectures") and when via multiple explicit "Use when..." / "Always consult this skill when..." trigger clauses.

5 / 5

Trigger Term Quality

Comprehensive coverage of natural terms with synonyms users would actually say: "webhook processing, HTTP API integration, database operations, AI agent workflows, batch processing, scheduled tasks, automate a process, connect services, optimize a slow workflow".

5 / 5

Distinctiveness Conflict Risk

The n8n-patterns niche is clear, but the clause "Always consult this skill when the user asks to create, build, or design an n8n workflow... even if they don't explicitly mention 'patterns'" over-claims and creates real overlap risk with sibling n8n skills (MCP Tools Expert, Node Configuration).

3 / 5

Total

17

/

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 (550 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.