Expression Syntax
n8n-expression-syntax
$json, $node, and $now patterns — plus the webhook-data-lives-under-body gotcha that breaks most first drafts.
MIT licensed · 14 skills + router · Agent Plugin ready
The expert skill pack for production-ready n8n workflows
Install the skills alone, or load the complete plugin with hosted n8n-mcp already connected over OAuth.
Build a webhook → Slack flow
prompt
using-n8n-mcp-skills
SessionStart hook
n8n-workflow-patterns
1 of 14
Validated workflow
no error loop
$ npx skills add czlonkowski/n8n-skillsNeed it built for you?
AiAdvisors audits, builds, and operates production n8n automation — led by the author of n8n-mcp and n8n-skills.
Runs in

Claude Code
CLI & IDE

Claude Desktop
Desktop app

Claude.ai
Web
The skills use the open Agent Skills format. The same repository also ships Agent Plugin manifests that connect supported clients to hosted n8n-mcp.
0
expert skills
0K+
installs
0+
nodes covered
0+
templates
The repository is more than a folder of Markdown. Its portable plugin package pairs the complete skill pack with the hosted n8n-mcp service while keeping authentication out of the manifest.
The repository ships Agent Plugin 1.0 manifests alongside the skills, ready for clients that support the open package layout.
The plugin points to n8n-mcp over Streamable HTTP. Authentication stays in the OAuth flow — no API key is copied into the package.
Guidance now covers routed workflow operations, agent and resource discovery, folders, data tables, credentials, and production operations.
Each one owns a class of failure. They compose: a single workflow build can pull in patterns, node configuration, expressions, and validation without you naming any of them.
n8n-expression-syntax
$json, $node, and $now patterns — plus the webhook-data-lives-under-body gotcha that breaks most first drafts.
n8n-mcp-tools-expert
The right n8n-mcp route for workflows, folders, credentials, data tables, agents, resources, and every validation stage.
n8n-workflow-patterns
Five architectures drawn from real templates: webhook, HTTP API, database, AI agent, and scheduled runs.
n8n-validation-expert
Read errors and warnings correctly, handle routed test runs, separate real failures from false positives, and exit the fix loop.
n8n-node-configuration
Operation-aware requirements for nodes and official MCP resources, so every field is configured with the right context.
n8n-code-javascript
Production-tested Code node patterns with $input, $json, and this.helpers — and the top five failure modes.
n8n-code-python
Python in Code nodes, with a straight answer on the standard library and what simply isn't available.
n8n-code-tool
The AI-callable Custom Code Tool: string returns, the query binding, input schemas — a different node entirely.
n8n-error-handling
Error outputs, retryOnFail, 4xx/5xx response shapes, and Error Trigger runs. Failures get loud, not silent.
n8n-binary-and-data
Files, images, and PDFs: $binary versus $json, keeping binary alive across transforms, agent-tool boundaries.
n8n-subworkflows
Typed inputs, all-versus-each execution, discoverable naming, and exposing a workflow as an agent tool.
n8n-agents
Agent, chain, or classifier; model, memory, tools, parsers, $fromAI, RAG, and official MCP agent operations.
n8n-multi-instance
Target the right instance across prod, staging, and clients — and never write a credential to the wrong one.
n8n-self-hosting
Production n8n with Caddy and Docker Compose: single or queue mode, managed OAuth, backups, updates, and hardening.
A skill only helps if it loads at the moment of the decision. The plugin ships a router and hooks that surface the right one then — not only when your question happens to match a description.
A SessionStart hook loads it into every session. It points at the skill that owns the decision, covers the full n8n-mcp surface, and re-fires after resume, clear, and compact.
Before a high-impact n8n-mcp call, a reminder names the relevant skill. Looking up Set, Code, Merge, Loop Over Items, DateTime, Data Table, or AI Agent fires a node-specific one. Credentials and instance switches get their own.
After validate_workflow, the node types get inspected and you're routed to whatever still carries risk — because a workflow passing validation is necessary, not sufficient.
Hooks run in the Claude Code and Codex plugin installs. Elsewhere the skills still activate by description — the pack degrades gracefully, just without the nudges. Every hook fails open and never blocks a tool call.
Choose the complete Agent Plugin when your client supports it, or install the skills on their own. Self-hosted setups can keep using their own n8n-mcp configuration.
Skills + hosted n8n-mcp
Loads all 14 specialist skills and the router, then declares the hosted n8n-mcp endpoint over Streamable HTTP. The client completes OAuth without storing an API key in the plugin package.
Get the Agent Plugin packageSkills-only install for any agent
$ npx skills add czlonkowski/n8n-skillsInstalls all 14 skills plus the router into whichever agent you use — Claude Code, Codex, Cursor, Copilot, and the rest. Configure n8n-mcp separately when the client is not loading the Agent Plugin.
View the listingIncludes the hooks layer
$ /plugin install czlonkowski/n8n-skillsAll 14 skills, the router, and the hooks enforcement layer come up after the restart.
Upload skills one by one
Download the per-skill zips from the latest release, then go to Settings → Capabilities → Skills → Upload Skill.
The complete bundle zip is Claude Code only — it uses a nested plugin structure Claude.ai can't read.
For local installs
$ git clone https://github.com/czlonkowski/n8n-skills.git$ cp -r n8n-skills/skills/* ~/.claude/skills/Available immediately. Copying folders skips the hooks layer — use the plugin install to get it.
Installing the pack and building a workflow with it, end to end.