Content
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides strong actionability with numerous concrete, executable examples covering a wide range of Peekaboo CLI capabilities. Its main weaknesses are the verbose command catalog that reads like reformatted help output, and the lack of validation/error-recovery steps in workflows. The content would benefit from splitting the reference material into separate files and adding explicit checkpoints for multi-step operations.
Suggestions
Add validation checkpoints to multi-step workflows (e.g., verify permissions succeeded before proceeding, check that `see` returned expected element IDs before clicking, handle click failures).
Move the exhaustive command catalog (Core/Interaction/System/Vision feature lists) and parameter reference sections into a separate REFERENCE.md file, keeping only the most essential commands inline.
Add a brief troubleshooting or error-recovery section covering common failure modes (permissions denied, element not found, wrong window targeted).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is fairly efficient and avoids explaining basic concepts, but the exhaustive feature listing (Core/Interaction/System/Vision sections) is essentially a reformatted `--help` output that adds bulk without much instructional value. Some trimming of the command catalog would improve token efficiency. | 2 / 3 |
Actionability | The skill provides numerous concrete, copy-paste-ready bash commands covering the full range of use cases—see->click->type flows, window targeting, capture, app management, keyboard input, and more. Every example is executable with specific flags and arguments. | 3 / 3 |
Workflow Clarity | The 'See -> click -> type' example demonstrates a clear multi-step workflow, and the quickstart provides a logical sequence. However, there are no explicit validation checkpoints or error recovery steps (e.g., what to do if permissions fail, if an element ID isn't found, or if a click doesn't land correctly). | 2 / 3 |
Progressive Disclosure | The content is reasonably well-organized with clear section headers, but it's monolithic—the extensive command catalog and parameter reference could be split into separate reference files. There are no bundle files and no references to external documents for deeper details. | 2 / 3 |
Total | 9 / 12 Passed |