Content
88%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 dense, highly actionable body that covers when to extract, input/output contracts, calling modes, and anti-patterns with concrete code, commands, tables, and a validation-backed checklist. Its main weaknesses are mild editorial padding in the intro and two referenced files that are signaled but not actually shipped in the bundle.
Suggestions
Trim the motivational framing in the opening paragraphs (encapsulation/reuse/drift) — Claude already knows why duplication is bad; lead with the mechanism instead.
Ship SUBWORKFLOW_PATTERNS.md and NAMING_AND_DISCOVERY.md in a references/ directory, or inline the essential bits they promise (the N+1 worked example, the fire-and-forget polling pattern, the verb-first prefix convention) so the signaled references resolve.
Move the long 'Integration with other skills' list toward the end or into a reference file; it is navigational context rather than core instruction and competes with the actionable sections for attention.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Mostly efficient and dense with concrete JSON, tables, and commands, but the opening framing ('the things functions buy you everywhere... badly underused... quietly drift apart') and occasional editorial flourishes ('ambushes every caller') explain motivations Claude already knows and could be trimmed. | 4 / 5 |
Actionability | Provides copy-paste-ready JSON for the trigger's workflowInputs.values, concrete MCP commands (n8n_list_workflows, n8n_get_workflow, n8n_test_workflow, validate_workflow), exact expression syntax ($json.<field>, $('When Executed by Another Workflow').first().json.<field>), and explicit return shapes covering the common cases. | 5 / 5 |
Workflow Clarity | Multi-step processes are clearly sequenced with explicit validation checkpoints ('verify with validate_workflow and n8n_get_workflow before you're done'), a feedback loop for destructive field renames (enumerate callers → migrate → verify), and a closing shipping checklist. | 5 / 5 |
Progressive Disclosure | Well-organized into focused sections with a clear 'Reference files' table and one-level-deep, clearly signaled pointers to SUBWORKFLOW_PATTERNS.md and NAMING_AND_DISCOVERY.md, but neither referenced file is present in the bundle (no references/ directory exists), leaving those navigation targets dangling. | 4 / 5 |
Total | 18 / 20 Passed |