CtrlK
BlogDocsLog inGet started
Tessl Logo

n8n-validation-expert

Interpret validation errors and guide fixing them. Use when encountering validation errors, validation warnings, false positives, operator structure issues, or need help understanding validation results. Also use when asking about validation profiles, error types, the validation loop process, or auto-fix capabilities. Consult this skill whenever a validate_node or validate_workflow call returns errors or warnings — it knows which warnings are false positives and which errors need real fixes.

69

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

77%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A genuinely expert, highly actionable validation guide with excellent feedback-loop structure and executable examples. Its weaknesses are length/redundancy (duplicated error-type listings, scattered version numbers, telemetry padding) and broken progressive disclosure: the three referenced detail files are missing while their intended content is inlined.

Suggestions

Create the referenced ERROR_CATALOG.md, FALSE_POSITIVES.md, and REVIEW_CHECKLIST.md files and move the inlined error-catalog examples, the four-issue false-positives detail, and the review audit into them so SKILL.md stays an overview.

Dedupe the error-type listings — 'Error Severity Levels' and 'Common Error Types' cover the same five types — into a single canonical list, and remove the telemetry padding ('7,841 occurrences', '23 seconds thinking/fixing') that does not guide action.

Consolidate time-sensitive version notes (n8n-mcp 2.63.0, 2.85.0, n8n 2.34+) into a single 'Version requirements' or 'Deprecated behavior' section so they do not clutter the main flow.

DimensionReasoningScore

Conciseness

The body is dense with valuable n8n-mcp-specific knowledge, but it is noticeably long (~520 lines), duplicates the error-type catalog between 'Error Severity Levels' and 'Common Error Types', and scatters time-sensitive version numbers (2.63.0, 2.85.0, n8n 2.34+) and telemetry padding ('7,841 occurrences', '23 seconds thinking') through the main body rather than isolating them.

3 / 5

Actionability

Provides copy-paste-ready, executable examples throughout — validate_node/validate_workflow calls with real config, n8n_autofix_workflow with applyFixes/confidenceThreshold/fixTypes parameters, cleanStaleConnections operations, and the prepare/pinned/direct test-workflow flow with concrete pinData shapes.

5 / 5

Workflow Clarity

The core validation loop is explicitly sequenced with feedback checkpoints (validate -> read errors -> fix -> validate again -> repeat), recovery strategies are stepwise, and the run-after-validating section has a clear numbered prepare/pinned/direct flow with a consent checkpoint before enabling MCP.

5 / 5

Progressive Disclosure

References to ERROR_CATALOG.md, FALSE_POSITIVES.md, and REVIEW_CHECKLIST.md are clearly signaled and one level deep, but those files do not exist in the bundle and substantial detail that belongs in them (the full false-positives section with four issue links, the error catalog with JSON examples, the auto-fix type list) is inlined in SKILL.md.

3 / 5

Total

16

/

20

Passed

Description

95%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, well-constructed description that clearly states the skill's purpose and gives multiple concrete, natural trigger conditions including the specific MCP tool calls that should activate it. The only minor weakness is that the concrete action vocabulary is essentially two verbs (interpret, guide) while the rest of the text enumerates contexts rather than actions.

DimensionReasoningScore

Specificity

Opens with two concrete actions ('Interpret validation errors and guide fixing them') and enumerates several specific sub-capabilities (false positives, operator structure issues, validation profiles, error types, the validation loop, auto-fix), with only minor gaps in action verbs.

4 / 5

Completeness

Explicitly answers both what ('Interpret validation errors and guide fixing them') and when ('Use when encountering validation errors... Also use when asking about validation profiles... Consult this skill whenever a validate_node or validate_workflow call returns errors or warnings') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Comprehensive coverage of natural terms users would say ('validation errors', 'validation warnings', 'false positives', 'validation results', 'auto-fix') plus the actual tool names ('validate_node', 'validate_workflow') that fire the skill.

5 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (n8n validation interpretation/fixing) with distinct triggers tied to specific tools (validate_node, validate_workflow) and concepts (validation profiles, false positives), giving minimal conflict risk with other skills.

5 / 5

Total

19

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (524 lines); consider splitting into references/ and linking

Warning

relative_links

Relative link issues: 7 missing

Warning

Total

14

/

16

Passed

Repository
czlonkowski/n8n-skills
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.