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.
The body is highly actionable with executable commands and a well-validated workflow; it is concise and well-structured, with only slight room to offload the command catalog into a reference file.
Suggestions
Consider moving the long 'Common commands' code catalog into a references file (e.g. commands.md) and summarizing only the canonical patterns inline, to push progressive disclosure toward 5.
Trim the repeated foreground/background caveats between 'Background-first safety' and 'Click coordinates safely' to tighten conciseness further.
Add a one-line 'Use Peekaboo when...' trigger near the top of the body to mirror the frontmatter gap and aid skill selection.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Dense operational specifics with no concept padding; assumes Claude knows the domain. Minor redundancy across the foreground/background caveats keeps it just short of fully lean. | 4 / 5 |
Actionability | Fully executable, copy-paste-ready bash snippets with exact flags and selectors, covering the common cases (status, capture, AX tree, click, type, paste) plus targeted examples for coordinate clicks. | 5 / 5 |
Workflow Clarity | A 9-step numbered workflow with explicit validation checkpoints (version, host selection, permissions, fresh snapshots, mutation verification, artifact checks) and a retry feedback loop ('run a fresh see before retry'), satisfying the destructive/batch validation requirement. | 5 / 5 |
Progressive Disclosure | Well-organized sections with a one-level-deep pointer to the source-of-truth docs; no bundle files exist, and ~150 lines of inlined command reference could plausibly be split out, keeping it at 4 rather than 5. | 4 / 5 |
Total | 18 / 20 Passed |