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.

67

Quality

81%

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

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 dense, highly actionable reference with excellent feedback-loop structure and concrete tool usage, undermined by redundancy between sections and references to bundle files that are missing from the skill directory. The core guidance is strong; the packaging needs consolidation.

Suggestions

Deduplicate the error-type documentation: 'Error Severity Levels' and 'Common Error Types' both fully list missing_required, invalid_value, type_mismatch, invalid_expression, and invalid_reference — keep one summary list in SKILL.md and defer worked examples to the error catalog.

Include ERROR_CATALOG.md, FALSE_POSITIVES.md, and REVIEW_CHECKLIST.md in the bundle (or remove the links) — as delivered, all three references point at nonexistent files.

Trim the repeated 23s/58s/'7,841 occurrences' telemetry from 'Validation Philosophy', 'The Validation Loop', and 'Summary' — stating it once, and moving the full profile and auto-fix detail into the referenced files, would cut significant length.

DimensionReasoningScore

Conciseness

The ~515-line body is information-dense but duplicates content: error types are fully listed in both 'Error Severity Levels' and 'Common Error Types', the 23s/58s telemetry stats appear in three sections, and motivational filler ('This is normal! Don't be discouraged') adds nothing. Anchor 3 fits — mostly efficient but could be tightened; not 4 because the duplication is more than minor.

3 / 5

Actionability

Fully executable guidance throughout: concrete tool calls with parameters (n8n_autofix_workflow with confidenceThreshold and fixTypes, cleanStaleConnections operations), the exact pinned-data shape keyed by node name, and the common flat-object mistake explicitly called out. Matches the copy-paste-ready anchor 5.

5 / 5

Workflow Clarity

The validate → read errors → fix → re-validate loop is explicitly sequenced with expected iteration counts, four named recovery strategies, preview-before-apply for auto-fix, and a consent checkpoint before routed runs. Clear feedback loops for error recovery — anchor 5.

5 / 5

Progressive Disclosure

References to ERROR_CATALOG.md, FALSE_POSITIVES.md, and REVIEW_CHECKLIST.md are one level deep and well-signaled, but none of these files exist in the bundle (verified by filesystem listing), and the body inlines substantial catalog content (full profile docs, auto-fix list, false-positive cases) that those files should hold. Dangling references plus inlined detail place this at anchor 3; broken links prevent a 4.

3 / 5

Total

16

/

20

Passed

Description

86%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 well-constructed description with explicit what/when structure, rich natural trigger terms, and strong tool-name anchoring. Its only weakness is a thin capability statement — two actions — with the description's weight carried by triggers rather than a fuller enumeration of what the skill does.

DimensionReasoningScore

Specificity

'Interpret validation errors and guide fixing them' names the domain and exactly two actions; the remainder of the description is trigger context rather than capabilities. Anchor 3 ('names domain and 1-2 concrete actions, but not comprehensive') fits; not 4 because actions like reading the result structure, running auto-fix, or selecting profiles appear only as topic keywords.

3 / 5

Completeness

Explicitly answers both questions: a clear 'what' ('Interpret validation errors and guide fixing them') and three concrete 'when' clauses ('Use when encountering...', 'Also use when asking about...', 'Consult this skill whenever a validate_node or validate_workflow call returns errors or warnings'). Anchor 5.

5 / 5

Trigger Term Quality

Comprehensive natural-term coverage with synonyms — 'validation errors', 'validation warnings', 'false positives', 'validation results', 'validation profiles', 'error types', 'auto-fix capabilities' — plus the exact tool names validate_node and validate_workflow. Matches the anchor-5 standard of natural phrasing an agent would actually produce.

5 / 5

Distinctiveness Conflict Risk

The validate_node/validate_workflow references anchor it firmly to the n8n MCP context, but the leading generic phrases 'validation errors' and 'false positives' could plausibly fire for schema or form validation in unrelated contexts. Mostly distinct with minor overlap risk — anchor 4; not 5 since the broadest triggers are not n8n-qualified.

4 / 5

Total

17

/

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 (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.