Conciseness

The body is dense with non-obvious, product-specific behavior (draft vs. active versionIds, 'unreconstructable-context' tags, run-step refusal rules, mocked-input semantics) and contains essentially no explanation of concepts Claude would already know. Not 4: there is no padded or over-explained passage to trim — each section adds information the model cannot infer; the rhetorical restatements ("sends the message, charges the card, or deletes the row") are doing safety work, not filling space.

Actionability

Concrete, executable tool invocations with full argument shapes throughout: `executions(action="run-step", workflowId, nodeName, reuseExecutionId=...)`, a complete `toolArguments={"query": "login fails", "status": "open"}` example, named actions (`debug`, `get-resolved-node-parameters`, `get-node-output`, `get-as-code`), and specific field names to check (`emptyResolutions`, `failedExpressions`, `workflowVersionId`, `ranThroughNodeNames`). Not 4: the specific examples cover the common cases (failed node, fix confirmation, wrong output on a successful run) with exact commands and semantics, not high-level hints.

Workflow Clarity

Each scenario is sequenced with explicit decision points and verification gates: re-run the failing path before claiming a fix, classify the node (read/transform = safe, write = do not run, unsure = treat as write) before run-step, and confirm a fix only via a new live run after publish — feedback loops are present for the risky operations. Not 5: the overall entry-point flow is implicit — the reader must synthesize the order across sections (when to use `debug` vs `run-step` vs `get-resolved-node-parameters`) rather than following one explicit ordered procedure; not 3: validation and safety checkpoints are explicit, not missing.

Progressive Disclosure

The single file is cleanly sectioned by scenario and the one detail-heavy lookup (trigger inputData shapes) is pushed to a clearly-signaled one-level-deep path: "read ${N8N_WORKSPACE_DIR}/knowledge-base/reference/trigger-input-data-shapes.md". Not 5: no bundle structure exists, and at ~195 lines some specialized material (tool/sub-node/MCP-registry run-step rules) would fit better in a reference file so SKILL.md stays a lean overview; not 3: what is inline is scenario-critical and navigation is easy.

Specificity

The description names the domain and one concrete action — "Debug failed or wrong-output workflow executions using executions tools" — but the action is generic ("debug") and the tool-specific capabilities (inspect resolved parameters, replay a single node, detect silent null resolutions) are not listed. Not 4: it does not enumerate several specific actions like the "Extracts text, fills forms, converts pages" anchor; not 2: it is more concrete than a bare domain mention.

Completeness

Explicitly answers both: what — "Debug failed or wrong-output workflow executions using executions tools"; when — "Load when the user reports execution failures, unexpected node output, empty parameter values after a successful run, or a node showing a red or failed expression error", with concrete trigger phrases. This matches the anchor-5 exemplar structure; a 'Use/Load when...' clause is present and specific, so no cap applies.

Trigger Term Quality

Triggers are natural and varied: "execution failures", "unexpected node output", "empty parameter values after a successful run", "a node showing a red or failed expression error" — phrasings a user would plausibly say verbatim. Not 5: common synonyms like "workflow run failed", "node error", or "expression resolved to empty" variations are absent; not 3: coverage goes well beyond a couple of generic keywords.

Distinctiveness Conflict Risk

The triggers are niche and distinctive ("red or failed expression error", "empty parameter values after a successful run") and unlikely to fire for unrelated skills. Not 5: "Debug failed... workflow executions" could mildly overlap with a general workflow-building or verification skill; not 3: the trigger phrases are far more specific than the 'Works with document files' anchor.