Skip to content
SkillModel-led5,481 tokens in use

n8n Validation Expert

Teaches an agent to read n8n-mcp validation results, run the validate-and-fix loop, judge which warnings matter and test a workflow once it validates.

6,686 stars on the repository MIT Licenseczlonkowski/n8n-skills · skills/n8n-validation-expert
/plugin install czlonkowski/n8n-skills
View source

Install command as written in the repository's README

Skill label

measured from its files

What installing n8n Validation Expert costs

90tokens idle
5,481tokens in use
21,347tokens, up to

Idle is what sits in context while the skill is installed. In use is its instructions, loaded when it runs. Up to adds the files its instructions link. Counts are approximate, made offline with cl100k_base.

Model dependence Model-led

Script-ledMixedModel-led

Mostly instructions, so how well it works depends on the model that follows them.

This describes the skill's structure, how much of it is scripts. It does not say how well it works.

Touches

Nothing detected: no shell, network, file writes, git or credentials in its files.

Declared tags come from the skill's frontmatter; detected ones from its scripts, its code blocks and the commands it names in inline code. This is detected, not audited.

How it scores

Quality

How well the skill is written, counted from its own files: its frontmatter, its steps, examples, stated output and constraints, its size and whether every file it ships is one it names.How we score it →
Excellent
  • Frontmatter12/15
  • Structure25/25
  • Examples15/15
  • Output15/15
  • Size13/15
  • Resources11/15

Security

Starts at 100 and loses points for each thing in the skill's files that a reader should look at first.How we score it →
Excellent

No findings.

Repository health

Pre-computed score based on development activity, maintenance, community, maturity, and trend momentum.How we score it →
Good
  • Development activity88
  • Maintenance92
  • Community60
  • Maturity36
  • Momentum40

n8n Validation Expert covers what to do when validate_node or validate_workflow returns errors, warnings or suggestions in the n8n-mcp server. It explains the five core error types, the four validation profiles and how to read the result structure.

It also covers recovery strategies, the auto-fix tool, known false positives and blind spots, and how to run a workflow after it validates. Three companion guides hold an error catalog, a false-positive guide and a review checklist for existing workflows.

What You Get

  • A severity guide that separates blocking errors from warnings and suggestions
  • A comparison of the minimal, runtime, ai-friendly and strict profiles, with runtime as the everyday default
  • An error catalog with broken configs and their fixes, plus a list of known false positives and blind spots
  • Recovery strategies: start fresh, binary search, clean stale connections and auto-fix with confidence levels
  • A procedure for running a validated workflow with real triggers or pinned test data, and a checklist for reviewing an existing workflow

Common Use Cases

  • Fixing a missing_required or invalid_expression error returned by validate_node
  • Deciding whether a best-practice warning such as missing error handling is worth fixing
  • Previewing and applying n8n_autofix_workflow fixes at a chosen confidence level
  • Running a workflow with pinned data to confirm it behaves after it validates
  • Auditing a workflow that already passes validation for silent connection bugs

What Makes It Unique

Most n8n guidance covers how to build a node. This skill covers the feedback side: it records which warnings the validator still raises in error, which mistakes it cannot see at all (such as a JavaScript error inside an expression that resolves to null), and when a warning is acceptable. It states that a passing validation is necessary but not sufficient, and pairs it with a test run.

Under The Hood

The skill is instructions only and ships no scripts. It loads SKILL.md into context and points to three companion markdown guides that the agent reads when needed. Following it, the agent calls n8n-mcp tools: validating nodes and workflows, which is read-only, then auto-fix and partial-update operations that edit and can activate a workflow on the connected n8n instance. The test step runs real nodes, so external calls and writes happen, and the skill tells the agent to ask the user before turning on the workflow’s MCP exposure setting.

Join founders building with open source

Opinionated takes, migration guides, cost-saving tips, and insights from the open source ecosystem.

Subscribe on SubstackJoin 750+ subscribers