agentleFS
NobiResearchNobiResearch/Ovenbird/.claude/skills/tidy/SKILL.md

tidy

Skill1 starsChanged 18 days agoMITView on GitHub

Answer "do I need to clean up my Mac?" and reclaim disk space on this Mac safely. Use when the human asks about the Mac's disk space or storage, a slow or full Mac, its caches, or cleaning up the Mac. Not for cleaning up, refactoring or tidying code or a project.

  • Deletes or force-pushes

26 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use map, help and 8 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • AWSSkill

    map

    Map verified service capabilities against customer-provided control framework and threat model. Produces mapping-results.json, controls-catalog.md, and framework-mapping.md. Supports pluggable frameworks: CCMv4, NIST 800-53, CIS Benchmarks, ISO 27001, etc. Split into 4 focused sub-skills for better accuracy; this skill orchestrates them.

    Also in 3 projects that use this

  • MicrosoftSkill

    help

    Entry point for the MedImageInsight plugin, covering the getting-started walkthrough, how the skills work, what MI2 is, and troubleshooting.

    Also in 4 projects that use this

  • AnthropicSkill

    status

    Case status summary by audience — client-facing (plain language), internal (for the professor), or court-ready (formal caption format per local rules). Same facts, different framing and depth. Use when a student needs to update the client, brief the professor, or prepare a court status report.

    Also in 4 projects that use this

  • Harut8Skill

    architect

    Also in 3 projects that use this

  • AWSSkill

    retro

    Conduct a retrospective on a coding session.

    Also in 3 projects that use this

  • AWSSkill

    ship

    Finalize dev work on an issue branch — update docs, push, and open a PR.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

5 rules. 0 are common, 2 are distinctive, and 3 are very specific to this project.

  • 0

    Common

    Most of the 21 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  • could be automatic: a setting could enforce it
  1. Very specific:

    Look first: Run cos status and cos clean --json (add --deep if they ask for a thorough pass.

    line 13
  2. Distinctive:

    Answer the actual question first: Do they *need* to clean up?

    line 15
  3. Very specific:

    Never rm -rf user folders yourself.

    line 32
  4. Distinctive:

    Never empty the Trash or delete downloads without naming them to the human first.

    line 34
  5. Very specific:

    If they say "just do the safe ones": apply every safe target, nothing else.

    line 35

“Common” is measured: kept by at least 6 in 10 of the 21 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Works from any folder on this Mac (0009). Run syscalls as cos …; in the Ovenbird folder, bin/cos … is the same. Whatever you cos remember or cos friction add is about the human or this Mac, never the project or client you're working in.

Tidy

Steps

  1. Look first. Run cos status and cos clean --json (add --deep if they ask for a thorough pass; it also finds stale node_modules and files over 2 GB).
  2. Answer the actual question first. Do they need to clean up? Judge it by free space (under ~15% or ~30 GB is tight; over ~25% is comfortable), the trend if you know it, and what they do (developers accumulate Xcode and package caches fast). Say it plainly in one or two sentences.
  3. Show the opportunity as a short table, biggest first: size, safety, what it is, and what it costs them to reclaim it (e.g. "next Xcode build is slower", "simulators lose their installed apps").
    • safe: recommend these as a bundle.
    • review: show the details (e.g. which simulators, which caches) and let them choose.
    • careful: list only. Explain how to handle it by hand (Finder, hf cache, etc).
  4. Ask which targets to reclaim. Never apply without a yes in this conversation.
  5. Apply exactly what they approved: cos clean apply <id> <id> --yes. The permission prompt will show the human the exact command; that's intended.
  6. Report what was freed and the new free space (cos status).

Rules

  • Never rm -rf user folders yourself; go through cos clean apply. If a target is missing, propose it as friction (cos friction add "clean: add target for X").
  • Never empty the Trash or delete downloads without naming them to the human first.
  • If they say "just do the safe ones": apply every safe target, nothing else.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.