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, expert-oriented router body: actionable tool guidance and a clearly sequenced, validation-backed protocol carry it. Slight redundancy in the drift messaging and a large inline tool catalog keep it just short of exemplary on conciseness and progressive disclosure.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Lean and opinionated, assuming Claude's competence with no beginner-concept padding, but the drift/trust-live-tools theme recurs across the opening, 'Lean on skills, not training data', and Non-negotiables #1, so a little could be tightened. | 4 / 5 |
Actionability | Highly actionable for an instruction-only skill: concrete tool names, parameter shapes (short- vs long-form nodeType), specific ops (patchNodeField, setNodeGroups), and exact error strings (INSTANCE_AMBIGUOUS, NOT_CONFIGURED, WORKFLOW_NOT_EXPOSED) to act on. | 5 / 5 |
Workflow Clarity | 'The protocol, in order' gives a 5-step sequenced flow with explicit validation checkpoints (validate_workflow before activating, n8n_get_workflow after to inspect connections), and Non-negotiable #2 plus the 'When in doubt' section supply feedback loops for error recovery. | 5 / 5 |
Progressive Disclosure | Well-organized sections with peer-skill references that are one level deep and clearly signaled via the Skill index; the minor gap is the ~50-line inline n8n-mcp tool catalog that could largely live in the referenced n8n-mcp-tools-expert skill. | 4 / 5 |
Total | 18 / 20 Passed |