Content
86%Weight 40%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
A tight, highly actionable debugging skill with concrete tool calls and clear per-scenario guidance that respects Claude's competence and the context budget. The main improvement room is converting the prose workflows into explicit numbered validate-inspect-retry sequences.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean, assumes Claude knows n8n, and avoids explaining basic concepts; the only trimming room is the stacked "Do not restate... and do not attribute..." guardrail clauses, which sit just above the efficient anchor rather than the fully lean one. | 4 / 5 |
Actionability | It gives concrete parameterized calls such as `executions(action="debug")` and `executions(action="get-resolved-node-parameters", executionId, nodeName)` plus a precise "Check `emptyResolutions` first" directive, matching the fully-executable anchor covering common cases. | 5 / 5 |
Workflow Clarity | Each scenario (failed execution, wrong-value, event-triggered) has a clear sequenced path with checkpoints like "inspect the real result before responding" and "do this unprompted", but it is prose rather than an explicit validate-fix-retry loop, leaving it just below the top anchor. | 4 / 5 |
Progressive Disclosure | At under 50 lines and single-purpose, it is well organized into clear sections with one clearly-signaled, conditionally-gated external reference and no local bundle files, satisfying the simple-skill exception for a top score. | 5 / 5 |
Total | 18 / 20 Passed |