CtrlK
BlogDocsLog inGet started
Tessl Logo

n8n-workflow-patterns

Proven architectural patterns for building n8n workflows.

33

Quality

28%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills/skills/n8n-workflow-patterns/SKILL.md

The canonical home for this skill is n8n-workflow-patterns in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

35%Scale 1-5

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

This skill provides a broad architectural overview of n8n workflow patterns but suffers from significant verbosity and lack of actionable, executable content. It repeats information across multiple sections (core patterns, selection guide, quick start examples, summary), includes dubious statistics, and stays at a descriptive level rather than providing concrete workflow JSON or executable configurations. The checklist structure is a strength, but the skill would benefit greatly from being cut in half and adding actual executable examples.

Suggestions

Replace the plain-text 'Quick Start Examples' with actual n8n workflow JSON snippets that Claude can use directly with workflow creation tools.

Remove the 'Pattern Statistics' section entirely — the percentages appear fabricated and don't help Claude build workflows.

Consolidate the 'Pattern Selection Guide' into the '5 Core Patterns' section to eliminate redundancy, and move detailed pattern content into the referenced .md files.

Add concrete validation commands and error recovery steps to the checklist (e.g., specific validate_workflow calls with expected outputs and what to do on failure).

DimensionReasoningScore

Conciseness

Significantly verbose with substantial padding. The 'Pattern Statistics' section with made-up percentages, the 'Pattern Selection Guide' that largely repeats the core patterns section, the 'Summary' that restates everything, and extensive 'Best Practices' lists all add bulk without proportional value. Many sections explain things Claude already knows (what triggers are, what databases do). The skill could be cut by 50%+ without losing actionable content.

2 / 5

Actionability

The skill is almost entirely descriptive rather than executable. The 'Quick Start Examples' are pseudo-workflows described in plain text, not actual n8n workflow JSON or executable code. The few code snippets (expression syntax gotchas) are minimal. There are no copy-paste ready workflow configurations, no actual node configuration JSON, and no concrete API calls. The guidance stays at a high architectural level without giving Claude enough specifics to execute.

2 / 5

Workflow Clarity

The 'Workflow Creation Checklist' provides a reasonable multi-phase sequence (Planning → Implementation → Validation → Deployment) with validation steps mentioned. However, the validation steps are vague ('validate each node configuration', 'test with sample data') without concrete commands or explicit feedback loops for error recovery. The checklist is a good structure but lacks the specificity needed for a higher score.

3 / 5

Progressive Disclosure

The skill references detailed pattern files (webhook_processing.md, ai_agent_workflow.md, etc.) and other skills, which is good structure. However, no bundle files are provided, so these references are unverifiable. The main file itself is very long (~300+ lines) with content that should be in those referenced files but is instead partially duplicated inline (e.g., pattern descriptions appear in multiple sections). The references to other skills are well-signaled but the overall organization is bloated.

3 / 5

Total

10

/

20

Passed

Description

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

This description is extremely vague and reads more like a tagline than a functional skill description. It fails to specify any concrete actions the skill performs and completely lacks a 'when to use' clause. The only redeeming quality is the mention of 'n8n workflows' which provides minimal domain targeting.

Suggestions

Add concrete actions the skill performs, e.g., 'Designs error-handling flows, structures sub-workflows, configures retry logic, and organizes node chains in n8n automation workflows.'

Add an explicit 'Use when...' clause with trigger terms, e.g., 'Use when building n8n automations, structuring workflow logic, or asking about n8n best practices, nodes, or integrations.'

Replace the vague 'proven architectural patterns' with specific pattern names or capabilities to improve both specificity and distinctiveness.

DimensionReasoningScore

Specificity

The description is entirely vague — 'proven architectural patterns' names no concrete actions. It doesn't say what the skill actually does (e.g., create workflows, configure nodes, set up triggers). It reads as abstract marketing language.

1 / 5

Completeness

The 'what' is extremely vague ('proven architectural patterns' says nothing concrete), and there is no 'when' clause at all. Both dimensions are missing or inadequate.

1 / 5

Trigger Term Quality

It includes 'n8n' and 'workflows' which are relevant keywords a user might say, but misses natural variations like 'automation', 'nodes', 'integrations', 'n8n flow', or specific workflow types. 'Architectural patterns' is not a phrase users naturally use.

3 / 5

Distinctiveness Conflict Risk

'n8n workflows' provides some specificity that distinguishes it from generic workflow or automation skills, but 'architectural patterns' is broad enough to overlap with any n8n-related skill. Without concrete actions, it's hard to distinguish from other n8n skills.

3 / 5

Total

8

/

20

Passed

Validation

90%

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

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

10

/

11

Passed

Repository
administrakt0r/AI-Agents-Safe-Coding-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.