Content
73%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.
The body is highly actionable with a clear, validated decision workflow, but it suffers from meaningful repetition of the webhook-body and native-node-first rules, and its progressive-disclosure structure is broken in practice: all four referenced detail files are missing from the bundle. Fixing the dangling references is the single highest-impact improvement.
Suggestions
Ship the four referenced files (DATA_ACCESS.md, COMMON_PATTERNS.md, ERROR_PATTERNS.md, BUILTIN_FUNCTIONS.md) in a references/ directory, or remove the links and fold their essential content inline — the current bundle promises a detail layer that does not exist.
State the webhook `.body` rule once (in the data-access section) and the native-node-first list once (in the gate), dropping the duplicates in Essential Rules, Top Mistakes, Common Patterns, and the checklist.
Trim meta-filler such as the closing "Ready to write JavaScript!" paragraph and the vague per-skill bullet lists under "Integration with Other Skills" in favor of one-line pointers.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Mostly efficient, n8n-specific material, but noticeably repetitive: webhook `.body` nesting is explained four times (Essential Rules #4, the "Critical: Webhook Data Structure" section, Top Mistakes #5, the checklist) and the native-node-first list recurs ~5 times (the gate, "Native first:", Common Patterns overview, the When-to-Use table, the "Not on the list" paragraph). Anchor 3 fits — could be tightened considerably without losing information. | 3 / 5 |
Actionability | Fully executable guidance throughout: copy-paste code for both modes and return shapes, exact error messages ("Code doesn't return items properly", "ReferenceError: $helpers is not defined"), specific env vars, and a JSON snippet for the `notes` convention. Matches the copy-paste-ready top anchor. | 5 / 5 |
Workflow Clarity | The decision flow is explicit and validated: a numbered 3-step gate, a decision shortcut, the enforced `Why Code:` note convention, a pre-deployment checklist, `validate_node` for verification, and an error-message lookup table for recovery. Batch-loop guidance includes safety steps (Limit 1 after the done output, static-data accumulation), so the batch-operation cap does not apply. | 5 / 5 |
Progressive Disclosure | The body links repeatedly to DATA_ACCESS.md, COMMON_PATTERNS.md, ERROR_PATTERNS.md, and BUILTIN_FUNCTIONS.md, but no references/, scripts/, or assets/ directories exist in the bundle — every "See:" link is a dead end, and detail that should live in those files is inlined in a ~430-line SKILL.md instead. Scored against the actual (empty) bundle structure, this lands at anchor 2: the disclosed layer is absent, so navigation breaks wherever a link is followed. | 2 / 5 |
Total | 15 / 20 Passed |