Content
75%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 content is highly actionable with executable CLI commands and a solid connection-state workflow, weakened only by minor verbosity and an implied rather than explicitly numbered overall sequence. It is well-structured for a single-file skill.
Suggestions
Trim the marketing intro and 'rather than auth plumbing' filler to assume Claude's competence and save tokens.
Add a short numbered overview of the full flow (install → login → connect → search → run) so the end-to-end sequence is explicit, and reconcile the dangling 'Step 2' reference.
Consider moving the proxy flags table and clientAction state-machine detail into a separate reference file to keep the overview lean.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is mostly concrete commands, but includes some padding such as the marketing-style intro ('understand the deeper meaning and impact of text data') and 'so you can focus on the integration logic rather than auth plumbing' that could be trimmed. | 3 / 5 |
Actionability | Copy-paste ready commands cover the common cases end-to-end — install, login, connection ensure, polling, action list/run, and proxy — plus a concrete flags table for the proxy path. | 5 / 5 |
Workflow Clarity | The connection state machine has explicit checkpoints and a feedback loop (poll until READY, handle CLIENT_ACTION_REQUIRED by re-polling), but the overall install-to-run sequence is implied rather than a clearly numbered list and 'Step 2' is referenced without a matching header. | 4 / 5 |
Progressive Disclosure | No bundle files exist and the single SKILL.md is well-organized into clear sections, but at ~140 lines with all content inline (including the proxy flags table and clientAction state detail) some material could be split into a reference. | 4 / 5 |
Total | 16 / 20 Passed |