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.
This is a strong operational skill: fully executable commands with explicit validation checkpoints and error-recovery pitfalls, written for a competent reader with almost no padding. The only weaknesses are minor — a couple of trimmable asides and a stale-repo-note that will rot. Structure is appropriate for a self-contained single-file skill.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense and assumes Claude's competence (CDP, Electron single-instance lock, Vite dev mode) with no basic-concept padding, but a few tokens could be trimmed: "The renderer is a Chromium page, so everything DevTools can read, a script can read" and the time-sensitive stale-note about profile-typing-lag.md, which is repo-state commentary not placed in an old-patterns/deprecated section. Fits anchor 4 (efficient, minor trimmable instances) rather than 5. | 4 / 5 |
Actionability | Every path is copy-paste ready: the curl port check with --max-time and env-var default, the `node scripts/eval.mjs "..."` one-liner, a complete CDP.connect import snippet with match and eval usage, and a full isolated-instance launch command with HERMES_HOME, port, and --user-data-dir. This matches anchor 5 (fully executable commands covering the common cases). | 5 / 5 |
Workflow Clarity | The flow is explicit and validated: check the port first ("Check before doing anything else"), eval against the user's window or launch an isolated instance when no port exists, with concrete validation checkpoints (curl response, "DevTools listening on ws://... — that line is the proof the port opened", "Poll, don't probe once") and error-recovery guidance for ECONNREFUSED and self-exited probes. Operations are read-only, so the destructive/batch cap does not apply; this is anchor 5. | 5 / 5 |
Progressive Disclosure | No bundle files exist, and the body is well-sectioned (Overview / When to Use / The port / Reading the DOM / isolated instance / Pitfalls) while deferring bulk detail to real repo files (eval.mjs, scripts/perf/lib/cdp.mjs) instead of inlining them. It sits at anchor 4 rather than 5 because at ~145 lines, with the under-50-line simple-skill exception unavailable, sections like the winning-rule deep dive could arguably live in a separate reference file. | 4 / 5 |
Total | 18 / 20 Passed |