n8n MCP Workflow Router
Routes n8n-mcp tasks to the right skills and reduces production workflow failures.
The document explicitly requires credential-system storage for secrets, validation before activation, user confirmation before side-effectful testing, and mentions workflow version history for rollback. However, data-flow disclosure, permission isolation, rollback procedure, and sensitive-data boundaries are incomplete, and publisher verification is absent, so points are deducted.
Routing rules, tool-name formats, validation order, and drift handling are reasonably consistent, with guidance to trust live tools and report drift. Static review found no reproducible tests for this skill path itself; key behavior depends on external MCP, plugin hooks, and other skills, so the score is conservatively limited by the static ceiling.
The intended audience, n8n workflow scenarios, trigger language, skill index, and some non-fit boundaries are clear. Inputs and outputs, false-trigger boundaries, Chinese-language support, and mainland-China reachability are not addressed; core use also depends on n8n-mcp and a compatible Claude/plugin environment, so points are deducted.
The router, red-flag table, index, and ordered protocol provide clear progressive disclosure. Shared repository context supplies installation prerequisites, MIT licensing, and version 1.0.0 compatibility. Missing are a changelog, explicit maintenance responsibility, stable update path, troubleshooting entry point, and version-evolution policy; publisher identity is unverified, so points are deducted.
As an entry router, it gives task-to-specialist mappings, compact tool knowledge, and production safeguards, establishing clear navigation value. It does not contain the specialist guidance itself; usable results depend on other skills, tools, and correct triggering, and no representative output is statically verifiable, so the score remains below the static ceiling.
SKILL.md, README, license, and revision metadata provide auditable primary material, and the main rules are traceable. No tools or tests were executed; claims about production-tested patterns, template counts, and coverage lack independent reproduction and corroboration in the supplied material, so points are deducted.
- This is a router rather than a complete operating guide; its capability drops substantially without the companion skills, a reachable n8n-mcp service, or plugin hooks.
- It recommends validation before activation but does not provide complete templates for side-effect confirmation, least-privilege review, data-flow disclosure, or recovery. Manually confirm the target instance, permissions, and rollback plan before handling production credentials or workflows.
- Chinese-language interaction and mainland-China network reachability are undocumented; the external MCP service and plugin environment may limit availability.
- README claims about testing and production-tested patterns are not reproducibly evidenced by the supplied static materials.
What does this skill do, and when should you use it?
This is the entry-point router in the n8n-skills repository for building, editing, validating, testing, and debugging n8n workflows through the n8n-mcp MCP server. It maps task types to specialist skills and provides working knowledge of the n8n-mcp tool surface. Its core rules require validation before activation, connection inspection after changes, and credential-based handling of secrets. It fits teams that already operate n8n-mcp and want more reliable AI-assisted workflow work.
Routes n8n tasks to the relevant specialist skill before work begins; explains the roles of tools including tools_documentation, search_nodes, get_node, validate_node, workflow creation and update tools, validation, inspection, testing, execution records, credentials, and audits; requires validate_workflow before activation and n8n_get_workflow after creation or updates to inspect connections; directs users to store tokens, API keys, and passwords through n8n credentials rather than text fields; and maps common intentions to skills for expressions, code, error handling, binary data, sub-workflows, AI agents, or multiple n8n instances.
- An automation developer building a new workflow through Claude Code and n8n-mcp can use it to identify the architecture and specialist skills needed.
- A user configuring n8n nodes, expressions, credentials, or connections can use it to avoid relying on outdated parameter memory.
- A user whose workflow passes validation but behaves incorrectly can use its checks to inspect connections, tool parameters, and the relevant specialist guidance.
- A team managing multiple n8n instances or sensitive credentials can use its prompts for instance targeting and credential discipline.
What are this skill's strengths and limitations?
- Covers n8n-mcp discovery, node configuration, validation, workflow lifecycle, and security discipline.
- Requires validation before activation and connection inspection after updates, addressing common silent failures.
- Provides an intent-based index for the specialist skills and works as the entry point for the pack.
- Released under the MIT license with installation, usage, development, and testing documentation.
- It is a router rather than a complete node or workflow reference; detailed implementation guidance is in sibling skills.
- It requires the n8n-mcp MCP server and an n8n instance, so it is not standalone.
- The supplied material does not show test results or cross-platform verification for this individual skill.
- n8n and its tools change frequently, so documented behavior can drift from the live tool surface.
How do you install this skill?
Install and configure the n8n-mcp MCP server and provide an n8n instance. For Claude Code, the README recommends: /plugin install czlonkowski/n8n-skills. Alternatively, clone the repository, run cp -r n8n-skills/skills/* ~/.claude/skills/, and reload Claude Code. In Claude.ai, download the skills/using-n8n-mcp-skills/ folder and upload it through Settings → Capabilities → Skills.
How do you use this skill?
After installing skills/using-n8n-mcp-skills/SKILL.md as a skill, submit an n8n request such as: Build and validate a webhook workflow through n8n-mcp. The router is intended to be consulted before any n8n, workflow, node, or automation task. Full implementation guidance resides in the specialist skills and must be invoked separately.