peekaboo

Capture and automate macOS UI with the Peekaboo CLI.

1.92x

Quality

43%

Does it follow best practices?

Impact

77%

1.92x

Average score across 3 eval scenarios

Securityby

Risky

Do not use without reviewing

Optimize this skill with Tessl

npx tessl skill review --optimize ./openclaw/skills/peekaboo/SKILL.md

Quality

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, like 'screenshot', 'screen capture', 'UI element', 'accessibility', 'desktop automation', 'peekaboo'.

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 reference-style skill with excellent actionability — the concrete bash examples cover a wide range of Peekaboo capabilities and are immediately usable. The main weaknesses are the verbose feature catalog that reads more like a man page than a skill, and the lack of validation/error-recovery steps in workflows, which is important for inherently fragile UI automation tasks.

Suggestions

Add validation checkpoints to workflows, e.g., after `peekaboo see`, verify expected elements exist in the JSON output before proceeding to click; include error recovery guidance for when elements aren't found.

Move the exhaustive Features list and detailed parameter references to a separate REFERENCE.md file, keeping SKILL.md focused on the quickstart, the see->click->type pattern, and the most common examples.

Add a brief troubleshooting/error-handling section covering common failure modes (permissions denied, element not found, stale snapshot IDs) with recovery steps.

Dimension	Reasoning	Score
Conciseness	The skill is fairly efficient and avoids explaining basic concepts, but the exhaustive listing of every CLI subcommand in the Features section is verbose — much of it could be discovered via `peekaboo --help`. The feature catalog adds bulk without proportional instructional value.	2 / 3
Actionability	The skill provides numerous concrete, copy-paste-ready bash commands covering the full range of use cases. Targeting parameters, flags, and real-world workflows (see -> click -> type) are all specific and executable.	3 / 3
Workflow Clarity	The 'See -> click -> type' flow is clearly sequenced and represents the most reliable pattern. However, there are no explicit validation/verification checkpoints (e.g., checking if `see` found the expected elements before clicking, or verifying a click succeeded). For UI automation — which is inherently fragile — feedback loops for error recovery are missing.	2 / 3
Progressive Disclosure	The content is organized into logical sections (Features, Quickstart, Parameters, Examples) which aids navigation. However, the extensive feature catalog and numerous examples make this a long monolithic file; the detailed command reference and advanced examples could be split into separate referenced files.	2 / 3
	Total	9 / 12 Passed

Validation

72%

Warnings & errors only

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: trpc-group/trpc-agent-go
Commit: af8bd5f

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

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.