Conciseness

The dense n8n-specific sections (SplitInBatches semantics, lifecycle gates, Google Sheets/Drive gotchas, performance rules) earn their tokens and teach things Claude would not know. But the ~550-line body carries real padding: the pattern list is repeated three times ("The 6 Core Patterns", "Pattern Selection Guide", "Detailed Pattern Files"), the "Pattern Statistics" percentages and "Real Template Examples" sections add near-zero actionable content ("AI Agents: Growing in usage — Most common: Chatbots"), and the Do/Don't list includes trivia like "iterate! avg 56s between edits". This matches the 3 anchor (mostly efficient, some unnecessary material) rather than 2, since nothing explains concepts Claude already knows and the core guidance is tight.

Actionability

Guidance is concrete and executable: exact node-output semantics ("main[0] = done", "main[1] = each batch"), copy-paste code for dry-run verification and Math.abs threshold checks, exact expressions (`{{ $json.price.toNumber() }}`), concrete URLs (`https://drive.google.com/uc?id={fileId}&export=download`), ASCII wiring diagrams, and named tool calls (validate_workflow, n8n_test_workflow). It stops short of the 5 anchor because the Quick Start "examples" are node-name lists without the key configuration (auth, operation, expressions), and the full workflow-JSON pattern is deferred to pattern files that are not present, leaving a gap between promise and executable detail.

Workflow Clarity

The "validate, verify, test before activating" section is an explicit four-gate sequence with the rule "validation passing is necessary, not sufficient", per-gate tool invocations, feedback loops ("Fix every error and re-validate"), and a safety checkpoint ("Real side effects fire during a test... confirm with the user before running"). It is reinforced by the four-phase creation checklist with validation items in each phase. This squarely matches the 5 anchor (clear sequence, explicit validation, feedback loops, checklist) and clearly exceeds 4's "most checkpoints".

Progressive Disclosure

Section headers are clear and pattern references are well-labeled with one-line descriptions, but the disclosure contract is broken: the body links to five pattern files (webhook_processing.md, http_api_integration.md, database_operations.md, ai_agent_workflow.md, scheduled_tasks.md) that do not exist in the bundle, so navigation dead-ends. Simultaneously, content that clearly belongs in those detail files — the full Batch Processing pattern, Performance, and Integration-Specific Gotchas sections — is inlined, and the batch pattern is even flagged "(below)" while its siblings point outward. This sits between anchors 2 and 3: better organized than "minimal structure / buried references", but the missing files plus inline bulk keep it from 4.

Specificity

The description lists several concrete action contexts — "building new workflows, designing workflow structure, choosing workflow patterns, planning workflow architecture" and "optimizing a slow workflow or speeding up large-item-count processing (node count, batchSize, all-items vs per-item)" — and enumerates six covered architectures (webhook, API, database, AI, batch, scheduled). It falls short of the 5 anchor because the headline "what" is a resource description ("Proven workflow architectural patterns") rather than a list of concrete operations, and verbs like "designing" and "choosing" stay somewhat abstract; it is clearly above 3's "1-2 concrete actions" coverage.

Completeness

Both halves are explicit: the "what" ("Proven workflow architectural patterns from real n8n workflows... Covers webhook, API, database, AI, batch processing, and scheduled automation architectures") and the "when" ("Use when building new workflows... Always consult this skill when the user asks to create, build, or design an n8n workflow, automate a process, or connect services"), with concrete trigger phrases throughout — matching the 5 anchor. Voice is third person throughout, so no voice penalty applies.

Trigger Term Quality

Comprehensive natural-phrase coverage: "webhook processing", "HTTP API integration", "database operations", "AI agent workflows", "batch processing", "scheduled tasks", "automate a process", "connect services", "optimize a slow workflow", plus the brand term "n8n" and the explicit catch "even if they don't explicitly mention 'patterns'". It matches the 5 anchor's synonym-and-variation coverage; no common phrasing is missing.

Distinctiveness Conflict Risk

The n8n niche and its pattern vocabulary are distinct, and the description names the platform explicitly, giving minimal conflict with unrelated skills. However, the clause "Always consult this skill when the user asks to... automate a process, or connect services" is unscoped by n8n and would fire on generic automation/integration requests, so it sits at 4 ("mostly distinct; minor overlap risk") rather than 5.