Content
81%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 and workflow-clear, with exact tool calls, return shapes, and explicit validation/feedback loops for high-stakes credential writes. Its main weakness is conciseness: the core credential-safety guidance is repeated across many sections and the monolithic structure leaves no room for progressive disclosure into reference files.
Suggestions
Consolidate the verify-before-credential-write and INSTANCE_AMBIGUOUS→switch→retry guidance into a single authoritative section; have other sections link to it instead of restating it (Golden rules, Credential operations, copy task, and Quick reference currently overlap heavily).
Consider moving the full error-envelope table and the INSTANCE_AMBIGUOUS payload deep-dive into a references/ file, keeping SKILL.md as a lean overview with one-level-deep links.
Tighten the 'How targeting behaves' section — several of its bullets restate rules already covered in Golden rules and Credential operations.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | No padding with concepts Claude already knows, but the verify-before-credential-write and INSTANCE_AMBIGUOUS→switch→retry guidance is restated across the Golden rules, INSTANCE_AMBIGUOUS section, 'How targeting behaves', Recovery playbook, Credential operations, copy task, and Quick reference — could be tightened by deduplication. | 3 / 5 |
Actionability | Fully executable, copy-paste-ready tool calls (e.g. n8n_instances({mode:"list"}), {mode:"switch", name:"prod"}), exact return shapes, error codes, and numbered procedures cover the common cases. | 5 / 5 |
Workflow Clarity | Clear numbered sequences with an explicit validation checkpoint before credential writes, plus feedback loops (INSTANCE_AMBIGUOUS→switch→retry, NOT_FOUND→re-list→switch→retry) and checklists (Golden rules, Quick reference); validation is present so the destructive-cap does not apply. | 5 / 5 |
Progressive Disclosure | Well-organized single file with clear headers and a Quick reference for navigation, but with no bundle files the ~180-line body is monolithic and the error-envelope / INSTANCE_AMBIGUOUS deep-dive could plausibly live in a one-level-deep reference. | 4 / 5 |
Total | 17 / 20 Passed |