CtrlK
BlogDocsLog inGet started
Tessl Logo

peekaboo

Capture and automate macOS UI with the Peekaboo CLI.

73

1.92x
Quality

Does it follow best practices?

Impact

77%

1.92x

Average score across 3 eval scenarios

SecuritybySnyk

Risky

Do not use without reviewing

SKILL.md
Quality
Evals
Security

Quality

Content

80%

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

The content is lean and highly actionable, with copy-paste CLI examples and well-organized sections. Its weaknesses are the absence of explicit validation feedback loops in workflows and a monolithic structure that does not leverage progressive disclosure via bundle files.

Suggestions

Add an explicit verify/retry checkpoint to the primary workflow, e.g. re-run "peekaboo see --annotate" after acting to confirm the target state before proceeding.

Move the full per-command flag reference into a bundled REFERENCE.md and keep SKILL.md as a concise overview pointing to it, enabling one-level-deep progressive disclosure.

Add a brief troubleshooting/validation note for when a click or type fails to land (e.g. re-snapshot and re-target by ID).

DimensionReasoningScore

Conciseness

The body avoids explaining concepts Claude already knows and is a dense, command-and-example reference where nearly every line is actionable; no padded introductory prose is present.

3 / 3

Actionability

Commands such as "peekaboo see --annotate --path /tmp/peekaboo-see.png" and "peekaboo click --on B1" are concrete, executable, and copy-paste ready across many scenarios.

3 / 3

Workflow Clarity

Sequences like see→click→type are shown and the Notes suggest using "see --annotate" to identify targets before clicking, but there are no explicit validation checkpoints or error-recovery feedback loops for the multi-step flows.

2 / 3

Progressive Disclosure

The ~190-line body is well-sectioned (Features, Quickstart, Common parameters, Examples) but is a single monolithic file with no bundle references; the full command catalog could be split into referenced files for one-level-deep navigation.

2 / 3

Total

10

/

12

Passed

Description

57%

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 specific and distinctive but reads as a terse tagline: it states what the tool does without explicit trigger guidance or a broader set of concrete action keywords. Adding a "Use when..." clause and more natural trigger terms would raise completeness and trigger-term quality.

Suggestions

Add an explicit trigger clause, e.g. "Use when automating macOS UI: capturing screenshots, clicking elements, typing text, or driving menus/windows."

Expand the action list beyond "capture" and "automate" to concrete verbs users would say (screenshot, click, type, hotkey, menu, window management).

Include natural keyword variants like "macOS UI automation", "screenshots", and "click/type" to improve trigger-term coverage.

DimensionReasoningScore

Specificity

"Capture and automate macOS UI" names the domain and two actions but does not list multiple specific concrete actions like screenshot, click, type, or menu control, so it is not comprehensive enough for a 3.

2 / 3

Completeness

It clearly states what the skill does, but there is no "Use when..." clause or equivalent explicit trigger guidance, which caps completeness at 2 per the rubric guideline.

2 / 3

Trigger Term Quality

"macOS UI", "capture", and "automate" are relevant keywords, but common natural variations a user would say (screenshots, click, UI automation, menubar) are missing.

2 / 3

Distinctiveness Conflict Risk

"Capture and automate macOS UI with the Peekaboo CLI" carves out a clear niche tied to a specific CLI on a specific OS, making conflict with other skills unlikely.

3 / 3

Total

9

/

12

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.