DC macos-memory-triage
Diagnose why a Mac (especially one running Claude Code, other AI coding tools, or several Electron-based IDEs at once) is slow, hanging, or freezing due to memory pressure and swap thrashing. Covers reading real swap/memory numbers, finding MCP-server and plugin process bloat, spotting orphaned or duplicate background processes, safely clearing regenerable caches, and recognizing when a killed process keeps respawning because something else supervises it. Use this whenever the user says their Mac/MacBook is slow, laggy, hanging, freezing, "using too much memory," has "high memory pressure," or asks to find/stop/kill whatever is eating RAM or CPU. Every fix in this skill is reversible (stop, kill, disable, clear cache) — it never deletes or uninstalls anything, and it says so explicitly before running anything.
Diagnose why a Mac (especially one running Claude Code, other AI coding tools, or several Electron-based IDEs at once) is slow, hanging, or freezing due to…
As a process C 60/100 · Has gaps — weak spots: result and completion, inputs and preconditions, progress reporting
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 · 4
-
high Dangerous commands
cmd-persistenceSKILL.md:98Persistence mechanism (cron / launchd / scheduled task / autorun registry)launchctl unload ~/Library/LaunchAgents/<the-plist-file>.plist
-
high Dangerous commands
cmd-persistenceSKILL.md:100Persistence mechanism (cron / launchd / scheduled task / autorun registry)launchctl load ~/Library/LaunchAgents/<the-plist-file>.plist
Medium and low: 2
-
medium Dangerous commands
cmd-persistenceSKILL.md:96Persistence mechanism (cron / launchd / scheduled task / autorun registry) (quoted — discussed, not commanded)If it shows up, it likely has a launch agent plist under `~/Library/LaunchAgents/`. Unloading it stops the process *and* the auto-restart behavior, and it's fully reversible:
quoted -
medium Dangerous commands
cmd-persistenceSKILL.md:135Persistence mechanism (cron / launchd / scheduled task / autorun registry) (documentation table row)| Unload a launchd agent | Yes, with confirmation | Reversible via `launchctl load` |
table
Files scanned: 1. 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 60/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 60Tools and files. Uses tools (bash) that frontmatter does not declare
- 60Failures and branches. 2 branches
- 85Steps. 12 steps, 3 vague phrases
- 100When it triggers. States when to use and when not to
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2372 tokens
- 100Running it twice. Mutating operations check current state
- high The skill tells the model to perform an irreversible action with no human approval
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
- +4Description does not say when NOT to use the skill (false activations)
- +3Description length 821: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +5Description quotes 2 example trigger phrases
- +4Structure: 9 headings
- +3Step-by-step instructions: 12 items
- +4Has examples (10 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 86.