n8n Node Configuration Guide

The documentation shows meaningful security awareness through validation-first guidance, avoidance of placeholder credentials, parameterized SQL, silent-data-loss warnings, and explicit response-code handling. Points are deducted because deployment and workflow updates remain routine next steps without user confirmation, sensitive-data boundaries, rollback, change isolation, or complete disclosure of external effects; publisher identity and source attribution are also not independently verified.

The skill provides operation discovery, dependency inspection, iterative validation, and some diagnosable failure handling, including strict patchNodeField behavior. Points are deducted for visible inconsistencies: SKILL.md says timezone is workflow-level while OPERATION_PATTERNS.md places timezone inside rules; database parameter fields vary between queryReplacement and additionalFields.queryParameters; and several claims depend on unspecified tools, versions, or runtime behavior. No reproducible execution evidence is supplied, so the static cap keeps this at 10 or below.

README provides trigger phrases, common scenarios, tool context, and covered node categories, giving the skill a reasonably clear target for n8n configuration work. Points are deducted because non-fit boundaries, version-compatibility limits, and tool-availability requirements are incomplete; Chinese-language support is not declared, and mainland-China reachability of the n8n-mcp/Claude Code dependency is not established.

The material has a useful information hierarchy, progressive disclosure, related references, examples, gotcha sections, version history, MIT licensing, and author information. Points are deducted because maintenance ownership, issue/feedback channels, update procedures, and change tracking are weak; the README claims four evaluations without providing them here, while usage statistics and the end-to-end verification claim lack attached evidence.

The central workflow is clear and practically useful: inspect resource and operation, understand displayOptions, validate, and iterate. Examples cover common HTTP, Slack, database, and conditional-node cases. Points are deducted because some examples may be version-sensitive or contradictory, configurations still require instance-specific schema correction, and no statically verifiable representative output demonstrates deploy-ready completeness.

The files contain concrete configurations, field names, failure symptoms, and proposed fixes, which provide some auditability. Points are deducted because success rates, timing metrics, coverage claims, and end-to-end verification are author statements without committed tests, CI evidence, or independent corroboration; static review cannot reproduce them, so the score remains below the static ceiling of 5.