CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

desktop-wait

Wait for UI element or window to appear. When you need to wait for dialog to open, loading to complete, or synchronize with application state before next action. Default timeout is 10 seconds.

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

85%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.

A tight, well-structured reference for a simple single-action tool: a typed parameter table, concrete JSON examples, and clearly labeled sections with zero padding. Its only weaknesses are mild redundancy between sections and a vague Returns description that leaves the timeout-failure outcome unspecified.

DimensionReasoningScore

Conciseness

The body is lean — a typed parameter table and two short JSON examples with no explanation of concepts Claude already knows — but the "Target Types" section restates the target_type parameter row and "Use Cases" repeats the frontmatter description, so there are minor instances of redundancy that could be trimmed, matching the 4 anchor rather than the fully lean 5.

4 / 5

Actionability

Two copy-paste-ready JSON payloads ("{\"target\": \"另存为\", \"target_type\": \"window\"}" and "{\"target\": \"确定按钮\", \"timeout\": 5}") plus a complete parameter table give mostly executable guidance; it falls short of 5 because "Returns" is vague ("成功:元素/窗口信息") and there is no example of the timeout-failure output.

4 / 5

Workflow Clarity

This is a simple single-purpose skill and the single action is unambiguous: call desktop_wait with target, optional target_type (element default / window), and optional timeout with a stated default of 10. Per the simple-skill exception it scores 5, and no destructive or batch operations exist to require validation checkpoints.

5 / 5

Progressive Disclosure

The skill is under 50 lines with no need for external reference files, and the content is organized into clear sections (Parameters, Target Types, Use Cases, Examples, Returns, Related Skills); the Related Skills entries are sibling skill pointers, not nested file references, so per the under-50-line guideline it scores 5.

5 / 5

Total

18

/

20

Passed

Description

75%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.

A solid, concrete description that explicitly covers both what the skill does and when to use it, with natural trigger phrasing and a useful default timeout. It sits just below the top anchor because the when-clause echoes the what rather than broadening trigger coverage, and it lacks synonyms that would fully distinguish it from adjacent wait/sync skills.

Suggestions

Broaden the when-clause with distinct trigger phrases and synonyms, e.g., "Use when a dialog, popup, spinner, or loading indicator must appear before the next step, or when the app needs time to reach a ready state."

State the timeout behavior explicitly (e.g., what is returned or raised on timeout) so the what-portion is comprehensive rather than only naming the default.

Anchor distinctiveness by naming the desktop-automation context in the trigger clause (e.g., "during desktop UI automation") to reduce overlap with generic sleep/delay skills.

DimensionReasoningScore

Specificity

"wait for dialog to open, loading to complete, or synchronize with application state" names several concrete actions with a concrete default ("Default timeout is 10 seconds"), but coverage has minor gaps (no behavior on timeout or polling details), matching the 'several specific actions; minor gaps' anchor rather than the comprehensive 5.

4 / 5

Completeness

It has an explicit what ("Wait for UI element or window to appear") and an explicit when ("When you need to wait for dialog to open, loading to complete, or synchronize with application state before next action"). Not a 5 because the when-clause largely restates the what instead of adding distinct concrete trigger phrases; not a 3 because the when is explicit, not merely implied.

4 / 5

Trigger Term Quality

Natural phrases like "wait for dialog to open", "loading to complete", and "synchronize" match what users would say, giving good keyword coverage, but common synonyms (e.g., "spinner", "app ready", "sleep/delay") are missing, so it is not the comprehensive synonym coverage of a 5.

4 / 5

Distinctiveness Conflict Risk

"UI element or window" plus "dialog"/"application state" anchor it clearly to desktop UI automation, but generic terms like "wait" and "synchronize" leave minor overlap risk with closely related skills (e.g., generic sleep/delay or web-wait skills), matching the 'mostly distinct; minor overlap risk' anchor.

4 / 5

Total

16

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

openakita/openakita

Path

skills/system/desktop-wait/SKILL.md

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.