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.

64

Quality

76%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/n8n-validation-expert/SKILL.md
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.

A well-structured, actionable guide with an exemplary validation feedback loop, weakened by noticeable repetition across sections and by three dangling references to bundle files that are not actually present.

Suggestions

Add the missing referenced files (ERROR_CATALOG.md, FALSE_POSITIVES.md, REVIEW_CHECKLIST.md) to the bundle, or inline their essential content and remove the broken links.

Deduplicate the iteration/telemetry narrative — keep it once in The Validation Loop and reference it elsewhere instead of restating it in Validation Philosophy and Summary.

Consolidate the error-type listings in Error Severity Levels and Common Error Types into a single authoritative section to reduce overlap.

DimensionReasoningScore

Conciseness

The skill is mostly efficient and focused on n8n-specific behavior Claude would not know, but the iterative-loop theme and telemetry stats recur across Validation Philosophy, The Validation Loop, and Summary, and error-type listings overlap between Error Severity Levels and Common Error Types.

3 / 5

Actionability

Provides concrete executable calls (validate_node, validate_workflow, n8n_autofix_workflow, cleanStaleConnections) with worked broken-config→fix examples; minor gaps where fix detail is deferred to the referenced catalog.

4 / 5

Workflow Clarity

The validate→read→fix→re-validate loop is explicitly sequenced with iteration counts and feedback guidance, and recovery strategies are numbered with concrete commands — a textbook validation feedback loop.

5 / 5

Progressive Disclosure

References are one-level-deep and clearly signaled as markdown links, but all three referenced files (ERROR_CATALOG.md, FALSE_POSITIVES.md, REVIEW_CHECKLIST.md) are absent from the bundle, breaking navigation; some catalog content is also inlined rather than split out.

3 / 5

Total

15

/

20

Passed

Description

83%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, trigger-rich description that clearly states capabilities and multiple use-when conditions with concrete tool anchors. Its main weakness is omitting the n8n domain name from the description text, which slightly raises conflict risk with generic validation skills.

Suggestions

Open the description with the n8n domain (e.g. "Interpret n8n validation errors...") to eliminate overlap risk with generic validation skills.

Consider whether the three separate trigger clauses can be consolidated to reduce repetition without losing trigger specificity.

DimensionReasoningScore

Specificity

States concrete actions ("Interpret validation errors and guide fixing them") and enumerates several specific subtopics — false positives, operator structure issues, validation profiles, error types, the validation loop, and auto-fix capabilities — with only minor coverage gaps.

4 / 5

Completeness

Explicitly answers both what ("Interpret validation errors and guide fixing them") and when via repeated concrete trigger clauses ("Use when...", "Also use when...", "Consult this skill whenever...").

5 / 5

Trigger Term Quality

Good keyword coverage including natural phrases ("validation errors", "validation warnings", "false positives") and concrete tool names ("validate_node", "validate_workflow"), though a few common user phrasings are absent.

4 / 5

Distinctiveness Conflict Risk

Anchored by n8n MCP tool names (validate_node, validate_workflow) giving it a clear niche, but the description text never names n8n, leaving minor overlap risk with generic validation skills.

4 / 5

Total

17

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 7 missing

Warning

Total

15

/

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.