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.
An excellent instruction-heavy skill body: executable code, verbatim UI directives, exact endpoints and error semantics, and workflows with genuine validation checkpoints and recovery loops. The only real improvements are marginal tightening of repeated Slack guidance and potentially splitting app-specific tips into reference files.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense with QM-specific operational detail ("an absent sandbox API key is expected", "Inspect successful and error, not just the HTTP status") and explains nothing Claude already knows. Minor trimming is possible — Slack linking guidance is repeated in both the connect section and step 3, and a few cross-references ("the connect option above") could be consolidated. | 4 / 5 |
Actionability | The `apps()` fetch helper is complete and copy-paste ready, directives are given verbatim (`::connect-apps{}`, `::add-to-slack{}`), and error handling is exact ("`409 choose_account` lists matching connections: ask which, then pass `accountId`"). Concrete steps 1-5 with executable calls cover the common cases. | 5 / 5 |
Workflow Clarity | Steps 1-5 are clearly sequenced with explicit validation checkpoints ("only claim success once the returned account ID is listed", "remove the old one with apps(\"disconnect\", {accountId}), never before") and error-recovery feedback loops (on 502, read `cause`/`providerStatus` and "back off and shrink the page rather than repeating the same request"). Destructive and batch operations (disconnect, bulk reads) all carry validation, so the cap at 3 does not apply. | 5 / 5 |
Progressive Disclosure | Sections are well-organized and easy to navigate (scenario-based headers, a routing table for app-specific skills), and with no bundle files there are no broken or nested references. At ~117 lines it exceeds the under-50-line simple-skill case, and app-specific content (Gmail drafting, X image upload, Slack flows) is inlined where it could arguably be split into reference files. | 4 / 5 |
Total | 18 / 20 Passed |