Bundled skills

Seven n8n skills ship with the plugin. You don't install them separately.

What's bundled

Skill	What it's for
n8n-mcp-tools-expert	Canonical tool selection guide — which MCP tool for which task, parameter formats, common gotchas
n8n-workflow-patterns	5 core architectural patterns: webhook processing, HTTP API integration, database ops, AI agents, scheduled tasks
n8n-node-configuration	Operation-aware config — knows which fields matter for which node operation
n8n-validation-expert	Interpreting validation errors, profile selection, handling false positives
n8n-expression-syntax	n8n's expression syntax, $json, $node, $item variable access
n8n-code-javascript	JavaScript in Code nodes — $input, $helpers, DateTime
n8n-code-python	Python in Code nodes — _input, _json, standard library usage

When they activate

The subagents invoke these skills automatically as part of the build loop. You rarely need to invoke them by hand — but you can, if you want to use a specific skill in a non-subagent conversation.

Updates

New skill versions ship with plugin releases. After updating:

/plugin update n8n-claude-kit

The latest skill content is pulled automatically.

See the Changelog for what's changed in each release.

Adding your own

Skills you install into ~/.claude/skills/ coexist with the bundled ones — no conflict.

If you've written a skill that would help everyone, open a PR against the repo — it'll land in skills/ in the next minor release.

Why bundle instead of dependency-install?

We considered requiring users to separately install each skill from some registry. Bundling wins because:

• Users don't need to discover or install skills one by one
• Plugin versioning guarantees all users on the same version have the same skill content
• The 90-second bootstrap target doesn't have room for multi-step skill installation

Trade-off: the plugin repo carries responsibility for tracking upstream skill changes. See VERSION.md for the sync process.