n8n-node-configuration

Operation-aware node configuration guidance. Use when configuring nodes, understanding property dependencies, determining required fields, choosing between get_node detail levels, or learning common configuration patterns by node type. Always use this skill when setting up node parameters — it explains which fields are required for each operation, how displayOptions control field visibility, and when to use patchNodeField for surgical edits vs full node updates.

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

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 well-structured, actionable skill body with clear workflows, explicit validation feedback loops, and exemplary progressive disclosure via signaled one-level-deep references. Its main weakness is conciseness — the standard-detail guidance and a few stats are repeated more than necessary.

Suggestions

Consolidate the 'get_node standard detail / 1-2K tokens / 95% of needs' guidance into a single authoritative location (e.g. the get_node Detail Levels section) and reference it elsewhere instead of restating it 4-5 times.

Remove the '56 seconds average between configuration edits' statistic and other filler from the Configuration Philosophy section — it does not guide Claude's actions.

Convert the remaining illustrative JSON structure snippets (e.g. Pattern 1-4 templates) into minimal executable examples or explicitly mark them as structural templates to close the small actionability gap.

Dimension	Reasoning	Score
Conciseness	The 'get_node standard detail / 1-2K tokens / 95% of needs' message is repeated across Configuration Philosophy, Core Concepts, get_node Detail Levels, Best Practices, and Summary, and the '56 seconds average between configuration edits' stat is filler — mostly efficient but could be tightened.	3 / 5
Actionability	Provides concrete executable calls (get_node({...}), patchNodeField with full operations array, validate_node) plus structural JSON config examples; mostly executable and copy-paste ready with minor gaps where snippets illustrate structure rather than full calls.	4 / 5
Workflow Clarity	The Standard Process is a clearly sequenced 8-step workflow with explicit validation checkpoints (steps 4 and 7) and a validate-driven feedback loop ('Configure → Validate → Fix → Repeat'), satisfying the validation requirement for batch/destructive-adjacent operations.	5 / 5
Progressive Disclosure	No bundle files are provided, so scoring is on references alone; the body is a clear overview with well-signaled one-level-deep references (DEPENDENCIES.md, OPERATION_PATTERNS.md, NODE_FAMILY_GOTCHAS.md) including specific anchor links, with deep-dive content appropriately split out and quick recaps kept inline.	5 / 5
	Total	17 / 20 Passed

Description

88%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, specific description that clearly states what the skill does and when to use it, with concrete actions and explicit trigger guidance. It is held back only slightly by some tool-specific jargon in the trigger terms and minor overlap with sibling n8n skills.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'configuring nodes, understanding property dependencies, determining required fields, choosing between get_node detail levels' plus 'explains which fields are required for each operation, how displayOptions control field visibility, and when to use patchNodeField' — giving comprehensive coverage of the skill's capabilities.	5 / 5
Completeness	Explicitly answers both 'what' (operation-aware node configuration guidance, field requirements, displayOptions, patchNodeField) and 'when' ('Use when configuring nodes...', 'Always use this skill when setting up node parameters') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Includes natural phrases a user would say ('configuring nodes', 'required fields', 'node parameters') alongside tool-specific jargon ('displayOptions', 'patchNodeField', 'get_node detail levels'); good keyword coverage but a few common natural variations are absent.	4 / 5
Distinctiveness Conflict Risk	Carves a clear n8n node-configuration niche with distinct triggers, but minor overlap risk remains with closely related sibling skills (n8n MCP Tools Expert, n8n Validation Expert) referenced in the body.	4 / 5
	Total	18 / 20 Passed

Validation

87%

Warnings & errors only

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

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (519 lines); consider splitting into references/ and linking	Warning
relative_links	Relative link issues: 9 missing	Warning

	Total	14 / 16 Passed

Repository: czlonkowski/n8n-skills
Path: skills/n8n-node-configuration/SKILL.md
Commit: 0296522

Reviewed: 4 days ago

Table of Contents

Discovery Implementation Validation

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.