redcoatasher/n8n-skills-redux

Overview

This skill provides operation-aware guidance for configuring n8n nodes, focusing on required fields, property dependencies, and progressive discovery patterns. It helps you choose when to use get_node_essentials, get_property_dependencies, or get_node_info and shows common configuration patterns by node type. Use it to harden workflows by validating minimal, correct configurations before deployment.

How this skill works

The skill inspects node type and selected operation to determine which fields are required and which are conditional. It recommends starting with get_node_essentials to obtain required fields and common options, then falling back to get_property_dependencies to reveal displayOptions-driven dependencies, and finally get_node_info for a full schema when needed. It supports an iterative configure → validate → fix workflow and explains common dependency patterns (boolean toggles, operation switches, type selections).

When to use it

• When creating or editing a node and you need the minimal required fields
• When validation errors reference missing or hidden fields
• When switching operations for a resource and requirements change
• When you need to decide between get_node_essentials and get_node_info
• When you want to avoid over-configuring and harden workflows

Best practices

• Start with get_node_essentials; it covers ~90% of cases and is fastest
• Validate iteratively: configure → validate → fix → repeat
• Use get_property_dependencies when a field is missing or visibility is unclear
• Respect operation context—resource + operation determine required fields
• Keep configurations minimal; add optional fields only when needed

Example use cases

• Configuring an HTTP Request: start with method and url, then add sendBody/body only if POST/PUT/PATCH and validation requires it
• Setting up a Slack node: use get_node_essentials to see fields for post vs update (channel vs messageId)
• Resolving a validation error that says "body required when sendBody=true" by calling get_property_dependencies for the HTTP node
• Hardening a database node by confirming operation-specific required fields (insert → table+values, update → where clause)
• Designing IF node conditions and letting auto-sanitization handle singleValue for unary operators