n8n-skills

Pick a task and get started

Install the skills, configure the local MCP below, confirm node lookup works, then send the first task. Installing a plugin, connecting an instance and publishing a workflow are separate steps.

1. Install the community plugin in Claude Code

   Copy install command

   Run each line inside Claude Code, not a system shell. The second opens plugin selection: choose n8n-mcp-skills, then reload as the host requires. This is the author’s marketplace route and installs its available version rather than pinning this page’s commit. Use host-specific instructions elsewhere; hooks and MCP setup are not automatically equivalent.

   /plugin marketplace add czlonkowski/n8n-skills
   /plugin install

   Read the author’s setup and capability guide

   Connect local documentation and validation first

   Copy install command

   Create or merge .mcp.json at the project root, preserving existing mcpServers entries. This configuration pins the verified npm release 2.99.2. On first launch, npx downloads and runs it, so you need network access and a compatible Node.js version. Follow Claude Code’s project-MCP confirmation and reload prompts, then perform the connection check below. This setup includes no instance credentials and disables n8n-mcp telemetry. The repository’s .mcp.json.example is only an example; installing the skills does not turn it into your connection.

   {
     "mcpServers": {
       "n8n-mcp": {
         "command": "npx",
         "args": [
           "-y",
           "[email protected]"
         ],
         "env": {
           "MCP_MODE": "stdio",
           "LOG_LEVEL": "error",
           "DISABLE_CONSOLE_OUTPUT": "true",
           "N8N_MCP_TELEMETRY_DISABLED": "true"
         }
       }
     }
   }

   Companion MCP configuration for Claude Code

2. Give your AI this first task

   Copy prompt

   These editorial task examples are based on the reviewed sources. Replace brackets, attach real inputs and send them to a configured assistant. File names are deliverables chosen for this page, not built-in plugin commands.

   Use n8n-skills, specifically using-n8n-mcp-skills, n8n-node-configuration and n8n-expression-syntax, to create order-summary.json for n8n [target version]. Write local files only; do not create or run a remote workflow. Use a Manual Trigger and this built-in fixture: {"customer":{"first_name":"Ada","last_name":"Lovelace"},"items":[{"sku":"A1","price_cents":1250,"qty":2},{"sku":"B2","price_cents":300,"qty":4}]}. Return one summary item containing full_name, line_count (number of product rows), unit_count (sum of quantities), and subtotal_cents (sum of unit price in cents × quantity). Prefer native nodes and short expressions. Edit Fields may hold the fixture or an explicit return object; do not add Code for simple totals. Discover nodes and fields through search_nodes/get_node, then validate the complete JSON. Check that the target n8n version supports the chosen typeVersions. Do not invent credential IDs. Also save cases.json and README.md. The normal case should return Ada Lovelace, 2, 6, 3700. Empty items should return 0, 0, 0. A missing price_cents must take a clear invalid-input path rather than silently become zero. Explain import, manual execution, fixture replacement and output inspection. Record actual validation responses. If n8n has not been run, label these values as expected and do not invent an execution ID.

3. Check what you receive

   • order-summary.json, cases.json and import instructions, with node names that explain each step.
   • After importing, run manually: the normal case should produce one item and a subtotal of 3700 cents. Then try the empty-array and missing-field cases.
   • Check item counts, types, values and the invalid-input branch. Structural validation covers only one of these checks.
   Read the author’s notes for this task