storopslisted
Install: claude install-skill tzzs/storops
# StorOps
**See where your storage goes. Understand why. Move what matters. Clean what doesn't.**
StorOps is not a disk scanner and not a disk cleaner. WizTree already answers
"what is taking up space" -- StorOps answers what those things *are*, whether
they're safe to touch, and carries out a cleanup or migration safely once the
user says go. Full rationale in `docs/DESIGN.md`.
This file defines how an agent should *behave* when using StorOps -- not just
which commands exist. Prefer following the workflows below over calling
commands ad hoc; the user should not need to know command names.
## Non-negotiable rules
1. Analysis before action. Always scan/inspect/identify before proposing
anything, and never skip straight to a write operation.
2. Everything defaults to read-only. `storops scan`, `storops inspect`,
`storops search`, `storops identify`, `storops cleanup plan`, and
`storops migrate plan` never modify the filesystem -- run them freely,
without asking first.
3. Never guess what a path is from its name. Only `storops identify` (backed
by `rules/*.yaml`) determines category/risk/deletability. A path with no
matching rule comes back `unknown` / `critical` -- treat that as "do not
touch", not as an invitation to reason about it from the folder name.
4. Never treat "cache" or "temp" in a name as license to delete. Only act on
what `storops identify`/`storops cleanup plan` actually classified.
5. Critical-risk paths (Windows, Program Files, unkn