Content
71%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 executable, copy-paste-ready patterns and good sequencing, but it loses points on conciseness from repeated restatements and on progressive disclosure because the four referenced bundle files are absent from the skill directory.
Suggestions
Dedupe the recurring points: state the webhook `.body` nesting, the canonical `[{json:{...}}]` return, and the `$helpers`/sandbox note once each and link out for depth instead of repeating them across Quick Start, Return Format, and Built-in Functions sections.
Provide the referenced bundle files (DATA_ACCESS.md, COMMON_PATTERNS.md, ERROR_PATTERNS.md, BUILTIN_FUNCTIONS.md) or remove the dangling links, so the "See:" pointers actually resolve.
Tighten or fold the "Integration with Other Skills" and "Quick Reference Checklist" sections — they restate guidance already covered and add tokens without proportionate new, actionable information.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is mostly efficient and assumes Claude's competence (no primers on what JS or n8n is), but several points are restated across sections — webhook `.body` nesting, the canonical return shape, and the "$helpers is undefined" sandbox note each appear 2–3 times — and the Integration/Quick Reference Checklist sections add length without proportional new guidance. | 3 / 5 |
Actionability | Code throughout is fully executable and copy-paste ready, covering common cases with explicit wrong/right (❌/✅) comparisons, concrete helpers (this.helpers.httpRequest, DateTime, $jmespath), and a worked sum/aggregate example; specific examples cover the common Code-node shapes. | 5 / 5 |
Workflow Clarity | A clear transform gatekeeper sequence (expression → IIFE → Code node) and a deployment Quick Reference Checklist provide good sequencing and a pre-flight verification list, but explicit validate→fix→retry feedback loops are only implicit rather than spelled out as a recovery cycle. | 4 / 5 |
Progressive Disclosure | The body is well-sectioned and signals four one-level-deep references (DATA_ACCESS.md, COMMON_PATTERNS.md, ERROR_PATTERNS.md, BUILTIN_FUNCTIONS.md) via clear "See:" pointers, but none of those files exist in the bundle — the references are dangling, so the disclosed structure does not actually resolve. | 3 / 5 |
Total | 15 / 20 Passed |