CtrlK
BlogDocsLog inGet started
Tessl Logo

1k-ui-verify

AI-agent-driven UI verification for OneKey. Use to actually drive the running app and confirm a visual/interactive change works — Electron desktop via Chrome DevTools Protocol (CDP) on port 9222 with playwright-core, and React Native (iOS/Android) via callstack agent-device. Triggers on "verify the UI", "drive the app", "screenshot the change", "check it on desktop/simulator", "CDP 9222", "agent-device", "UI 验证", "跑一下看看", "截图确认".

72

Quality

90%

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

86%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 well-structured, highly actionable body that leans on concrete commands and one-level-deep references. It is tight and navigable; the only marginal improvements are trimming a few RN-recipe sentences and surfacing the RN wait-until-stable checkpoint in the main workflow.

Suggestions

Tighten the RN quick recipe prose (e.g. the perf-overlay sentence) since the full gotcha is already in agent-device-rn.md.

Add the 'wait ~10-13s and screenshot to confirm a stable screen' checkpoint into the main Workflow checklist so the RN timing gate is visible in the body, not only the reference.

DimensionReasoningScore

Conciseness

Lean and dense with no concept padding; it assumes Claude knows CDP/playwright/RN and every section earns its place, though a few explanatory sentences in the RN quick recipe could be tightened further.

4 / 5

Actionability

Copy-paste-ready bash commands for both backends with concrete testIDs, exact ports, and a parameterized regression runner covering the common desktop/web/RN cases.

5 / 5

Workflow Clarity

A numbered checklist with an explicit evidence gate ('capture AFTER screenshot', 'do not claim fixed without it') and an expected-vs-actual step; the wait-until-stable checkpoint lives in the referenced file rather than the body, leaving a minor gap.

4 / 5

Progressive Disclosure

Overview cleanly points to two real one-level-deep reference files (electron-cdp.md, agent-device-rn.md) that are clearly signaled and cover the detailed material; the bundled script keeps the body short.

5 / 5

Total

18

/

20

Passed

Description

95%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 with explicit what/when structure, rich natural trigger phrases including bilingual variants, and a clearly distinct niche. The only minor gap is that it lists backends rather than a comprehensive enumeration of discrete actions.

DimensionReasoningScore

Specificity

Names the domain and concrete actions ('drive the running app and confirm a visual/interactive change works') plus specific backends ('CDP on port 9222 with playwright-core', 'React Native via callstack agent-device'), but does not enumerate as many distinct discrete actions as a top anchor.

4 / 5

Completeness

Explicitly answers what it does ('AI-agent-driven UI verification ... drive the running app and confirm a visual/interactive change works' with two backends) and when to use it ('Triggers on ...').

5 / 5

Trigger Term Quality

Comprehensive natural triggers with synonyms and bilingual variants ('verify the UI', 'drive the app', 'screenshot the change', 'UI 验证', '跑一下看看', '截图确认') plus technical terms ('CDP 9222', 'agent-device').

5 / 5

Distinctiveness Conflict Risk

Highly niche and OneKey-specific with concrete ports/tools and a clear Electron-vs-RN split, giving distinct triggers and minimal conflict risk.

5 / 5

Total

19

/

20

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 4 deeper-than-1-level

Warning

referenced_paths_exist

Referenced path issues: 4 deeper-than-1-level

Warning

Total

14

/

16

Passed

Repository
OneKeyHQ/app-monorepo
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.