BD workday-music-greeter
On weekdays, automatically switch the home-music scene for the current time slot, fetch a matching GIF, and send a greeting email that embeds and attaches that GIF. Includes a cron installer for Mon–Fri scheduling. Use when the user wants automated workday music scene switching paired with themed greeting emails.
On weekdays, automatically switch the home-music scene for the current time slot, fetch a matching GIF, and send a greeting email that embeds and attaches…
As a process D 49/100 · Unfinished process — weak spots: result and completion, inputs and preconditions, failures and branches
What is at stake
Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.
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
- 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
✓ No critical or high findings
Medium and low: 5
-
medium Dangerous commands
cmd-persistenceinstall-cron.sh:29Persistence mechanism (cron / launchd / scheduled task / autorun registry) (string literal in code, not executed)current="$(crontab -l 2>/dev/null || true)"
code literal -
medium Dangerous commands
cmd-persistenceinstall-cron.sh:31Persistence mechanism (cron / launchd / scheduled task / autorun registry) (detector / deny-list definition)printf '%s\n%s\n' "$cleaned" "$BLOCK" | sed '/^$/N;/^\n$/D' | crontab -
detector -
low Dangerous commands
cmd-cron-mentioninstall-cron.sh:29Mentions editing / listing crontab (string literal in code, not executed)current="$(crontab -l 2>/dev/null || true)"
code literal -
low Dangerous commands
cmd-cron-mentioninstall-cron.sh:32Mentions editing / listing crontab (detector / deny-list definition; string literal in code, not executed)echo "Installed weekday cron entries. View with: crontab -l"
detectorcode literal -
low Exfiltration
read-dotenvSKILL.md:43Reads a .env filecp .env.example .env && $EDITOR .env # set WMG_MAIL_TO + SMTP_* creds
Files scanned: 4. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- note
frontmatter-keyunknown frontmatter key "triggers"
Process rating: all ten parameters 49/100
- 0Result and completion. Does not say what the result is
- 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. 4 mutating operations with no state check
- 60Tools and files. Uses tools (bash) that frontmatter does not declare
- 70When it triggers. States when to use, but not when not to
- 100Steps. 7 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 732 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)
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +3Description length 314: enough signal without eating the budget
- +4Structure: 7 headings
- +3Step-by-step instructions: 7 items
- +4Has examples (3 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 83.