CtrlK
BlogDocsLog inGet started
Tessl Logo

using-n8n-mcp-skills

Use when building, editing, validating, testing, or debugging an n8n workflow through the n8n-mcp MCP server — designing a flow, configuring a node, writing an expression or Code node, wiring credentials, or fixing one that misbehaves. The entry-point skill for the n8n-mcp-skills pack: it routes you to the right specialist skill, gives working knowledge of every n8n-mcp tool from turn one, and states the rules that keep workflows from breaking in production. Always consult it first on any n8n, workflow, node, or automation task — even a quick one-off, and even when the user names no skill — because n8n's surface drifts between versions and the specialist skills prevent silent failures.

73

Quality

90%

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

SKILL.md
Quality
Evals
Security

Quality

Content

81%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 well-structured router skill: opinionated, concrete, and sequenced with real validation checkpoints. Its only soft spot is the inline working-knowledge tool list, which is slightly dense and carries version-sensitive detail that a future refactor could move into a referenced reference file.

Suggestions

Consider moving the 'n8n-mcp tools — working knowledge from turn one' section into a bundled reference file (e.g. references/tools-cheatsheet.md) and linking to it from the router body, which would improve both conciseness and progressive_disclosure.

The version-gated notes (e.g. 'n8n 2.28+', 'n8n >= 2.30', 'n8n >= 2.32') are time-sensitive; grouping them under an explicitly versioned table or a 'version compatibility' reference would reduce drift risk and trim the body.

A one-line legend mapping each tool to its owning specialist skill (alongside the existing Skill Index) would let the model pick the right follow-up skill without scanning the prose.

DimensionReasoningScore

Conciseness

Dense and opinionated, assuming Claude's competence throughout (e.g. 'Set node feeding 0-1 consumers is almost always wrong') with no padding explaining what n8n or MCP are; the inline tool list carries some time-sensitive version detail that keeps it just short of fully lean.

4 / 5

Actionability

Provides concrete tool names and parameter shapes (e.g. 'get_node' takes SHORT-form 'nodes-base.httpRequest', the LONG-vs-SHORT node-type trap) plus a Red Flags thought-to-skill table, though the actual how-to is delegated to specialist skills rather than given as copy-paste code.

4 / 5

Workflow Clarity

'The protocol, in order' gives a clear 5-step sequence with explicit validation checkpoints ('validate_workflow before activating' and 'n8n_get_workflow after' to check connections) and a drift-surfacing feedback loop, reinforced by the Non-negotiables and Red Flags sections.

5 / 5

Progressive Disclosure

As a router it cleanly references 14 specialist skills by name at one level of depth, with clear signals (Red Flags table, Skill Index, 'See <skill>' pointers); no bundle files exist, so there is nothing to split out, and the inline tool list is moderately dense.

4 / 5

Total

17

/

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 model description: it states concrete capabilities, gives an explicit 'Use when' trigger with natural synonyms, anchors its niche as the pack's router, and even handles the edge case where the user names no skill. No fluff, no over-claiming.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — building, editing, validating, testing, debugging, designing a flow, configuring a node, writing an expression or Code node, wiring credentials, fixing misbehaviors — giving comprehensive coverage of the domain.

5 / 5

Completeness

Explicitly answers both 'what' (entry-point router for the pack, working knowledge of every tool, production-safety rules) and 'when' (an explicit 'Use when...' clause with concrete trigger phrases).

5 / 5

Trigger Term Quality

Comprehensive natural triggers including 'building, editing, validating, testing, or debugging an n8n workflow' and 'any n8n, workflow, node, or automation task — even a quick one-off, and even when the user names no skill', covering the synonyms users would actually say.

5 / 5

Distinctiveness Conflict Risk

Scoped tightly to n8n-mcp workflows and explicitly positioned as the entry-point router for a named pack, giving it a clear niche with minimal conflict risk.

5 / 5

Total

20

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

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.