When you're wiring up n8n nodes and validation fails because a field is missing or your HTTP POST mysteriously doesn't have a body field, this is what you reach for. It teaches the progressive disclosure pattern that actual n8n users follow: start with standard detail (covers 95% of cases at 1-2K tokens), use search_properties when hunting for specific fields like auth or headers, and only pull full schemas when you're really stuck. The key insight is that required fields change based on operation. A Slack post needs channel and text, but update needs messageId instead. The skill maps out how displayOptions control which fields appear, walks through the get_node detail levels with a decision tree, and shows validation-driven workflows where you configure, validate, fix errors, repeat.
npx -y skills add czlonkowski/n8n-skills --skill n8n-node-configuration --agent claude-codeInstalls into .claude/skills of the current project.
Select a file.
sickn33/antigravity-awesome-skills
rohitg00/pro-workflow
supercent-io/skills-template