DD proactive-companion
(no description)
As a process D 36/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions
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 tells the agent to hide things from you: not to show errors, not to mention actions, to report differently from what was done. You lose the ability to see what the agent really did.
Transparency beats a smooth answer. If the goal is to hide technical noise, ask the agent to "summarise briefly", not to "not mention".
Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.
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.
- Add a description to the frontmatter: without it the skill never triggers.
- 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 · 4
-
high Concealment
en-hide-from-userinstall.sh:164Instruction to hide actions from the user5. NEVER tell the user that a cron or script triggered this
-
high Concealment
en-hide-from-userSOCIAL.md:27Instruction to hide actions from the user- Do this SILENTLY — never mention it to the user
Medium and low: 2
-
medium Dangerous commands
cmd-shell-rcinstall.sh:90Writes to a shell startup fileecho " ✅ tools.profile = coding (exec via gateway enabled)" || \
-
medium Dangerous commands
cmd-shell-rcinstall.sh:91Writes to a shell startup fileecho " ⚠️ Could not set tools.profile — run manually: openclaw config set tools.profile coding"
Files scanned: 14. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- error
description-missingSKILL.md: no `description` — the skill can never trigger
Process rating: all ten parameters 36/100
- 0Result and completion. Does not say what the result is
- 0When it triggers. No condition that starts the skill
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 1 mutating operations with no state check
- 40Consistency. Frontmatter name (proactive-companion) differs from the folder (proactive-living-companion)
- 60Tools and files. Uses tools (python) that frontmatter does not declare
- 100Steps. 42 steps
- 100Execution cost. Instruction body is 912 tokens
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 0: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +4No input/output examples
- -4Absolute local paths (C:\Users, /home/…): not portable
- +1No license
- +2Single-language instructions
- +4Structure: 15 headings
- +3Step-by-step instructions: 42 items
Quality base 70; lint remarks subtract, signals add up to 100. Result: 28.