CtrlK
BlogDocsLog inGet started
Tessl Logo

n8n-workflow-patterns

Proven architectural patterns for building n8n workflows.

49

Quality

54%

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-claude/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

63%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 content is a well-structured, actionable catalog of n8n patterns with a solid validation-aware checklist and concrete gotchas. Its main weaknesses are moderate redundancy across sections and references to detail files that are not actually bundled.

Suggestions

Remove or consolidate redundant sections (Pattern Statistics, the stub Real Template Examples, restated Summary) to tighten token use.

Either create the referenced detail files (webhook_processing.md, database_operations.md, etc.) under references/ or remove the "Detailed Pattern Files" section to avoid broken references.

Add an explicit validate→fix→retry loop to the Validation Phase of the checklist to push workflow clarity toward 5.

DimensionReasoningScore

Conciseness

The body is mostly efficient structured guidance without teaching basic concepts, but sections like "Pattern Statistics", the stub "Real Template Examples", and restating the 5 patterns three times add padding, matching anchor 3; not 2 because the core guidance is genuinely useful rather than dominated by fluff.

3 / 5

Actionability

Concrete node sequences ("Webhook → Validate → Transform → Respond"), named tool operations (search_nodes, validate_workflow, activateWorkflow), and specific gotcha fixes ({{$json.body.email}}) give mostly executable guidance, matching anchor 4; not 5 because examples are node lists rather than copy-paste-ready workflow definitions.

4 / 5

Workflow Clarity

The Workflow Creation Checklist sequences Planning → Implementation → Validation → Deployment with explicit validation checkpoints (validate_node, validate_workflow, test with sample data), so the destructive/batch cap does not apply; not 5 because there is no explicit validate→fix→retry feedback loop.

4 / 5

Progressive Disclosure

Internal sectioning is clear, but the "Detailed Pattern Files" section references webhook_processing.md, http_api_integration, database_operations.md, ai_agent_workflow.md, and scheduled_tasks.md that do not exist, and all detail is inlined in one ~400-line file, matching anchor 3; not 4 because the signaled references are broken.

3 / 5

Total

14

/

20

Passed

Description

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

The description names a clear domain and a couple of natural terms but is too terse to be complete: it lacks any "Use when" trigger guidance and lists no concrete actions. It is adequate but would benefit from explicit trigger phrasing and a sharper distinction from sibling n8n skills.

Suggestions

Add a "Use when ..." clause naming concrete triggers (e.g., building, debugging, or structuring n8n workflows; mention webhooks, scheduled jobs, AI agents).

List 1-2 concrete actions (e.g., "selects an architectural pattern and sequences nodes for a workflow") to raise specificity above anchor 2.

Differentiate from sibling skills by stating the pattern-selection angle (e.g., "Choose this before reaching for n8n MCP Tools Expert or Node Configuration").

DimensionReasoningScore

Specificity

Quotes "architectural patterns for building n8n workflows" name the domain but the only action ("building") is generic, matching anchor 2; not 3 because no concrete actions like designing or validating are listed.

2 / 5

Completeness

A clear "what" is present ("architectural patterns for building n8n workflows") but there is no "when"/"Use when" clause, which the guidelines cap at 3; not 4 because the when is entirely absent rather than merely weak.

3 / 5

Trigger Term Quality

"n8n", "workflows", and "architectural patterns" are natural terms but common variations and an explicit trigger phrase are missing, matching anchor 3; not 4 because coverage is thin with no synonyms or context cues.

3 / 5

Distinctiveness Conflict Risk

The n8n niche is specific but the body references several sibling n8n skills, so a user asking to build a workflow could trigger a related skill, matching anchor 3; not 4 because the short description does not carve a clearly separate trigger.

3 / 5

Total

11

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

15

/

16

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.