AB clawdcursor
AI desktop agent — control any app on Windows/macOS from your OpenClaw agent. Send natural language tasks to the Clawd Cursor API and it handles everything: opening apps, clicking buttons, typing text, navigating browsers, filling forms. If you can click it, your agent can too.
As a process B 71/100 · Nearly there — weak spots: inputs and preconditions, consistency
The same skill appears in 1 more place: ClawHub
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: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- note
frontmatter-keyunknown frontmatter key "homepage" - note
frontmatter-keyunknown frontmatter key "source" - note
frontmatter-keyunknown frontmatter key "privacy" - note
frontmatter-keyunknown frontmatter key "notes"
Process rating: all ten parameters 71/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 40Consistency. Frontmatter name (clawdcursor) differs from the folder (clawd-cursor)
- 60Tools and files. Uses tools (bash, write, web, node) that frontmatter does not declare
- 60Result and completion. Output format stated, no completion criterion
- 100Steps. 46 steps
- 100When it triggers. States when to use and when not to
- 100Failures and branches. 5 branches, has a failure section
- 100Execution cost. Instruction body is 3873 tokens
- 100Running it twice. Mutating operations check current state
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 12 top-level sections: this looks like several domains in one skill
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
- -2localhost URLs: will not work for another user
- +1No license
- +2Single-language instructions
- +4Description says when NOT to use the skill
- +3Description length 278: enough signal without eating the budget
- +4Structure: 37 headings
- +3Step-by-step instructions: 46 items
- +3Output format is stated explicitly
- +4Has examples (14 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 86.