CtrlK
BlogDocsLog inGet started
Tessl Logo

n8n-mcp-tools-expert

Expert guide for using n8n-mcp MCP tools effectively. Use when searching for nodes, validating configurations, accessing templates, managing workflows, organizing workflows into folders, managing credentials, auditing instance security, or using any n8n-mcp tool. Provides tool selection guidance, parameter formats, and common patterns. IMPORTANT — Always consult this skill before calling any n8n-mcp tool — it prevents common mistakes like wrong nodeType formats, incorrect parameter structures, and inefficient tool usage. If the user mentions n8n, workflows, nodes, or automation and you have n8n MCP tools available, use this skill first.

68

Quality

83%

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

The canonical home for this skill is n8n-mcp-tools-expert in czlonkowski/n8n-skills

SKILL.md
Quality
Evals
Security

Quality

Content

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

Highly actionable, tool-accurate reference material with exemplary validation loops and safety gates. It is held back by redundant restatement across sections and a guide-file split that either is missing from the bundle or is undercut by deep inline detail in SKILL.md itself.

Suggestions

Merge the 'Quick Reference' speed column and the 'Performance Characteristics' table into one table, and cut the 'Summary' section's restatement of Common Mistakes and patterns to pure pointers.

State the nodeType short-vs-full prefix rule once (in 'Critical: nodeType Formats') and reference it from Common Mistakes, the Best Practices lists, and the Summary instead of repeating it in each.

Ship the four referenced guide files with the skill, and move the deep per-tool detail (n8n_test_workflow methods, n8n_workflow_versions sources, n8n_manage_agents actions/error codes) into them, leaving one-paragraph summaries plus links in SKILL.md.

DimensionReasoningScore

Conciseness

The body is dense with server-specific facts Claude cannot know (good), but duplication is pervasive: the Quick Reference 'Speed' column restates the Performance Characteristics table, the Summary restates Common Mistakes and patterns, nodeType-format guidance appears in four places (Tool Selection, Critical: nodeType Formats, Common Mistakes #1, Summary #2), and timing stats like '18s average' and '56s avg between edits' repeat more than four times.

3 / 5

Actionability

Fully executable throughout: concrete calls like `search_nodes({query: "slack"})` and `n8n_manage_credentials({action: "list"})`, wrong/correct JSON for credentials and nodeType prefixes, exact parameter shapes ('column: {name, type}', '{__rl: true, mode: "id", value: …}'), and named error codes per tool.

5 / 5

Workflow Clarity

Multi-step processes are explicitly sequenced with validation checkpoints and feedback loops ('Fix errors, validate again', 'Validate after every significant change', validate → fix → validate cycles), and destructive or batch operations get explicit confirm/dryRun gates ('confirm with the user before dropping a populated column', 'use dryRun: true before bulk changes', 'ask the user first' for exposeToMcp).

5 / 5

Progressive Disclosure

References to SEARCH_GUIDE.md, VALIDATION_GUIDE.md, WORKFLOW_GUIDE.md, and OPERATIONS_GUIDE.md are clearly signaled one level deep, but none of those files exist in the bundle, and long inline sections (Running Workflows, Version History, Agents) carry detail that the guide split was meant to offload — structure exists, but content placement and broken navigation hold it at the middle anchor.

3 / 5

Total

16

/

20

Passed

Description

88%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: comprehensive concrete capabilities, explicit use-when triggers, and a clear n8n-mcp niche. Its only weaknesses are a trigger clause broad enough to collide with sibling n8n skills and a few missing natural phrasings like 'run/execute a workflow'.

Suggestions

Narrow the final trigger clause to the MCP-tool context (e.g. 'if the user mentions n8n and n8n-mcp/MCP tools are available') to avoid competing with sibling n8n skills.

Add one or two common action phrasings users actually say — 'run'/'execute'/'test a workflow', 'deploy a template' — to the trigger list.

DimensionReasoningScore

Specificity

The description lists multiple concrete capabilities — 'searching for nodes, validating configurations, accessing templates, managing workflows, organizing workflows into folders, managing credentials, auditing instance security' — plus 'tool selection guidance, parameter formats, and common patterns'. Coverage is comprehensive and stays in third person ('Provides...').

5 / 5

Completeness

Both questions are answered explicitly: what ('Expert guide for using n8n-mcp MCP tools effectively... Provides tool selection guidance, parameter formats, and common patterns') and when ('Use when searching for nodes, validating configurations... or using any n8n-mcp tool', reinforced by 'If the user mentions n8n, workflows, nodes, or automation... use this skill first').

5 / 5

Trigger Term Quality

Good natural-keyword coverage ('n8n, workflows, nodes, or automation' plus action phrases like 'validating configurations' and 'auditing instance security'), but a few natural user phrasings such as 'run/execute a workflow', 'webhook', or 'trigger' are missing — falls between the 'good coverage' and 'comprehensive with synonyms' anchors, closer to the former.

4 / 5

Distinctiveness Conflict Risk

The n8n-mcp MCP-tool niche is clear and mostly distinct, but the broad trigger 'If the user mentions n8n, workflows, nodes, or automation' risks overlap with the closely related sibling n8n skills the body itself lists (n8n Expression Syntax, n8n Workflow Patterns, n8n Node Configuration).

4 / 5

Total

18

/

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 25 missing, 1 suspicious

Warning

Total

15

/

16

Passed

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.