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

85%

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

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

Highly actionable, well-sequenced content with strong validation feedback loops and good file-based structure. The main weaknesses are redundancy that hurts token efficiency and three referenced bundle files that are missing from the bundle.

Suggestions

Remove the duplicated get_node detail-levels explanation (keep it in one place) and trim the Summary/Best Practices sections that restate earlier principles, plus drop the irrelevant '56 seconds average' stat, to improve conciseness.

Add the missing referenced bundle files (DEPENDENCIES.md, OPERATION_PATTERNS.md, NODE_FAMILY_GOTCHAS.md) to the bundle, or remove the references if the content is being inlined, so the progressive-disclosure navigation actually resolves.

Dimension	Reasoning	Score
Conciseness	Mostly efficient n8n-specific detail, but it carries redundant sections — get_node detail levels are explained both in 'Progressive Discovery' and again in a dedicated section, the Summary restates principles already covered, and the irrelevant '56 seconds average' stat adds padding.	3 / 5
Actionability	Fully executable, copy-paste-ready tool calls (get_node, n8n_explore_node_resources with all six required parameters, patchNodeField) with concrete examples spanning common node types (HTTP, Slack, Google Sheets, IF, SplitInBatches).	5 / 5
Workflow Clarity	An 8-step Standard Process with explicit validation checkpoints (steps 4 and 7), a validate→fix→retry feedback loop ('avg 2-3 iterations'), and a decision tree; validation is present for the destructive/batch database cases so the cap does not apply.	5 / 5
Progressive Disclosure	A clear overview with well-signaled, one-level-deep references and specific anchor links to DEPENDENCIES.md, OPERATION_PATTERNS.md, and NODE_FAMILY_GOTCHAS.md, but those three referenced bundle files are not present in the bundle, so navigation is partially broken.	4 / 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 trigger phrases. It is held back only by jargon-heavy 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 named mechanisms (displayOptions, patchNodeField) — giving comprehensive coverage rather than just several actions.	5 / 5
Completeness	Explicitly answers both 'what' (operation-aware node configuration guidance explaining required fields, displayOptions, patchNodeField) and 'when' with concrete trigger phrases ('Use when configuring nodes...', 'Always use this skill when setting up node parameters').	5 / 5
Trigger Term Quality	Good coverage of natural phrases a user would say ('configuring nodes', 'setting up node parameters', 'required fields'), but it leans on technical jargon (get_node detail levels, displayOptions, patchNodeField) and lacks synonyms, stopping short of comprehensive.	4 / 5
Distinctiveness Conflict Risk	Clear n8n node-configuration niche with distinct triggers, but it overlaps with closely related skills (n8n MCP Tools Expert for get_node usage, n8n Validation Expert for required-field determination), a minor conflict risk.	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 (539 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: 2df0f18

Reviewed: 7 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.