AD desktop-automation-pro
Desktop GUI automation toolkit for browser, mobile devices, and native applications. 桌面 GUI 自动化工具包,支持浏览器、移动设备和原生应用。 Use this skill when: 使用此技能的场景: - Automating web browsers (Chromium-based) - 控制 Chromium 浏览器 - Controlling paired mobile devices (Android/iOS/macOS) - 控制配对的移动设备 - Taking screenshots of desktop/windows/regions - 桌面/窗口/区域截图 - Automating Windows native applications via Python - 通过 Python 自动化 Windows 原生应用 - Mouse/keyboard simulation - 鼠标键盘模拟 Triggers: 桌面自动化, GUI自动化, 浏览器自动化, 手机控制, 截图, desktop automation, GUI automation, browser automation, mobile control, screenshot, pyautogui, pywinauto
As a process D 46/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions
How to improve
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 4. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 46/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 40Consistency. Frontmatter name (desktop-automation-pro) differs from the folder (desktop-automation-pro-systiger)
- 50Failures and branches. 0 branches, has a failure section
- 60Tools and files. Uses tools (bash, python) that frontmatter does not declare
- 100Steps. 9 steps
- 100Execution cost. Instruction body is 1327 tokens
- 100Running it twice. No mutating operations
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +3Description length 604: enough signal without eating the budget
- +4Structure: 16 headings
- +3Step-by-step instructions: 9 items
- +4Has examples (6 code blocks)
- +3All 2 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 87.