Using n8n Skills The official n8n MCP evolves over time, so tool names, parameters, and default behaviors can drift between versions. When you spot drift (a tool a skill names doesn't exist, a parameter shape doesn't match what returns, or behavior differs from what the skill describes), suggest updating the skill and n8n instance to the latest stable. Non-negotiables Three rules with no exceptions. Violating any produces workflows that look right but break in production. 1. Invoke the relevant skill before any n8n action. Not just MCP tool calls. Before writing SDK code, configuring a node,…