Config GC — garbage collection for your Claude Code configuration
Scan ~/.claude for stale skills, hooks, permissions, MCP servers and caches, then walk through confirm-each-deletion cleanup with soft-delete and a gc_log
- What
- Scan ~/.claude for stale skills, hooks, permissions, MCP servers and caches, then walk through confirm-each-deletion cleanup with soft-delete and a gc_log
- Cost
- Free
- Needs
- a Claude Code setup (~/.claude) to clean up — the skill is guidance the agent follows, not software to install
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — @affaan-m's Config GC: garbage collection for a Claude Code setup. It scans eight accumulation channels — skills, memory files, hooks, permission entries, MCP servers, scheduled reminders/jobs, project history and runtime caches — for redundant, stale, orphaned or low-value items, ranks candidates by confidence, and walks the user through a confirm-one-by-one cleanup (no "yes to all" shortcut). The design is deliberately safe: soft-delete first (`.disabled` renames, `_gc_trash/<date>/` moves), settings JSON is backed up before permission entries are pruned with `jq`, and every run is logged to `~/.claude/gc_log.md` with undo instructions. Includes ready-made scan commands (orphan hook scripts, redundant permission entries, largest stale caches) and an anti-pattern list (bulk approval, hard-deleting on first pass, treating "old" as "dead"). Honest caveats: methodology + shell commands, no binaries — it only works on a Claude Code setup; it never deletes autonomously by design (a human confirms each item), and it never touches anything outside `~/.claude`. MIT licensed. Skill Harbor never reviews the code, review it yourself before use. Discovered via skills.sh.
Version:
Install
Prerequisites: a Claude Code setup (~/.claude) to clean up — the skill is guidance the agent follows, not software to install Install "Config GC — garbage collection for your Claude Code configuration" for me. It gives my agent @affaan-m's config-cleanup workflow: scan eight channels (skills, memory files, hooks, permission entries, MCP servers, scheduled jobs, project history, caches) for stale or redundant items, rank candidates by confidence, confirm each deletion one by one, soft-delete (.disabled renames, _gc_trash/<date>/ moves, JSON backups), and log everything to ~/.claude/gc_log.md with undo instructions. MIT-licensed. Repository: https://github.com/affaan-m/ecc/blob/main/skills/config-gc/SKILL.md 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "config-gc". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. tell the agent to run a scan ("clean up my config") and confirm each deletion one by one; nothing else — it never deletes autonomously by design). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.