n8n-validation-expert

Interpret and fix n8n workflow validation errors through iterative validation loops.

2|Updated Jan 12, 2026
One-click install
npx skills add https://github.com/mdc159/cbass --skill n8n-validation-expert-mdc159
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: n8n-validation-expert
Source: https://github.com/mdc159/cbass/tree/main/.claude/skills/n8n-validation-expert-v1.0.0
Command: npx skills add https://github.com/mdc159/cbass --skill n8n-validation-expert-mdc159

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Validation errors in n8n workflows are common and often require 2-3 validate-fix iterations to resolve, leaving users confused about which errors must be fixed, which warnings are acceptable false positives, and which issues are auto-fixed by sanitization. ## Core Features & Use Cases - Error Interpretation: Explains the five core error types (missing_required, invalid_value, type_mismatch, invalid_expression, invalid_reference) with concrete broken/fixed configuration examples. - Validation Profiles: Guides selection between minimal, runtime, ai-friendly, and strict profiles, noting that ai-friendly reduces false positives by 60%. - False Positive Triage: Provides a decision framework for when warnings like missing error handling, retry logic, or unbounded queries are acceptable versus must-fix. - Use Case: When validate_node_operation returns a missing_required error on a Slack node, consult the error catalog to identify the required channel field, fix the config, and re-validate until valid. ## Quick Start Ask the assistant to explain and fix the validation error returned by validate_node_operation for your n8n node configuration.

Frequently Asked Questions about n8n-validation-expert

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I fix n8n validation errors in my workflow?

Run validate_node_operation, read each error message carefully, fix errors one at a time, and re-validate. Expect 2-3 iterations on average. Use get_node_essentials to check which fields are required before configuring a node.

What n8n validation profile should I use?

Use the runtime profile for most pre-deployment validation since it balances coverage and noise. Use ai-friendly for AI-generated configs to reduce false positives by 60%, minimal for quick checks, and strict only for production-critical workflows.

Are all n8n validation warnings required to be fixed?

No. Roughly 40% of warnings are acceptable depending on context. Missing error handling is fine for dev or test workflows, and retry logic is unnecessary for idempotent operations or APIs with built-in retries. Always fix security warnings and document accepted ones.

Why does my n8n IF node show operator structure errors?

Binary operators like equals must not have singleValue, while unary operators like isEmpty require singleValue: true. These are auto-fixed by n8n's sanitization on every workflow save, so you do not need to correct them manually.

How do I fix invalid_reference errors in n8n workflows?

Verify the referenced node exists and check for typos in the node name within expressions. For stale connections to deleted nodes, run n8n_update_partial_workflow with the cleanStaleConnections operation to remove broken references.