Capture and automate macOS UI with the Peekaboo CLI.
65
Quality
56%
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 ./openclaw/skills/peekaboo/SKILL.mdQuality
Discovery
32%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 identifies the tool and general domain but is too terse to be effective for skill selection. It lacks specific capabilities, natural trigger terms users would say, and critically missing the 'Use when...' guidance that helps Claude choose this skill appropriately.
Suggestions
Add a 'Use when...' clause specifying triggers like 'when user asks to take screenshots', 'automate Mac apps', 'interact with desktop UI', or 'capture screen content'
Expand specific capabilities: 'take screenshots, capture window contents, automate clicks and keyboard input, read UI elements'
Include natural user terms: 'screenshot', 'screen capture', 'Mac automation', 'desktop interaction', 'GUI automation'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (macOS UI) and two actions (capture, automate), but lacks specific concrete actions like 'take screenshots', 'click buttons', 'read window contents', or 'record interactions'. | 2 / 3 |
Completeness | Provides a brief 'what' but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | Includes 'macOS UI' and 'Peekaboo CLI' which are relevant, but misses natural user terms like 'screenshot', 'screen capture', 'automation', 'click', 'window', or 'Mac desktop'. | 2 / 3 |
Distinctiveness Conflict Risk | 'Peekaboo CLI' is a distinctive tool name, but 'automate macOS UI' could overlap with other automation or macOS-related skills without clearer trigger boundaries. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
79%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a high-quality, actionable skill with excellent conciseness and immediately executable examples. The main weaknesses are the lack of validation/verification steps for UI automation workflows (which are inherently fragile) and the monolithic structure that could benefit from splitting detailed examples into separate files.
Suggestions
Add validation checkpoints to workflows, e.g., 'After clicking, use `peekaboo see` to verify the expected UI state before proceeding'
Include error recovery guidance for common UI automation failures (element not found, window not focused, permission denied)
Consider splitting the extensive examples section into a separate EXAMPLES.md file, keeping only the quickstart in SKILL.md
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely lean and efficient - no explanations of what macOS is or how CLIs work. Every section provides direct, actionable information without padding. The feature list is dense but necessary for discoverability. | 3 / 3 |
Actionability | Fully executable bash commands throughout with real flags and arguments. Examples are copy-paste ready with concrete values (paths, coordinates, app names). No pseudocode - all commands are immediately runnable. | 3 / 3 |
Workflow Clarity | The 'See -> click -> type' section shows a clear sequence, but lacks explicit validation checkpoints. For UI automation (which can fail silently), there's no guidance on verifying actions succeeded or error recovery patterns. | 2 / 3 |
Progressive Disclosure | Well-organized with clear sections (Features, Quickstart, Examples), but everything is in one file. The extensive feature list and many examples could benefit from splitting into separate reference files, with SKILL.md as a concise overview. | 2 / 3 |
Total | 10 / 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 | |
50ef2f3
Table of Contents
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.