Skills for Real Engineers. Straight from my .agents directory.
n8n-multi-instance
Agent skill fromczlonkowski/n8n-skills
Use when an n8n-mcp account targets more than one n8n instance — i.e. the `n8n_instances` tool is available, the user mentions multiple n8n instances or environments (prod vs staging, several teams or clients), several agents or chats work on one account in parallel, a workflow / datatable / credential / execution call returns an unexpected NOT_FOUND or reads data you don't recognize, or a call is refused with `INSTANCE_AMBIGUOUS` or `INSTANCE_NOT_FOUND`. Covers naming the target instance on each call with the `instance` argument, setting the default with `switch`, verifying the target before high-stakes work — credential writes above all — and recovering from misroutes and fail-closes. Always consult this skill before operating on a specific instance, before any credential create/update/delete on a multi-instance account, or when a call hits the wrong/empty data or an instance error.
How to install n8n-multi-instance
npx skills add czlonkowski/n8n-skills# or add only this skill to Claude Code: copy the folder
skills/n8n-multi-instance/
# into
~/.claude/skills/n8n-multi-instance/ (all projects)
.claude/skills/n8n-multi-instance/ (one project)
1# Working with multiple n8n instances over MCP23When the `n8n_instances` tool is available, the user has **multi-instance mode** on: one MCP4connection can reach several n8n instances (e.g. `prod`, `staging`, or one per client/team).56There are two ways to say which instance a call should hit:78- **Name it on the call** — every n8n tool (`n8n_get_workflow`, `n8n_list_workflows`,9 `n8n_update_partial_workflow`, `n8n_manage_datatable`, `n8n_manage_credentials`,10 `n8n_executions`, `n8n_test_workflow`, `n8n_health_check`, …) takes an optional11 `instance: "<name>"`. It routes **that one call** and changes nothing else. **Prefer this.**12- **Set the default with `switch`** — `n8n_instances({mode:"switch", name})` sets the instance used13 by calls that *don't* name one.1415The default is shared more widely than it looks. On claude.ai (and other hosted connectors) one16connection serves **every chat and agent** using it, so a `switch` in one chat moves all the17others too — and their next unnamed call silently lands on your instance. A wrong target is18usually silent: a read returns the wrong data and a write lands in the wrong place. So name the19instance.2021If the `n8n_instances` tool is **not** present, the account is single-instance: ignore this skill22and use the n8n tools directly.2324> **Availability.** The `instance` argument needs hosted n8n-mcp backend 0.1.120+ / n8n-mcp25> 2.94.0+. It is there when the n8n tools' input schemas list an `instance` property (and the26…
Excerpt shown under the repository's MIT license.
More skills in n8n-skills
Similar skill repositories
An agentic skills framework & software development methodology that works.
A single CLAUDE.md file to improve Claude Code behavior, derived from Andrej Karpathy's observations on LLM coding pitfalls.
Public repository for Agent Skills
Makes your AI agent think like the laziest senior dev in the room. The best code is the code you never wrote.
Persistent Context Across Sessions for Every Agent – Captures everything your agent does during sessions, compresses it with AI, and injects relevant context back into future sessions. Works with Claude Code, OpenClaw, Codex, Gemini, Hermes, Copilot, OpenCode + More
