DC c-drive-safe-cleanup-skill
(no description)
As a process C 53/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
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
- 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 · 10
✓ No critical or high findings
Medium and low: 10
-
medium Dangerous commands
cmd-execpolicy-bypassREADME.md:32Runs PowerShell with execution policy bypassedpowershell -ExecutionPolicy Bypass -File ".\script\c-dr…ps1" -DryRun
-
medium Dangerous commands
cmd-execpolicy-bypassREADME.md:38Runs PowerShell with execution policy bypassedpowershell -ExecutionPolicy Bypass -File ".\script\c-dr…ps1"
-
medium Dangerous commands
cmd-execpolicy-bypassREADME.md:44Runs PowerShell with execution policy bypassedpowershell -ExecutionPolicy Bypass -File ".\script\c-dr…ps1" -LogOutputPath ".\tasks\evaluation-2026-04-22-c-disk-cleanup.md"
-
low Dangerous commands
cmd-execpolicy-bypassmeta.json:13Runs PowerShell with execution policy bypassed (quoted — discussed, not commanded)"cleanup": "powershell -ExecutionPolicy Bypass -File .\\script\\c-dr…ps1",
quoted -
low Dangerous commands
cmd-execpolicy-bypassmeta.json:14Runs PowerShell with execution policy bypassed (quoted — discussed, not commanded)"dry_run": "powershell -ExecutionPolicy Bypass -File .\\script\\c-dr…ps1 -DryRun"
quoted -
low Dangerous commands
cmd-execpolicy-bypassREADME.md:55Runs PowerShell with execution policy bypassed (quoted — discussed, not commanded)- `powershell -ExecutionPolicy Bypass -File ".\script\c-dr…ps1" -DryRun`
quoted -
low Dangerous commands
cmd-execpolicy-bypassREADME.md:57Runs PowerShell with execution policy bypassed (quoted — discussed, not commanded)- `powershell -ExecutionPolicy Bypass -File ".\script\c-dr…ps1"`
quoted -
low Dangerous commands
cmd-execpolicy-bypassskill.md:170Runs PowerShell with execution policy bypassed (quoted — discussed, not commanded)- `powershell -ExecutionPolicy Bypass -File ".\script\c-dr…ps1"`
quoted -
low Dangerous commands
cmd-execpolicy-bypassskill.md:172Runs PowerShell with execution policy bypassed (quoted — discussed, not commanded)- `powershell -ExecutionPolicy Bypass -File ".\script\c-dr…ps1" -DryRun`
quoted -
low Dangerous commands
cmd-execpolicy-bypassskill.md:174Runs PowerShell with execution policy bypassed (quoted — discussed, not commanded)- `powershell -ExecutionPolicy Bypass -File ".\script\c-dr…ps1" -LogOutputPath ".\tasks\evaluation-2026-04-22-c-disk-cleanup.md"`
quoted
Files scanned: 5. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- error
frontmatterSKILL.md: no YAML frontmatter block found - error
name-missingSKILL.md: frontmatter has no `name` - error
description-missingSKILL.md: no `description` — the skill can never trigger
Process rating: all ten parameters 53/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
- 100Tools and files. No external tools needed
- 100Steps. 79 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 961 tokens
- 100Running it twice. No mutating operations
- 100Progress reporting. Reports progress
- low 13 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 0: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +4Structure: 15 headings
- +3Step-by-step instructions: 79 items
- +4Has examples (1 code blocks)
- +4Reference files are cited in the instructions (1 of 1)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 0.