Conciseness

The body is dense with n8n-mcp-specific knowledge Claude cannot know (routing semantics, fail-close behavior, error envelopes) and explains nothing generic. Minor trimming opportunities remain: the shared-default hazard is restated in three sections (intro, 'How targeting behaves', 'Switching') and credential-safety rules in four, and the version-availability note ('backend 0.1.120+ / n8n-mcp 2.94.0+') is time-sensitive info placed inline rather than in a compat/deprecated section. Efficient with minor over-explanation → 4, not 5; not 3 since each repetition targets a distinct failure mode.

Actionability

Fully executable throughout: exact call shapes (`n8n_instances({mode:"list"})`, `n8n_manage_credentials({action:"create", …, instance:"client-a"})`), a numbered core workflow, a step-by-step copy-between-instances recipe with read/create/verify calls, concrete JSON error payloads, and a symptom→action recovery table. Copy-paste-ready guidance covering the common multi-instance cases matches the 5 anchor.

Workflow Clarity

Clear sequencing (Golden rules → numbered Core workflow → Recovery playbook) with explicit validation checkpoints at every high-stakes point: 'Check the name against `list` first' before credential writes, 'confirm current.name == "prod"' after a switch, 're-confirm current, then write', and 'verify on B' after a copy. Feedback loops exist for every error code, matching the 5 anchor. The destructive-operation cap does not apply because verification before credential writes is explicitly mandated.

Progressive Disclosure

A single self-contained file with well-labeled sections, a Quick Reference index, and named pointers to sibling skills, so navigation is easy. However, everything is inline — no bundle files or one-level-deep references exist, and at ~230 lines the error-envelope table and the INSTANCE_AMBIGUOUS deep-dive are plausible candidates for a separate reference file. Good structure with minor organization gaps → 4; not 5 because this is not an under-50-line skill where well-organized sections alone suffice.

Specificity

The description lists four concrete, distinct actions — 'naming the target instance on each call with the `instance` argument', 'setting the default with `switch`', 'verifying the target before high-stakes work', and 'recovering from misroutes and fail-closes' — which comprehensively covers the skill's lifecycle (per-call targeting, default management, verification, recovery). Matches the 5 anchor ('multiple specific concrete actions; comprehensive coverage') rather than 4, since no relevant action in the domain is left uncovered.

Completeness

Both halves are explicit: the 'what' ('Covers naming the target instance on each call with the `instance` argument, setting the default with `switch`, … and recovering from misroutes and fail-closes') and a concrete 'when' ('Use when an n8n-mcp account targets more than one n8n instance — i.e. the `n8n_instances` tool is available … Always consult this skill before operating on a specific instance'). Matches the 5 anchor with concrete trigger phrases; 4 would require a less explicit 'when', which is not the case.

Trigger Term Quality

Natural user-side triggers are comprehensively covered with synonyms: 'multiple n8n instances or environments (prod vs staging, several teams or clients)', 'several agents or chats work on one account in parallel', 'unexpected NOT_FOUND', 'reads data you don't recognize', and the literal error codes `INSTANCE_AMBIGUOUS`/`INSTANCE_NOT_FOUND` a user would paste back. Not 4, because no common natural term for this niche is missing.

Distinctiveness Conflict Risk

The skill has a clear, gated niche ('an n8n-mcp account targets more than one n8n instance') and unique error-code triggers (`INSTANCE_AMBIGUOUS` is exclusive to it), but broader triggers like 'a workflow / datatable / credential / execution call returns an unexpected NOT_FOUND' and 'credential create/update/delete' overlap with sibling n8n skills (the body itself notes n8n-mcp-tools-expert owns credential CRUD). Minor overlap risk with closely related skills matches the 4 anchor; not 5 because these shared triggers could fire the wrong n8n skill.