CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

71

Quality

88%

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

92%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 content is a well-organized, lean reference for a simple skill: concrete executable examples, a clear parameters table, and clean sectioning with no padding beyond minor trigger restatement. It fully satisfies the simple-skill exceptions for workflow clarity and progressive disclosure.

Suggestions

Trim or repurpose the 'Use Cases' section so it does not restate the frontmatter's trigger phrases verbatim, raising conciseness toward 5.

DimensionReasoningScore

Conciseness

The body is lean with no concept explanations or fluff, but the 'Use Cases' bullets ('等待对话框打开', '等待加载完成', '在下一步操作前同步应用状态') largely restate triggers already in the frontmatter description, a minor instance of content that could be trimmed.

4 / 5

Actionability

Provides copy-paste-ready JSON examples covering both target types and a custom timeout ('{"target": "另存为", "target_type": "window"}', '{"target": "确定按钮", "timeout": 5}') alongside a parameters table with types and required flags, covering the common cases.

5 / 5

Workflow Clarity

A simple single-purpose skill whose single action (wait) is unambiguous: parameters, target types, examples, and return values are all clearly specified, satisfying the simple-skill exception for a top score.

5 / 5

Progressive Disclosure

Under 50 lines with no need for external references, organized into clear sections (Parameters, Target Types, Use Cases, Examples, Returns, Related Skills) with easy navigation, satisfying the simple-skill exception.

5 / 5

Total

19

/

20

Passed

Description

83%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 strong: it concisely pairs a clear capability statement with an explicit trigger clause and a concrete default, making it highly complete and actionable. Specificity and trigger coverage are solid but not maximal, and there is minor overlap risk with closely related desktop skills.

Suggestions

Add one or two natural trigger synonyms (e.g., 'spinner', 'progress indicator', 'page load') to broaden trigger_term_quality toward 5.

Tighten 'synchronize with application state before next action' to a more distinctive phrasing to reduce overlap with sibling desktop skills.

DimensionReasoningScore

Specificity

Lists several concrete wait scenarios ('wait for dialog to open, loading to complete, or synchronize with application state') plus a concrete default ('Default timeout is 10 seconds'), but all are variants of the single wait function rather than comprehensive coverage of distinct actions.

4 / 5

Completeness

Clearly states the 'what' ('Wait for UI element or window to appear') and an explicit 'when' clause ('When you need to wait for dialog to open, loading to complete, or synchronize with application state before next action') with concrete trigger phrases, plus a default timeout.

5 / 5

Trigger Term Quality

Natural user phrases are present ('wait for dialog to open', 'loading to complete', 'before next action'), giving good keyword coverage, though common synonyms like spinner, progress, or page load are absent.

4 / 5

Distinctiveness Conflict Risk

It carves a clear niche (desktop wait/synchronization) with distinct triggers, but 'synchronize with application state' and proximity to related desktop-click/desktop-find-element skills create minor overlap risk.

4 / 5

Total

17

/

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.

Validation15 / 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
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.