Content
93%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 exemplary lean operational skill: concrete commands with expected outputs, explicit safety warnings ("Anything you send is real"), and crisp routing guidance at the top. The sole weakness is the absence of failure-recovery steps in the workflow.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Every line is a runnable command, a path, or an operative rule; there is zero explanation of concepts Claude already knows (no "what CDP is", no library introductions). The ~40-line body assumes competence and every token earns its place. | 5 / 5 |
Actionability | Fully executable, copy-paste-ready guidance: the exact `pnpm world up`/`pnpm dev` commands with their printed outputs, `node $S new-session`/`send "Claude Opus 5.5" "Say hello"`/`wait-idle 180` invocations, a real JS eval snippet, and a complete sqlite3 query — the common cases are all covered with concrete examples. | 5 / 5 |
Workflow Clarity | The sequence is clear and ordered (find app → set CDP_URL → new-session first → send → wait-idle → shot/eval → world down), with real checkpoints like "wait-idle 180 # until the Run task button is back" and "Reload after state-heavy changes". It falls short of level 5 because there is no error-recovery loop: no guidance for what to do when a command fails, the CDP URL is stale, or the warned-about mid-run session switch occurs. | 4 / 5 |
Progressive Disclosure | An under-50-line single-purpose skill with clean sections (Find the app / Commands / Rules); everything needed is inline and the one bundle file (scripts/cdp.mjs, invoked via the S= variable) is appropriately factored out as an executable rather than inlined. No external reference docs are needed, matching the simple-skill exception. | 5 / 5 |
Total | 19 / 20 Passed |