CtrlK
BlogDocsLog inGet started
Tessl Logo

1k-ui-verify

Drive OneKey desktop or mobile apps to verify real visual and interactive behavior using CDP/Playwright or agent-device. Use for UI 验证 or screenshot confirmation.

67

Quality

82%

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.

An action-dense, well-structured skill body with copy-paste commands for both platforms and properly delegated detail files. The only meaningful improvement is making the workflow's validation feedback loop explicit rather than implied.

Suggestions

Promote the validation loop into an explicit step: after capturing AFTER, state 'Compare to BEFORE; if behavior unchanged, diagnose and re-run' to formalize the feedback loop.

Trim the inline gotchas paragraphs (e.g. the perf-overlay note) into a one-line pointer to the rule file to tighten conciseness.

DimensionReasoningScore

Conciseness

Lean and efficient with no padding of basic concepts; each section (decision table, recipes, regression scenarios) earns its place. Minor over-explanation in the gotchas blocks keeps it just below anchor 5.

4 / 5

Actionability

Fully executable, copy-paste-ready commands for both backends (node ...cdp-shot.mjs, agent-device click 'id=...', yarn app:desktop) covering the common desktop and RN cases.

5 / 5

Workflow Clarity

A numbered checklist with a clear evidence gate in step 6 ('do not claim fixed without screenshot') and BEFORE/AFTER comparison; not a 5 because validation checkpoints are implicit rather than formal feedback-loop steps.

4 / 5

Progressive Disclosure

Body is a clear overview with well-signaled one-level-deep references to real bundle files (references/rules/electron-cdp.md, references/rules/agent-device-rn.md, scripts/cdp-shot.mjs); content is appropriately split and easy to navigate.

5 / 5

Total

18

/

20

Passed

Description

78%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 concise, well-targeted description that answers both what and when with explicit trigger guidance and a distinct OneKey-specific niche. The main gap is trigger-term breadth — a few common natural phrasings are missing.

Suggestions

Broaden the 'Use for...' clause with a few more natural synonyms users would say, e.g. 'visual bug', 'check the screen', 'does the UI look right', alongside 'UI 验证' and 'screenshot confirmation'.

List one or two more concrete actions (e.g. 'capture before/after screenshots', 'click by testID') to push specificity toward comprehensive coverage.

DimensionReasoningScore

Specificity

Names the OneKey desktop/mobile UI-verification domain with concrete actions ('verify real visual and interactive behavior', 'screenshot confirmation') and tools (CDP/Playwright, agent-device), but does not enumerate a broad set of distinct actions, so it sits at anchor 4 rather than 5.

4 / 5

Completeness

Explicitly answers both what (drive the app to verify visual/interactive behavior) and when ('Use for UI 验证 or screenshot confirmation'); the trigger is explicit but narrower than the anchor-5 example, so it fits anchor 4.

4 / 5

Trigger Term Quality

Includes natural trigger terms ('verify', 'screenshot confirmation', bilingual 'UI 验证') plus an explicit 'Use for' clause, but misses common synonyms a user might say like 'visual bug' or 'check the screen', keeping it just below comprehensive.

4 / 5

Distinctiveness Conflict Risk

Scoped tightly to OneKey apps via CDP/agent-device, a clear niche with distinct triggers and minimal overlap with other skills.

5 / 5

Total

17

/

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.