CtrlK
BlogDocsLog inGet started
Tessl Logo

peekaboo

Capture and automate macOS UI with the Peekaboo CLI.

73

1.92x
Quality

68%

Does it follow best practices?

Impact

77%

1.92x

Average score across 3 eval scenarios

SecuritybySnyk

High

Do not use without reviewing

Fix and improve this skill with Tessl

tessl review fix ./openclaw/skills/peekaboo/SKILL.md

The canonical home for this skill is peekaboo in Hung-Reo/hungreo-openclaw

SKILL.md
Quality
Evals
Security

Quality

Content

82%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a lean, highly actionable command catalog with copy-paste examples and a sensible see-then-act workflow, organized into clear sections. It loses points only on minor conciseness trims and the absence of explicit post-action validation and external reference splitting.

DimensionReasoningScore

Conciseness

Commands are listed as terse one-line bullets with executable examples and almost no concept explanation, but a few soft touches (e.g. 'Tip: run via polter peekaboo', the 'most reliable flow' label) could be trimmed, matching 'efficient; minor instances of over-explanation' rather than the perfectly-lean anchor at 5.

4 / 5

Actionability

Examples are fully executable, copy-paste ready commands with real flags and arguments covering the common cases (see/click/type, capture, window/menu management, input), directly matching the 'fully executable; specific examples cover the common cases' anchor.

5 / 5

Workflow Clarity

The 'See -> click -> type' flow shows a clear sequence and embeds a verification checkpoint via 'see --annotate' to identify targets before acting, but there are no explicit validate/verify-after steps, so it sits at 'clear sequence with most checkpoints; minor validation gaps' rather than the explicit-feedback-loop anchor at 5.

4 / 5

Progressive Disclosure

Content is organized into well-labeled sections (Features, Quickstart, Common parameters, Examples, Notes) and is self-contained with no nested references, but at ~165 lines the command catalog could plausibly live in a separate reference file, fitting 'good structure; minor organization gaps' rather than the cleanly-split anchor at 5.

4 / 5

Total

17

/

20

Passed

Description

53%Weight 40%Scale 1-5

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 concise and specific to a clear niche (macOS UI automation via Peekaboo), but it omits any 'when to use' trigger guidance and lacks natural keyword synonyms, which limits its discoverability and completeness scores.

Suggestions

Add an explicit trigger clause, e.g. 'Use when automating macOS UI, taking screenshots, or driving clicks/typing on a Mac.'

Expand keywords to include natural user terms like 'screenshot', 'click', 'screen recording', and 'UI automation'.

Replace the generic 'automate' with concrete actions (e.g. 'click, type, and drive windows/menus') to lift specificity.

DimensionReasoningScore

Specificity

Names the domain ('macOS UI') and two actions ('Capture and automate'), but 'automate' is generic, so coverage is not comprehensive — matching the '1-2 concrete actions' anchor rather than the several-specific-actions anchor above.

3 / 5

Completeness

Provides a clear 'what' but has no 'Use when...' or equivalent trigger guidance; per the rubric guideline a missing explicit trigger clause caps completeness at 3, and it is not vague enough to drop to 2.

3 / 5

Trigger Term Quality

Includes relevant terms ('macOS UI', 'capture', 'automate', 'Peekaboo CLI') but misses common natural synonyms users would say like 'screenshot', 'click', 'screen recording', or 'UI automation', placing it at 'some relevant keywords but missing variations'.

3 / 5

Distinctiveness Conflict Risk

The pairing of a specific platform ('macOS UI') with a named tool ('Peekaboo CLI') carves a distinct niche with only minor overlap risk against general screenshot/automation skills, fitting 'mostly distinct' rather than the fully-distinct anchor at 5.

4 / 5

Total

13

/

20

Passed

Validation

81%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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

13

/

16

Passed

Repository
trpc-group/trpc-agent-go
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.