Content
67%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 concrete CLI commands and a clear connection-to-execution workflow. Its weaknesses are some unnecessary explanatory padding in the intro and slightly inconsistent step numbering.
Suggestions
Trim the marketing-style intro paragraph and the "so you can focus on the integration logic rather than auth plumbing" aside to save tokens.
Fix the inconsistent numbering ("Step 2" referenced without a labeled Step 1/Step 2) into a coherent numbered sequence so the workflow reads cleanly.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is mostly lean code commands, but the opening paragraph explaining what Saleshood is and phrases like "so you can focus on the integration logic rather than auth plumbing" are unnecessary padding that could be trimmed. | 3 / 5 |
Actionability | It provides concrete, copy-paste-ready commands for install, auth, connection, action discovery, action runs, and proxy requests with a clear options table, with only minor gaps such as no concrete example action names beyond placeholders. | 4 / 5 |
Workflow Clarity | The install → authenticate → connect → search → run sequence is clear and the connection state machine (READY / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR) with polling forms a feedback loop, though the inconsistent Step 1/1b/Step 2 numbering leaves a minor sequencing gap. | 4 / 5 |
Progressive Disclosure | No bundle files exist and the single SKILL.md is well-organized into clearly headed sections (Overview, Working with Saleshood, Popular actions, Best practices), which is good structure for a self-contained skill even without external references. | 4 / 5 |
Total | 15 / 20 Passed |