peekaboo
Capture and automate macOS UI with the Peekaboo CLI.
56
43%
Does it follow best practices?
Impact
77%
1.92xAverage score across 3 eval scenarios
Risky
Do not use without reviewing
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/peekaboo/SKILL.mdQuality
Discovery
22%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description is too terse and vague to effectively guide skill selection. It names the tool (Peekaboo CLI) and platform (macOS) but fails to enumerate specific capabilities or provide any trigger guidance for when Claude should select this skill. It would benefit significantly from listing concrete actions and adding explicit 'Use when...' conditions.
Suggestions
Add a 'Use when...' clause specifying trigger conditions, e.g., 'Use when the user asks about taking screenshots on macOS, automating UI interactions, inspecting accessibility elements, or mentions Peekaboo.'
List specific concrete actions the skill enables, e.g., 'Takes screenshots, clicks UI elements, reads accessibility trees, lists windows, and automates macOS GUI interactions using the Peekaboo CLI.'
Include natural trigger terms users would say, such as 'screenshot', 'screen capture', 'UI automation', 'click button', 'window list', 'accessibility tree', 'GUI testing'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description says 'Capture and automate macOS UI' which is vague. It doesn't list specific concrete actions like taking screenshots, clicking elements, reading accessibility trees, or other specific capabilities. 'Capture' and 'automate' are broad terms. | 1 / 3 |
Completeness | It partially addresses 'what' (capture and automate macOS UI) but is vague about it, and completely lacks a 'when' clause. There's no 'Use when...' guidance or explicit trigger conditions. Per the rubric, a missing 'Use when...' clause caps completeness at 2, and the 'what' is also weak, so this scores a 1. | 1 / 3 |
Trigger Term Quality | Includes 'macOS UI', 'Peekaboo', and 'CLI' which are somewhat relevant keywords. However, it's missing natural user terms like 'screenshot', 'screen capture', 'click button', 'UI automation', 'accessibility', or 'GUI testing' that users would actually say. | 2 / 3 |
Distinctiveness Conflict Risk | The mention of 'Peekaboo CLI' and 'macOS UI' provides some distinctiveness, narrowing it to a specific tool and platform. However, 'capture and automate' could overlap with general automation or screenshot skills without clearer scoping. | 2 / 3 |
Total | 6 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid reference-style skill with excellent actionability through numerous concrete, executable examples covering a wide range of Peekaboo CLI capabilities. Its main weaknesses are the lack of validation/error-recovery steps in workflows and the monolithic structure that packs a full command catalog inline rather than splitting it into referenced files. Trimming the feature listing and adding error handling guidance would significantly improve it.
Suggestions
Add validation checkpoints and error recovery guidance to multi-step workflows (e.g., check if `peekaboo see` found expected elements before clicking, handle permission failures gracefully).
Move the exhaustive feature/command catalog to a separate REFERENCE.md and keep only the most essential commands in SKILL.md with a pointer to the full reference.
Add brief troubleshooting notes for common failure modes (e.g., element not found, permissions not granted, stale snapshot IDs).
| 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 command catalog that could be trimmed or referenced externally. Some of this is useful as a quick reference, but it borders on verbose for a SKILL.md. | 2 / 3 |
Actionability | The skill provides numerous concrete, copy-paste-ready bash commands covering the full range of use cases. The examples are executable, specific, and cover real workflows like see->click->type, window management, and keyboard input. | 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 a monolithic file with no references to external documentation. The extensive command catalog and parameter listings could be split into separate reference files, keeping the SKILL.md as a concise overview with pointers. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
72%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 8 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata.version' is missing | Warning |
metadata_field | 'metadata' should map string keys to string values | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 8 / 11 Passed | |
- Repository
- Hung-Reo/hungreo-openclaw
- Commit
a5bf5e0
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.