Content
77%Reviews 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 concrete, executable tool calls and clearly sequenced validation-gated workflows. Its main weaknesses are verbosity from repeated content across sections and four missing reference files that the overview points to but which are absent from the bundle.
Suggestions
Add the four referenced bundle files (SEARCH_GUIDE.md, VALIDATION_GUIDE.md, WORKFLOW_GUIDE.md, OPERATIONS_GUIDE.md) to the skill, or remove the dead links and inline the essential content.
De-duplicate the body: the Summary, Best Practices, and Common Mistakes sections repeat material already covered in Quick Reference, Tool Selection Guide, and Performance Characteristics — collapse overlaps to reduce tokens.
Consolidate the overlapping tool tables (Quick Reference 'Most Used Tools' and Performance Characteristics) into a single table to tighten the document.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body assumes Claude's competence (no preamble on what n8n/MCP is) but is ~390 lines with notable redundancy — the Summary restates Best Practices, the Performance table overlaps the Quick Reference table, and Common Mistakes appears both inline and as a table. It is mostly efficient but could be tightened, matching the 2 anchor rather than the lean 3. | 2 / 3 |
Actionability | Provides fully executable, copy-paste-ready tool calls with exact parameters (e.g. `search_nodes({query: "slack"})`, `get_node({nodeType: "nodes-base.slack"})`) plus WRONG/CORRECT code contrasts, matching the executable-and-specific anchor of 3. | 3 / 3 |
Workflow Clarity | Multi-step workflows are clearly sequenced with explicit validation checkpoints and feedback loops ("validate → fix → validate again", "Validate after every significant change", iterative workflow building with re-validation), matching the clear-sequence-with-validation anchor of 3. | 3 / 3 |
Progressive Disclosure | The body is structured as an overview pointing to four well-signaled one-level-deep references (SEARCH_GUIDE.md, VALIDATION_GUIDE.md, WORKFLOW_GUIDE.md, OPERATIONS_GUIDE.md), but none of these referenced files actually exist in the bundle, so the cross-file structure does not resolve. The signaling intent is strong, but the broken/dead references are a real defect that fits the 2 anchor (references present but not actually delivered) rather than the clean 3. | 2 / 3 |
Total | 10 / 12 Passed |