Agent skill

Storage Audit

by Mathews-Tom in Mathews-Tom/armory

Read-only disk-storage audit for a repository or workspace root.

MITAuto-check passedDevelopment

Install Storage Audit

skills CLI
$ npx skills add Mathews-Tom/armory --skill storage-audit -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install Mathews-Tom/armory storage-audit --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/Mathews-Tom/armory.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/storage-audit .claude/skills/storage-audit && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
storage-audit
GitHub stars
328
Token cost
~1.4k tokens
SKILL.md length
604 words
Files
7 (incl. scripts, references)
Skills in repo
80
Repo updated
First seen
Licence
MIT

At a glance

Read-only disk-storage audit for a repository or workspace root.

  • Works in 6 steps: Resolve scope. Use the user path. A… → Run strict audit. Execute bash… → Classify evidence. Explain… → …
  • : audit disk space
  • SKILL.md covers Reference Files, Workflow, Supported Operations and Error Handling, plus 1 more section
  • Runs Shell scripts from its folder; calls bash

What it does

Storage Audit is an agent skill from Mathews-Tom/armory. Read-only disk-storage audit for a repository or workspace root. Measures project footprints, identifies rebuildable dependencies, classifies local data and Git-protected paths, and reports project liveness without modifying files. Triggers on: "audit disk space", "storage audit", "find removable build artifacts", "which projects use the most space", "cleanup commands but do not run them", "analyze repository storage", "workspace disk cleanup". Use this skill when a developer needs evidence-backed storage…

Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 10 other files, including scripts and reference files (for example `evals/cases.yaml`, `references/classification-policy.md` and `references/report-schema.md`).

It sits in Development, covering Git workflow. It works with Git. The repository describes itself as: Curated, production-grade skills for AI coding agents. Battle-tested workflows for developers who use AI seriously. The licence is MIT.

When your agent uses it

  • : audit disk space
  • Find removable build artifacts
  • Which projects use the most space
  • Cleanup commands but do not run them

Example prompts

  • “audit disk space”
  • “storage audit”
  • “find removable build artifacts”
  • “/storage-audit”

Requirements

  • A Bash shell

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

  1. Resolve scope. Use the user path. A request covering all projects or subfolders is workspace scope even when the root contains a Git…
  2. Run strict audit. Execute bash scripts/storage-audit.sh audit --root "" --scope --strict --format json. A strict result captures candidate…
  3. Classify evidence. Explain cleanup-eligible rebuildable entries separately from derived-review, local-data, and Git-protected entries…
  4. Report liveness. Surface project type, nested-repository count, Git cleanliness, last commit date, process count, and registered-worktree…
  5. Give the next action. After a strict audit with cleanup-eligible candidates, request a concise explicit selection: render all for every…
  6. Render script after selection. For render all, run plan --root --scope --all. For a subset, bind every requested ID to its canonical path…

What it can do on your machine

Read from SKILL.md and the folder at commit 4594fb7. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 1 file in scripts/ (Shell), which the agent can run.

    Shell commands in SKILL.md call:

    • bash

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Storage Audit loads about 1.4k tokens when it runs, and up to ~3.1k if it reads all its reference files. Until then it costs about 148 tokens; SKILL.md has 604 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~148
When it runs · the whole SKILL.md, loaded when a task matches
~1.4k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~3.1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from Mathews-Tom/armory at commit 4594fb7, republished under its MIT licence (© Mathews-Tom). 604 words, ~1,404 tokens.

Download SKILL.mdSave it as .claude/skills/storage-audit/SKILL.md (or your agent's skills folder). This skill also uses 6 other files; get the full folder from GitHub.
name
storage-audit
description
Read-only disk-storage audit for a repository or workspace root. Measures project footprints, identifies rebuildable dependencies, classifies local data and Git-protected paths, and reports project liveness without modifying files. Triggers on: "audit disk space", "storage audit", "find removable build artifacts", "which projects use the most space", "cleanup commands but do not run them", "analyze repository storage", "workspace disk cleanup". Use this skill when a developer needs evidence-backed storage recovery recommendations but must retain control of every deletion.
metadata.version
0.6.0
metadata.category
development
metadata.tags
disk-usage, storage, cleanup, safety, git
metadata.difficulty
intermediate
metadata.phase
review

Storage Audit

Audits allocated disk space without changing the requested root, invoking a package manager, accessing the network, or executing a cleanup command. The bundled Bash script produces deterministic, machine-readable evidence; it renders a guarded cleanup script after the user explicitly selects current actionable candidates.

Reference Files

FileContentsLoad when
references/classification-policy.mdArtifact classes and required evidenceBefore interpreting candidates
references/safety-contract.mdNon-negotiable read-only and script-rendering rulesAlways
references/report-schema.mdJSON and Markdown output contractWhen rendering or consuming output

Workflow

  1. Resolve scope. Use the user path. A request covering all projects or subfolders is workspace scope even when the root contains a Git marker or package manifest; do not let auto collapse that request into one repository. Otherwise, auto treats a Git/manifest root as one repository. Workspace discovery inventories direct children plus nested Git repositories to depth five and accepts both .git/ directories and .git files used by linked worktrees. Keep top-level multi-repository folders as repository-container rows with a nested_repo_count; list each nested repository separately. Report a discovered Git marker that Git cannot open as invalid-repository, not as an ordinary directory. Never widen the scan above the user-supplied root.
  2. Run strict audit. Execute bash scripts/storage-audit.sh audit --root "<path>" --scope <resolved-scope> --strict --format json. A strict result captures candidate identity and evidence at scan time; status:"unstable" means only that aggregate allocation drifted during collection.
  3. Classify evidence. Explain cleanup-eligible rebuildable entries separately from derived-review, local-data, and Git-protected entries. A-### means actionable candidate; P-### means protected or review-required candidate. Never infer that an old commit means the project checkout is disposable.
  4. Report liveness. Surface project type, nested-repository count, Git cleanliness, last commit date, process count, and registered-worktree count. These are review signals, not deletion authorization.
  5. Give the next action. After a strict audit with cleanup-eligible candidates, request a concise explicit selection: render all for every actionable candidate from that audit, or render A-001, A-002 for a subset. Do not paste the complete candidate list or tell the user to rerun the audit because aggregate allocation drifted.
  6. Render script after selection. For render all, run plan --root <path> --scope <scope> --all. For a subset, bind every requested ID to its canonical path from the preceding report: --candidate A-001 --expected-path <canonical-path>. plan collects a fresh strict candidate snapshot and rejects an ID whose current path differs from the selected path, then prints one self-contained selected-target script. Do not save or invoke it.
Show full SKILL.md (210 more words)Show less

Supported Operations

RequestScript invocationResult
Audit a repositoryaudit --root <repo> --scope repo --strict --format markdownRepository footprint and classified artifacts
Audit a workspaceaudit --root <workspace> --scope workspace --strict --format jsonProject and nested-repository inventory
Fast inventoryaudit --root <path> --fast --format markdownInformational report; cleanup suppressed
Render cleanup scriptplan --root <path> --scope <scope> --all or plan --root <path> --candidate A-001 --expected-path <canonical-path>Preview-by-default Bash script; only the operator may invoke --execute

Error Handling

ConditionRequired response
Missing/unreadable path, filesystem root, symlink root, or control-character pathStop and report the exact unsafe input; do not approximate
Strict scan changes while measuringReport UNSTABLE_SNAPSHOT; explain that candidate evidence remains a strict point-in-time capture and may render a script for its current actionable candidates.
Candidate path changed since auditRefuse to render a subset script; the selected ID must still resolve to the audited canonical path
Running process associated with a projectReport it and retain the project for review
User asks to delete a source checkout or old projectRefuse direct cleanup; provide an archive-review checklist only

Output

Return: root, snapshot status, allocated KiB, project type and nested-repository count, project liveness rows, classified artifact rows, and exact evidence for every recommendation. A strict report with cleanup-eligible candidates ends with concise render all and subset-selection instructions. State No command executed. whenever rendering a cleanup script.

© Mathews-Tom, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 6 other files (scripts, references) in skills/storage-audit of Mathews-Tom/armory.

  • SKILL.md
  • evals/cases.yaml
  • references/classification-policy.md
  • references/report-schema.md
  • references/safety-contract.md
  • scripts/storage-audit.sh
  • tests/test-storage-audit.sh

Open the folder on GitHubat commit 4594fb7

Compare with similar skills

Storage Audit next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Storage Audit compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Storage Audit this skillMathews-Tom/armory328—~1.4kAutomated safety check: PassMIT
Finishing a Development Branchobra/superpowers297k5 repos~1.9kAutomated safety check: PassMIT
Code Design Rationale Investigatorcursor/plugins10k9 repos~2.6kAutomated safety check: PassNone
Contributor-First PR MergeHKUDS/OpenHarness16k1 repos~847Automated safety check: PassMIT
Migrate Internal Package into GhostTryGhost/Ghost56k—~3.8kAutomated safety check: PassMIT
Create Pull Requestcline/cline70k1 repos~1.6kAutomated safety check: PassApache-2.0

Similar skills

  • Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.

    297k GitHub starsUsed in 5 repos~1.9k tokens
    DevelopmentAuto-check passed
  • Official

    Digs into why code is shaped the way it is by checking git history, pull requests and connected tools in parallel, then reporting a cited read on the tradeoffs.

    10k GitHub starsUsed in 9 repos~2.6k tokens
    DevelopmentAuto-check passed
  • Merges external GitHub pull requests while keeping the original author credited, and fixes conflicts after the merge instead of rewriting the contribution.

    16k GitHub starsUsed in 1 repo~847 tokens
    DevelopmentAuto-check passed
  • Moves a package from another TryGhost repository into Ghost as an internal workspace package while keeping its Git history, with checkpoints for the steps that need an administrator.

    56k GitHub stars~3.8k tokensUpdated today
    DevelopmentAuto-check passed
  • Opens a GitHub pull request from your current branch with the gh CLI, after reviewing the commits and diff and gathering the details the PR needs.

    70k GitHub starsUsed in 1 repo~1.6k tokens
    DevelopmentAuto-check passed
  • Git Merge Conflict Resolver

    tailcallhq/forgecode

    Resolves Git merge conflicts with a plan-first workflow that keeps both sides' intent, regenerates lock files and backs up deleted-but-modified files.

    7.6k GitHub starsUsed in 1 repo~4.5k tokens
    DevelopmentAuto-check passed

More from Mathews-Tom/armory

All 80 skills in this repo
  • Architecture Reviewer

    Mathews-Tom/armory

    Architecture reviews across 7 dimensions (structural, scalability, enterprise readiness, performance, security, ops, data) with scored reports.

    328 GitHub stars~4.6k tokensUpdated 3 days ago
    Auto-check passed
  • Concept To Image

    Mathews-Tom/armory

    Turn concepts into static HTML visuals exported as PNG or SVG files via HTML/CSS/SVG.

    328 GitHub stars~2.6k tokensUpdated 3 days ago
    Auto-check passed
  • Watch

    Mathews-Tom/armory

    A skill your agent uses when analyzing an existing video URL or local recording: "watch this video", "analyze youtube video", "summarize this video", "youtube transcript", "find this moment", "what…

    328 GitHub stars~2.8k tokensUpdated 3 days ago
    Auto-check passed
  • Code Refiner

    Mathews-Tom/armory

    Deep code simplification and refactoring preserving behavior across Python, Go, TypeScript, Rust.

    328 GitHub stars~3.1k tokensUpdated 3 days ago
    Auto-check passed
  • Concept To Video

    Mathews-Tom/armory

    Turn concepts into animated explainer videos using Manim (Python) with MP4/GIF output, audio overlay, multi-scene composition.

    328 GitHub stars~4.9k tokensUpdated 3 days ago
    Auto-check passed
  • Decision Map

    Mathews-Tom/armory

    Maps the unresolved architecture, policy, and scope decisions that must be answered before planning can start: one durable decision ticket per question on the issue tracker, typed and blocker-linked…

    328 GitHub stars~2.7k tokensUpdated 3 days ago
    Auto-check passed

Works with

Categories

Questions about Storage Audit

What does Storage Audit do?

Read-only disk-storage audit for a repository or workspace root. Storage Audit is an agent skill from Mathews-Tom/armory. Read-only disk-storage audit for a repository or workspace root.

When should I use Storage Audit?

Storage Audit fits situations like: : audit disk space; find removable build artifacts; which projects use the most space; cleanup commands but do not run them.

How do I install Storage Audit in Claude Code?

Run `npx skills add Mathews-Tom/armory --skill storage-audit -a claude-code`. Or copy the skill folder (skills/storage-audit in Mathews-Tom/armory) into .claude/skills/storage-audit in your project. Claude Code loads it when a task matches its description.

How do I install Storage Audit in Codex?

Run `npx skills add Mathews-Tom/armory --skill storage-audit -a codex`. Or copy the skill folder (skills/storage-audit in Mathews-Tom/armory) into .agents/skills/storage-audit in your project. Codex loads it when a task matches its description.

Can I use Storage Audit in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Mathews-Tom/armory --skill storage-audit -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/storage-audit, .gemini/skills/storage-audit, .github/skills/storage-audit and .opencode/skills/storage-audit in your project.

What does Storage Audit need to run?

Going by SKILL.md and its folder, Storage Audit needs a shell for the scripts in its folder and the command-line tools its instructions call (bash). Our summary lists: A Bash shell.

Does Storage Audit access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Storage Audit safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Storage Audit use?

Storage Audit is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Storage Audit use?

About 1.4k tokens (SKILL.md is roughly 5.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.7k tokens, read only when the agent opens those files.

What are the alternatives to Storage Audit?

Skills that share tags, products or a category with Storage Audit: Finishing a Development Branch (obra/superpowers, 297k stars), Code Design Rationale Investigator (cursor/plugins, 10k stars), Contributor-First PR Merge (HKUDS/OpenHarness, 16k stars) and Migrate Internal Package into Ghost (TryGhost/Ghost, 56k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Storage Audit?

Mathews-Tom (a GitHub user) maintains it in Mathews-Tom/armory, which has 328 GitHub stars. The repository holds 80 skills in this directory. The repository was last updated on October 6, 2026.

Source: Mathews-Tom/armory on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.