CtrlK
BlogDocsLog inGet started
Tessl Logo

host-computer-use-windows

Backend-specific Windows guidance for `computer_use_remote`. Load after `status` or `start_session` reports backend_family/backend_id `windows` or Windows UI Automation features. Covers UIA structural targeting, Windows session caveats, and screenshot verification.

69

Quality

84%

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

88%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 highly actionable, well-sequenced guide with executable JSON examples, explicit verification checkpoints, and error-recovery feedback loops. The only meaningful gap is progressive disclosure: the file is a single dense reference with no external split, which is acceptable but leaves it slightly above the ideal lean-overview pattern.

DimensionReasoningScore

Conciseness

Operational and dense with little padding — feature lists, copy-paste JSON, and action-selection rules assume Claude's competence; a few spots restate the background-first dispatch contract and could be tightened, fitting 'efficient; minor instances of over-explanation' rather than a fully lean 5.

4 / 5

Actionability

Provides copy-paste-ready JSON tool_args examples for element_action, uia_snapshot, and uia_action plus an enumerated operations list and concrete targeting options covering common cases, matching 'fully executable; copy-paste ready code; specific examples cover the common cases'.

5 / 5

Workflow Clarity

A clear numbered 'Preferred loop' (list_windows → get_window_state → element_action → fallback) with explicit verification ('inspect that image before saying the requested outcome happened') and error-recovery feedback loops (ambiguity/missing target → fresh snapshot; session errors → stop and ask user), matching the top anchor.

5 / 5

Progressive Disclosure

Well-organized into clear sections (UIA Targeting, Session Caveats, Geometry) with no nested references and no bundle files to mismanage; at ~110 lines it exceeds the 'under 50 lines' simple-skill exception, and the inline operations/targeting reference could arguably live in a separate file, so it lands at 'good structure; minor organization gaps' rather than 5.

4 / 5

Total

18

/

20

Passed

Description

80%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 strong, specific description that clearly states what it covers and when to load it, with a distinct Windows-backend niche. Its main weakness is trigger-term naturalness — the load conditions are phrased as internal API states rather than language a user would naturally say.

Suggestions

Add a couple of natural-language trigger phrases a user might actually say (e.g. 'Use when the user needs to drive a Windows desktop or automate a Windows app via computer_use_remote') alongside the backend-state triggers.

Include common synonyms/extensions (e.g. 'Windows desktop', 'UIA', 'Windows UI Automation') to broaden keyword coverage.

DimensionReasoningScore

Specificity

Names the domain and several concrete coverage areas ('UIA structural targeting, Windows session caveats, and screenshot verification'), matching the 'lists several specific actions; minor gaps' anchor; not a 5 because the actions are topical categories rather than a comprehensive enumerated action set.

4 / 5

Completeness

Explicitly answers both what ('Backend-specific Windows guidance... Covers UIA structural targeting, Windows session caveats, and screenshot verification') and when ('Load after status or start_session reports backend_family/backend_id windows or Windows UI Automation features') with concrete trigger phrases, matching the top anchor.

5 / 5

Trigger Term Quality

Includes relevant terms (Windows, UI Automation, computer_use_remote, screenshot) but the triggers are technical jargon ('backend_family/backend_id', 'status or start_session') rather than natural user phrasings, and common synonyms are missing; fits 'some relevant keywords but missing common variations'.

3 / 5

Distinctiveness Conflict Risk

A clear niche (the Windows backend of computer_use_remote) with distinct triggers and explicit non-targets implied by backend scoping; minimal conflict risk with other skills, matching the 'clear niche with distinct triggers' anchor.

5 / 5

Total

17

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
agent0ai/agent-zero
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.