BC toolguard-daemon-control
Manage long-running processes as macOS launchd services. Use when asked to start, stop, restart, check status of, or manage background services/daemons. Handles launchd plist creation, service lifecycle, and log access. Use this instead of background exec for any process that should persist beyond the current session.
Manage long-running processes as macOS launchd services.
As a process C 50/100 · Has gaps — 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 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.
- 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-persistencescripts/install.sh:119Persistence mechanism (cron / launchd / scheduled task / autorun registry)launchctl load "$PLIST_PATH"
Medium and low: 4
-
low Dangerous commands
cmd-persistencescripts/status.sh:9Persistence mechanism (cron / launchd / scheduled task / autorun registry) (detector / deny-list definition; string literal in code, not executed)PLIST_PATH="$HOME/Library/LaunchAgents/${LABEL}.plist"detectorcode literal -
low Dangerous commands
cmd-persistencescripts/uninstall.sh:11Persistence mechanism (cron / launchd / scheduled task / autorun registry) (detector / deny-list definition; string literal in code, not executed)PLIST_PATH="$HOME/Library/LaunchAgents/${LABEL}.plist"detectorcode literal
A further 2 matches are quotations in this security skill's documentation and are not counted as findings.
Files scanned: 6. 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 50/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 3 mutating operations with no state check
- 50Failures and branches. 0 branches, has a failure section
- 60Tools and files. Uses tools (bash) that frontmatter does not declare
- 100Steps. 10 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 552 tokens
- 100Progress reporting. Reports progress
- low The response is described with custom markup (4 tags): a typed call is more reliable
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 319: enough signal without eating the budget
- +4Structure: 9 headings
- +3Step-by-step instructions: 10 items
- +4Has examples (6 code blocks)
- +3All 5 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 87.