BC macos-cleaner
Diagnoses and safely reclaims macOS disk space: caches, logs, app remnants, large/duplicate files, Docker/OrbStack, Chromium code-sign clones, developer caches. Use when a Mac is low on storage, shows “Caching needs more space”, or before deleting anything to avoid data loss. Not for Windows/Linux or permission issues (use macos-permissions).
Diagnoses and safely reclaims macOS disk space: caches, logs, app remnants, large/duplicate files, Docker/OrbStack, Chromium code-sign clones, developer caches.
As a process C 61/100 · Has gaps — weak spots: result and completion, inputs and preconditions, execution cost
How to improve
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
- 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 · 2
✓ No critical or high findings
Medium and low: 2
-
low Dangerous commands
cmd-privilegescripts/check_gate_plan.py:364Privilege escalation / world-writable permissions (detector / deny-list definition; string literal in code, not executed; code comment)# - anchored to a leading `mv` (so `git mv`, `sudo mv`, and an `mv` after
detectorcode literalcomment -
low Dangerous commands
cmd-privilegeSKILL.md:253Privilege escalation / world-writable permissions (security demo / example; quoted — discussed, not commanded)The same-volume fallback is a quarantine move, not Trash: `mv` each exact approved target to a directory on the same volume (`<approved-dir>/_quarantine-<date>/`), writing a MANIFEST (original path, s
demoquoted
Files scanned: 25. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
body-longSKILL.md body ≈ 10431 tokens (recommended < 5000); move details to references/ - note
edit-residuethe text marks something as outdated (lines 32, 213, 247, 301): check that old rules are not kept next to new ones — the full check reads the text for contradictions
Process rating: all ten parameters 61/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 30Running it twice. 14 mutating operations with no state check
- 40Result and completion. Does not say what the result is
- 40Execution cost. Instruction body is 10431 tokens: crowds the task out of the window
- 50When it triggers. No condition that starts the skill
- 60Tools and files. Uses tools (bash, python) that frontmatter does not declare
- 100Steps. 83 steps
- 100Failures and branches. 3 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
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
- +3Output format is not stated: the model decides each time
- -32 of 13 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +4Description says when NOT to use the skill
- +3Description length 344: enough signal without eating the budget
- +4Structure: 16 headings
- +3Step-by-step instructions: 83 items
- +4Has examples (7 code blocks)
- +4Reference files are cited in the instructions (11 of 11)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 79.