When you're wiring up n8n nodes and hit that wall of "which fields are actually required for this operation?", this is your answer. It teaches Claude the operation-aware configuration model where a Slack post needs channel and text, but an update needs messageId instead. The key insight is starting with standard detail from get_node (covers 95% of cases at 1-2K tokens) rather than immediately dumping the full schema. It walks through property dependencies, those displayOptions rules that make fields appear and disappear based on your choices, and gives you the progressive discovery workflow: configure minimal fields, validate, search for specific properties if needed, validate again. Solid for anyone building n8n workflows who's tired of trial and error node configuration.
npx skills add https://github.com/sickn33/antigravity-awesome-skills --skill n8n-node-configuration