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

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

77%

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

A highly actionable, well-sequenced body with strong validation feedback loops, but it over-repeats the standard-detail guidance and references bundle files that do not exist. Tightening the redundancy and creating the referenced files would lift both conciseness and progressive disclosure.

Suggestions

Create the referenced DEPENDENCIES.md, OPERATION_PATTERNS.md, and NODE_FAMILY_GOTCHAS.md so the inline links resolve instead of dangling.

Consolidate the repeated get_node standard-detail guidance (appearances in Core Concepts, Detail Levels, Decision Tree, Best Practices, and Summary) into a single authoritative section to cut token redundancy.

Move the four full node-pattern code blocks and the complete detail-level breakdowns into OPERATION_PATTERNS.md / DEPENDENCIES.md, keeping SKILL.md as a lean overview that links out.

Dimension	Reasoning	Score
Conciseness	Largely assumes Claude's competence and stays action-dense, but repeats the standard-detail/get_node guidance ('95% of use cases', '1-2K tokens', 'standard is default') across the Core Concepts, Detail Levels, Decision Tree, Best Practices, and Summary sections — material that could be tightened.	2 / 3
Actionability	Provides copy-paste-ready, executable examples throughout — get_node calls, node-config JSON, validate_node usage, and a complete patchNodeField operation block — with specific field names and syntax.	3 / 3
Workflow Clarity	The 'Standard Process' is a clear 8-step sequence with explicit validation checkpoints (validate_node, validate→fix→repeat, 'validate before deploying') and an explicit feedback loop, reinforced by the anti-patterns section.	3 / 3
Progressive Disclosure	References DEPENDENCIES.md, OPERATION_PATTERNS.md, and NODE_FAMILY_GOTCHAS.md with well-signaled one-level-deep links, but those bundle files are absent on disk (dangling references), and the ~515-line body inlines content (all four node patterns with full code, full detail-level breakdowns) that arguably belongs in those files.	2 / 3
	Total	10 / 12 Passed

Description

100%

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 capabilities and provides explicit trigger guidance in third-person voice. Both the 'what' and 'when' are unambiguous.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'configuring nodes, understanding property dependencies, determining required fields, choosing between get_node detail levels' and 'explains which fields are required for each operation, how displayOptions control field visibility, and when to use patchNodeField'.	3 / 3
Completeness	Explicitly answers both what (operation-aware node configuration guidance, field/displayOptions/patchNodeField behavior) and when via explicit 'Use when...' and 'Always use this skill when...' trigger clauses.	3 / 3
Trigger Term Quality	Uses natural terms an n8n user would say — 'configuring nodes', 'setting up node parameters', 'required fields', 'node type' — with good coverage rather than opaque jargon.	3 / 3
Distinctiveness Conflict Risk	Occupies a clear n8n node-configuration niche with distinctive tool names (get_node, patchNodeField, displayOptions) making it unlikely to trigger for unrelated skills.	3 / 3
	Total	12 / 12 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
Commit: b90ba12

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.