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, failing to enumerate specific capabilities of the Peekaboo CLI or provide explicit trigger conditions for when Claude should select this skill. While the tool name 'Peekaboo' and 'macOS UI' provide some distinctiveness, the lack of concrete actions and a 'Use when...' clause significantly limits its effectiveness for skill selection.
Suggestions
Add a 'Use when...' clause specifying trigger scenarios, e.g., 'Use when the user asks to take screenshots, inspect UI elements, or automate macOS desktop interactions.'
List specific concrete actions the skill supports, such as 'take screenshots, list UI elements, click buttons, read accessibility tree, automate GUI workflows on macOS.'
Include natural trigger terms users might say, such as 'screenshot', 'screen capture', 'UI automation', 'accessibility', 'desktop automation', 'GUI testing'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description mentions 'capture and automate macOS UI' which is vague. It does not list specific concrete actions like 'take screenshots', 'click buttons', 'read screen elements', or 'automate workflows'. 'Capture' and 'automate' are broad verbs without detail. | 1 / 3 |
Completeness | The description partially answers 'what' (capture and automate macOS UI) but is vague, and completely lacks a 'when' clause or any explicit trigger guidance for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | Includes some relevant terms like 'macOS UI', 'Peekaboo CLI', and 'capture'/'automate', but misses natural user terms like 'screenshot', 'screen capture', 'UI automation', 'click', 'accessibility', or 'GUI testing'. 'Peekaboo' is a tool name users might mention but is niche. | 2 / 3 |
Distinctiveness Conflict Risk | The mention of 'Peekaboo CLI' and 'macOS UI' provides some distinctiveness, but 'capture and automate' could overlap with other automation or screenshot tools. The niche tool name helps but the vague actions reduce clarity. | 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, actionable reference for the Peekaboo CLI with excellent concrete examples and good coverage of commands. Its main weaknesses are the lack of validation/error-recovery steps in workflows (important for UI automation) and the monolithic structure that packs a full command catalog plus extensive examples into a single file. Trimming the feature catalog and adding verification checkpoints would meaningfully improve it.
Suggestions
Add validation/error-recovery steps to workflows, e.g., verify `peekaboo see` output contains expected elements before clicking, and handle permission check failures explicitly.
Move the exhaustive feature/command catalog to a separate REFERENCE.md and keep SKILL.md focused on the quickstart, common patterns, and targeting parameters.
Add a brief troubleshooting or 'common failures' section covering scenarios like missing permissions, stale snapshot IDs, or elements not found.
| 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 moved to a reference file. Some redundancy exists between the feature list and the examples. | 2 / 3 |
Actionability | The skill provides fully executable, copy-paste-ready bash commands throughout. Examples cover the most common workflows with specific flags, arguments, and realistic values. The targeting parameters and common flags are concrete and specific. | 3 / 3 |
Workflow Clarity | The 'See -> click -> type' flow is well-sequenced and represents the most reliable pattern. However, there are no explicit validation checkpoints or error recovery steps — e.g., what to do if permissions fail, if `see` returns no elements, or if a click misses its target. For UI automation (which can be fragile), feedback loops would be valuable. | 2 / 3 |
Progressive Disclosure | The content is reasonably well-organized with clear section headers, but it's monolithic — the extensive command catalog and numerous examples could be split into reference files. With no bundle files provided, there's no progressive disclosure structure; everything is inline in one file. | 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
d8d7f4b
- 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.