DC desktop-control
Control the desktop via CUA computer server API running on port 8000
As a process C 59/100 · Has gaps — weak spots: result and completion, when it triggers, consistency
What is at stake
The skill contains fragments that, in the wrong hands, cost money or data. Below: what the installer risks and what the author should do.
The skill contains commands that delete files, rewrite disks or execute code fetched from the network. The agent may run them without asking if it believes the instructions require it.
Replace destructive commands with safe equivalents that ask for confirmation, scope them to one folder, and stop piping curl into a shell: pin a version and a checksum.
How to improve
- Address the high-severity findings: each costs 18 safety points. If one is a false positive, add the rule id to guard.allow in spec.yaml.
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- 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 · 5
-
high Dangerous commands
cmd-persistenceSKILL.md:61Persistence mechanism (cron / launchd / scheduled task / autorun registry)cat > ~/Library/LaunchAgents/com.cua.server.plist <<EOF
-
high Dangerous commands
cmd-persistenceSKILL.md:84Persistence mechanism (cron / launchd / scheduled task / autorun registry)launchctl load ~/Library/LaunchAgents/com.cua.server.plist
-
high Dangerous commands
cmd-persistenceSKILL.md:128Persistence mechanism (cron / launchd / scheduled task / autorun registry)Register-ScheduledTask -TaskName "CUA Server" -Action $action -Trigger $trigger -Principal $principal -Settings $settings
Medium and low: 2
-
medium Dangerous commands
cmd-privilegeSKILL.md:93Privilege escalation / world-writable permissionssudo tee /etc/systemd/system/cua-server.service > /dev/null <<EOF
-
low Dangerous commands
cmd-background-processSKILL.md:113Starts a background / autostarted processsudo systemctl enable cua-server
Files scanned: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when")
Process rating: all ten parameters 59/100
- 0Result and completion. Does not say what the result is
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 40Consistency. Frontmatter name (desktop-control) differs from the folder (desktop-automation)
- 60Tools and files. Uses tools (web, python) that frontmatter does not declare
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 14 steps
- 100Failures and branches. 1 branches, has a failure section
- 100Execution cost. Instruction body is 3633 tokens
- 100Running it twice. No mutating operations
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
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)
- +3Description length 68: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- -4Absolute local paths (C:\Users, /home/…): not portable
- -2localhost URLs: will not work for another user
- +1No license
- +2Single-language instructions
- +4Structure: 37 headings
- +3Step-by-step instructions: 14 items
- +4Has examples (33 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 63.