CC yt2gdrive
Sync latest audio or video (mp3/mp4) from YouTube channels to Google Drive.
Sync latest audio or video (mp3/mp4) from YouTube channels to Google Drive.
As a process C 53/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.
- 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 · 4
-
high Dangerous commands
cmd-persistencescripts/install_launchd.sh:51Persistence mechanism (cron / launchd / scheduled task / autorun registry)launchctl load "$PLIST"
Medium and low: 3
-
medium Dangerous commands
cmd-persistenceREADME.md:81Persistence mechanism (cron / launchd / scheduled task / autorun registry) (quoted — discussed, not commanded)- 停用定时任务：`launchctl unload ~/Library/LaunchAgents/com.…ist`
quoted -
medium Dangerous commands
cmd-persistencescripts/install_launchd.sh:5Persistence mechanism (cron / launchd / scheduled task / autorun registry) (code comment)# 卸载: launchctl unload ~/Library/LaunchAgents/com.…ist
comment -
medium Dangerous commands
cmd-persistencescripts/install_launchd.sh:12Persistence mechanism (cron / launchd / scheduled task / autorun registry) (string literal in code, not executed)PLIST="$HOME/Library/LaunchAgents/com.…ist"
code literal
Files scanned: 5. 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 53/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
- 50Failures and branches. 0 branches, has a failure section
- 60Tools and files. Uses tools (bash) that frontmatter does not declare
- 100Steps. 52 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 852 tokens
- 100Running it twice. No mutating operations
- 100Progress reporting. Reports progress
- low 10 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
- +4Description does not say when NOT to use the skill (false activations)
- +3Description length 75: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +4Structure: 12 headings
- +3Step-by-step instructions: 52 items
- +3All 2 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 68.