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.

68

Quality

85%

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

The canonical home for this skill is n8n-validation-expert in czlonkowski/n8n-skills

SKILL.md
Quality
Evals
Security

Quality

Content

70%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.

The content is a thorough, actionable guide with excellent workflow sequencing and feedback loops, but it leans long with some over-explanation and relies on three referenced files that are not bundled alongside the skill.

Suggestions

Add the missing referenced bundle files (ERROR_CATALOG.md, FALSE_POSITIVES.md, REVIEW_CHECKLIST.md) to references/ so the inlined error-type lists can be trimmed and the one-level-deep structure is real.

Tighten the Validation Philosophy and Loop sections — drop the telemetry seconds and emphatic restatements ('This is normal!') that don't add actionable guidance.

Move the per-advisory false-positive bullets and the full auto-fix capability list into FALSE_POSITIVES.md / ERROR_CATALOG.md and keep only a concise pointer in the body.

DimensionReasoningScore

Conciseness

Mostly efficient and well-structured, but several sections re-explain context Claude can infer and the document is long (~515 lines) with repeated emphasis ('This is normal!', 'Validate early, validate often') and telemetry color that adds tokens without new guidance.

3 / 5

Actionability

Provides concrete, executable JS/JSON examples for validate_node, validate_workflow, cleanStaleConnections, and n8n_autofix_workflow with real arguments; minor gaps where guidance points to referenced catalog files rather than inlining the fix.

4 / 5

Workflow Clarity

The validation loop is explicitly sequenced with a feedback checkpoint (validate -> read errors -> fix -> re-validate), recovery strategies are enumerated, and the run/test section adds validation before declaring done — clear feedback loops for a validation-oriented, batch-capable process.

5 / 5

Progressive Disclosure

The body repeatedly signals separate files (ERROR_CATALOG.md, FALSE_POSITIVES.md, REVIEW_CHECKLIST.md) but those bundle files are not present in references/, scripts/, or assets/, so the referenced one-level-deep structure cannot be verified and several lists that belong in those files are inlined here.

3 / 5

Total

15

/

20

Passed

Description

100%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.

The description is a strong, concise trigger statement that answers both what and when with concrete, natural-language terms and tool-specific anchors. It uses correct third-person voice and avoids fluff.

DimensionReasoningScore

Specificity

Names the domain (n8n validation) and lists multiple concrete actions: 'Interpret validation errors and guide fixing them', handling 'validation warnings, false positives, operator structure issues', plus understanding profiles, error types, the loop, and auto-fix.

5 / 5

Completeness

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

5 / 5

Trigger Term Quality

Covers natural user phrasing and technical synonyms: 'validation errors', 'validation warnings', 'false positives', 'operator structure issues', 'validation profiles', 'error types', 'validation loop', 'auto-fix', plus the concrete tool triggers 'validate_node or validate_workflow'.

5 / 5

Distinctiveness Conflict Risk

A clear niche keyed to specific n8n validation tools and outcomes; the trigger is tied to validate_node/validate_workflow returns, making conflict with unrelated skills minimal.

5 / 5

Total

20

/

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.

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

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

Warning

relative_links

Relative link issues: 7 missing

Warning

Total

14

/

16

Passed

Repository
czlonkowski/n8n-mcp
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.