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

66%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/n8n-node-configuration/SKILL.md

Quality

Discovery

85%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This is a strong description that clearly articulates what the skill does and when to use it, with explicit trigger guidance including both 'Use when...' and 'Always use this skill when...' clauses. The specificity of capabilities is excellent, listing concrete actions and concepts. The main weakness is that trigger terms lean toward technical jargon rather than natural user language, which could reduce discoverability for less technical users.

Suggestions

Add more natural-language trigger terms that users might actually say, such as 'set up a node', 'which fields do I need', 'node not working', or 'configure workflow step'.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions: configuring nodes, understanding property dependencies, determining required fields, choosing between get_node detail levels, using patchNodeField for surgical edits vs full node updates, and how displayOptions control field visibility.	3 / 3
Completeness	Clearly answers both 'what' (operation-aware node configuration guidance, explaining required fields per operation, displayOptions behavior, patchNodeField usage) and 'when' (explicit 'Use when configuring nodes, understanding property dependencies, determining required fields...' and 'Always use this skill when setting up node parameters').	3 / 3
Trigger Term Quality	Includes some relevant terms like 'configuring nodes', 'required fields', 'patchNodeField', 'displayOptions', and 'node parameters', but these are fairly technical/domain-specific. Missing more natural user phrases like 'set up a node', 'which fields do I need', or 'node setup help'. The terms lean toward internal jargon rather than what users would naturally say.	2 / 3
Distinctiveness Conflict Risk	Highly distinctive with a clear niche around operation-aware node configuration, displayOptions, patchNodeField, and get_node detail levels. These are very specific domain concepts unlikely to overlap with other skills.	3 / 3
	Total	11 / 12 Passed

Implementation

47%

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

This skill provides comprehensive coverage of n8n node configuration with good workflow structure and validation checkpoints, but suffers severely from verbosity and repetition. The same core concepts are restated across multiple sections, and detailed examples that belong in referenced files (DEPENDENCIES.md, OPERATION_PATTERNS.md) are inlined, bloating the document to 400+ lines. Trimming redundancy and moving detailed examples to bundle files would dramatically improve token efficiency.

Suggestions

Eliminate repetition: the operation-aware concept (Slack post vs update), get_node detail levels, and '95% of use cases' are each explained 3-4 times — consolidate to a single authoritative section each.

Move the 'Property Dependencies Deep Dive', 'Common Node Patterns', and 'Operation-Specific Configuration' sections into DEPENDENCIES.md and OPERATION_PATTERNS.md respectively, keeping only brief summaries with cross-references in SKILL.md.

Remove explanations of concepts Claude already knows (what HTTP GET/POST are, what JSON bodies are, what binary vs unary operators mean) to cut token usage significantly.

Clarify the exact invocation format for MCP tools — are get_node/validate_node JavaScript function calls, tool_use blocks, or something else? Show the precise syntax once.

Dimension	Reasoning	Score
Conciseness	Extremely verbose at ~400+ lines with massive repetition. The same concepts (operation-aware configuration, displayOptions, get_node detail levels) are explained multiple times in different sections. Examples like Slack post vs update are shown at least 3 times. Statistics like '95% of use cases' and '1-2K tokens' are repeated 4+ times. Much content explains things Claude would already know (HTTP methods, what GET vs POST means). The anti-patterns section largely restates what was already covered.	1 / 3
Actionability	Provides concrete JavaScript examples with specific tool calls (get_node, validate_node, patchNodeField) and realistic node configurations. However, the code is illustrative rather than truly executable — functions like get_node() and validate_node() are shown as if they're JavaScript functions but are actually MCP tool calls, creating ambiguity about exact invocation syntax. The examples are useful but the actual tool call format is never precisely specified.	2 / 3
Workflow Clarity	The configuration workflow is clearly sequenced with explicit validation checkpoints and feedback loops (configure → validate → fix → repeat). The decision tree for get_node detail levels is well-structured. The HTTP Request walkthrough demonstrates iterative validation with error recovery at each step. The anti-patterns section reinforces validation-before-deploy as a critical checkpoint.	3 / 3
Progressive Disclosure	References DEPENDENCIES.md and OPERATION_PATTERNS.md at the bottom, but no bundle files are provided to verify these exist. The main issue is that enormous amounts of content that should be in those referenced files (the entire 'Property Dependencies Deep Dive' section, all 'Common Node Patterns', all 'Operation-Specific Configuration' examples) are inlined in the SKILL.md, making it a near-monolithic document despite having reference files available.	2 / 3
	Total	8 / 12 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (836 lines); consider splitting into references/ and linking	Warning

	Total	10 / 11 Passed

Repository: czlonkowski/n8n-skills
Commit: 27e9d0a

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