peekaboo
Capture and automate macOS UI with the Peekaboo CLI.
70
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
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 brief to be effective for skill selection. It lacks specific capabilities, natural trigger terms users would say, and critically missing explicit 'when to use' guidance. The mention of 'Peekaboo CLI' provides some distinctiveness but overall the description needs significant expansion.
Suggestions
Add a 'Use when...' clause specifying triggers like 'when user asks for screenshots, screen capture, UI automation on Mac, or mentions Peekaboo'
List specific concrete actions such as 'take screenshots, capture window contents, automate clicks and keystrokes, read UI element text'
Include natural user terms like 'screenshot', 'screen capture', 'Mac automation', 'click automation', 'window capture'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (macOS UI) and mentions two actions (capture, automate), but lacks specific concrete actions like 'take screenshots', 'click buttons', 'read window contents', or 'record interactions'. | 2 / 3 |
Completeness | Describes what at a high level 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', 'UI automation', 'click', 'window', or 'Mac automation'. | 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
87%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 skill that efficiently documents a comprehensive CLI tool. It excels at conciseness and actionability with dense, executable examples. The main weakness is the lack of explicit validation/error handling guidance for UI automation workflows, which are inherently fragile.
Suggestions
Add validation checkpoints to the 'See -> click -> type' workflow (e.g., 'verify element exists before clicking', 'check for error dialogs after actions')
Include a brief troubleshooting section or error recovery pattern for common failures (element not found, app not responding, permission denied)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely lean and efficient - no explanations of what macOS is or how CLIs work. Every section is dense with actionable flags and commands, assuming Claude's competence throughout. | 3 / 3 |
Actionability | Fully executable bash commands throughout with specific flags, real examples, and copy-paste ready code. The examples section covers diverse use cases with complete, runnable commands. | 3 / 3 |
Workflow Clarity | The 'See -> click -> type' flow shows a clear sequence, but lacks explicit validation checkpoints. No feedback loops for error recovery when clicks fail or elements aren't found, which is important for UI automation. | 2 / 3 |
Progressive Disclosure | Well-organized with clear sections (Features, Quickstart, Parameters, Examples). Content is appropriately structured for a single-file skill with logical groupings and the tip to use '--help' for deeper exploration. | 3 / 3 |
Total | 11 / 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 | |
- 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.