n8n-skills is a collection of Claude Code skills and hooks that guide AI assistants in creating, validating, and deploying n8n workflows through the n8n-mcp server. Developers use it to automate workflow construction, configure nodes and expressions, resolve validation errors, and operate self-hosted n8n. The catalogue entries are its skills, hooks, plugins, and instruction.
Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add czlonkowski/n8n-skills --skill using-n8n-mcp-skillsgit clone --depth 1 https://github.com/czlonkowski/n8n-skillsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/czlonkowski/n8n-skills/using-n8n-mcp-skills)<a href="https://agentmods.dev/skills/czlonkowski/n8n-skills/using-n8n-mcp-skills"><img src="https://agentmods.dev/badge/skills/czlonkowski/n8n-skills/using-n8n-mcp-skills/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/czlonkowski/n8n-skills/using-n8n-mcp-skills"><img src="https://agentmods.dev/badge/skills/czlonkowski/n8n-skills/using-n8n-mcp-skills.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket warn
- Snyk pass
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00164 | $0.04500 |
| Opus 5.5 | $0.00066 | $0.01800 |
| Sonnet 5.5 | $0.00033 | $0.00900 |
| Haiku 4.5 | $0.00016 | $0.00450 |
Grade A, and why
using-n8n-mcp-skills scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 3d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
This is a copy
100% identical to using-n8n-mcp-skills — 92 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 213 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Using the n8n-mcp Skills
This is a router, not a reference. It tells you which skill owns the rules for what you're about to do. The skill bodies hold the actual guidance — invoke them with the Skill tool. When in doubt, load more skills rather than fewer.
The community n8n-mcp server and n8n itself move faster than any model's training
cutoff. Tool names, parameters, node typeVersions, and default behaviors drift between
releases. When you spot drift — a tool a skill names doesn't exist, a parameter shape
doesn't match what get_node returns, behavior differs from what a skill describes —
trust the live tool, tell the user, and suggest updating the pack and the instance.
Non-negotiables
Three rules with no exceptions. Each one prevents a class of workflow that looks correct but breaks in production.
- Invoke the relevant skill before any n8n action — not just before MCP calls. Before writing an expression, configuring a node, designing a workflow, wiring a connection, or writing Code, invoke the matching skill. PreToolUse hooks remind you on the highest-impact tool calls, but they exist only in the Claude Code plugin install. Everywhere else — Claude.ai skill uploads, and any client that loads this pack as an Agent Plugin (Codex, Cursor, Copilot and the rest) — nothing nudges you and it's on you. Assume you are un-hooked unless you have seen a hook fire this session.
- Validate AND verify before activating. Run
validate_workflow(orn8n_validate_workflowby id) before you activate, and calln8n_get_workflowafter every create or update to inspect theconnectionsobject. Validation alone misses silently dropped wires, Merge index off-by-one, and error outputs that were never wired. Validation passing means the JSON is well-formed — not that the workflow is correct. A green test run isn't proof either: JS errors inside{{ }}resolve silently tonull(a Filter with a broken condition drops every item and still shows success), so inspect the output values. Seen8n-expression-syntax. - Secrets never go in text fields. Tokens, API keys, and passwords always go through
the n8n credential system. If no native node exists, use the HTTP Request node with
the official credential type. A Set node holding a token referenced via
{{ $json.token }}is a leak with extra steps. Seen8n-mcp-tools-expert.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 3d ago Changed · +24 lines 96ac692b385e
- 12d ago Changed fddfcdda70c6
- 1mo ago Changed · +2 lines 0651b3eebf65
- 1mo ago First seen · 187 lines · 164 tokens per session scan A de4ad06ed79d
using-n8n-mcp-skills is a skill published in the GitHub repository czlonkowski/n8n-skills (6,533 stars, last pushed 3d ago), licensed MIT. It adds 164 tokens to every session and 4,500 once invoked, about $0.0007 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to using-n8n-mcp-skills, differing in 92 lines, and is treated as a copy.
Other skills, from other repositories
n8n-code-javascript
Write JavaScript code in n8n Code nodes. Use when writing JavaScript in n8n, using $input/$json/$node syntax, making HTTP requests with $helpers, working with dates using DateTime, troubleshooting Code node errors, or choosing between Code node modes.
data-tables
Manage n8n DataTables (CRUD on tables, columns, rows) via the n8n public REST API. Use when the user wants to create/seed/list/delete data-table resources outside of a workflow — n8nac CLI does not support this. Curl is explicitly allowed for /api/v1/data-tables (carve-out in PreToolUse hook).
n8n-patterns
Common n8n workflow patterns. Use when designing workflows to apply proven patterns for error handling, data processing, integrations, and flow control.
create-credentials
Create n8n credentials using type-safe factory methods. Supports Google, Postgres, MySQL, Slack, Telegram, OpenAI, GitHub, and more.
n8n-code-tool
Write JavaScript or Python for the n8n Custom Code Tool (@n8n/n8n-nodes-langchain.toolCode) — the AI-agent-callable tool, NOT the workflow Code node. Use when building a Code Tool attached to an AI Agent, writing code that an LLM will invoke, parsing the query input, returning a string result, defining an input schema…
n8n-expression-syntax
Validate n8n expression syntax and fix common errors. Use when writing n8n expressions, using {{}} syntax, accessing $json/$node variables, troubleshooting expression errors, mapping data between nodes, or referencing webhook data in workflows. Use this skill whenever configuring node fields that reference data from…