janitor-swipe
Skill123 starsChanged 3 months agoMITView on GitHub
Tinder for your Claude Code skills. Reviews a sorted deck of every installed skill and lets you swipe keep / delete / skip on each one. Use when the user wants to bulk-clean their skill collection, triage unused skills, or do interactive skill cleanup. Trigger with '/janitor-swipe'.
- Deletes or force-pushes
1 other project uses a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- juanmackie/juanskillsedited, first seen Oct 20, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 1
- juanmackie/juanskills★ 191% same
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository5 other files it gives its agents.
- janitor-discoverSkill
- janitor-fixSkill
- janitor-reportSkill
- janitor-securitySkill
- janitor-valueSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 42
When the user asks for /janitor-swipe, tell them to run that command in their terminal.
- Very specific: line 77
After the last card (or q), an apply screen shows keep/skip/delete counts, the deletion list with paths, the "frees X always-loaded + Y …
- Distinctive: line 91
Error: No skills to swipe
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Janitor Swipe — interactive skill triage
A bash TUI that puts every installed skill into a sorted deck and lets the user swipe keep / delete / skip on each card.
Overview
The deck is sorted "most likely waste first" — heavy, never-used skills appear at the top, so most users hit ← delete a few times and quit before reviewing the whole list. The swipe is scope-aware and honest about what it can delete: user-scope skills are actually removed (after confirmation), plugin skills are flagged for review instead.
Prerequisites
- Claude Code with the skills-janitor plugin installed (provides
scripts/swipe.shandswipe-build-deck.sh) - bash 3.2+ (the stock macOS bash works; no external dependencies)
- An interactive terminal at least 50 columns x 22 rows — the TUI reads single keypresses
Instructions
Step 1: Tell the user to run it via !
Inside Claude Code, the Bash tool's stdin is non-interactive, so the keypress reader can't work. The user must invoke it via the ! prefix so the command runs in their actual shell:
!bash ~/.claude/skills/skills-janitor/scripts/swipe.shWhen the user asks for /janitor-swipe, tell them to run that command in their terminal. Do NOT try to run it yourself via the Bash tool — it will error with "needs an interactive terminal".
Step 2: Explain the card and controls
Each card shows:
- Skill name + position in deck (e.g.
[3 / 47]) - Context cost split:
X always · Y on trigger(description tokens are permanent; body loads only when the skill fires) - Usage count and last invoked date
- Scope (
user,project,plugin · <plugin-name>, etc.) - 3-line truncated description
- Verdict label (e.g. "Unused + heavy on trigger — prime delete candidate")
Controls:
←/h/d— stage for delete→/l/k— keep↓/j/s/ space — skipu— undo (back up one card, clear its decision)i— inspect (show full SKILL.md description)q/ Esc — quit (still shows summary for decisions made so far)
Step 3: Scope-aware deletion (the critical correctness point)
| Scope | What happens on swipe left |
user, project, codex-user, codex-project | Path is staged for rm -rf (or unlink if symlink) |
plugin, plugin-source | NOT deleted — flagged under "Plugins to review" at the apply screen, with a hint to run /plugin uninstall <plugin> if enough skills from that plugin were swiped |
mcp-user, mcp-project (v1.7) | Server entry is removed from its config file (~/.claude.json / .mcp.json) with a timestamped .bak backup — reversible |
mcp-plugin | NOT edited — flagged for plugin review like plugin skills |
MCP server cards show real call counts from session transcripts instead of token guesses (schemas live server-side). An unused connected server ranks high — its tool schemas load into context for nothing.
Output
After the last card (or q), an apply screen shows keep/skip/delete counts, the deletion list with paths, the "frees X always-loaded + Y on-trigger" token summary, the plugin review breakdown, and a prompt:
y— apply deletions immediately (logged to~/.skills-janitor/log.jsonlwith path and frontmatter snapshot)N— cancelsave— write decisions to~/.skills-janitor/swipe-<timestamp>.jsonfor later application viaswipe.sh --apply <file>
Error Handling
- Error: "Swipe needs an interactive terminal"
Solution: The command was run through the Bash tool. Have the user run it with the
!prefix in their own terminal. - Error: "Swipe needs at least 50 columns / 22 rows" Solution: The terminal window is too small — resize and retry.
- Error: No skills to swipe
Solution: Nothing is installed (exits 0 with a message) — suggest
/janitor-discoverto find skills. - Error: The user wants a non-interactive view instead
Solution: Point them at
/janitor-reportor/janitor-valuefor the same data in list form.
Edge cases handled by the script: Ctrl-C mid-swipe restores the terminal; symlinks are unlinked, never followed; old saved decks without the v1.5 token-split fields still load.
Examples
Example 1: Standard triage
Input: "/janitor-swipe" or "help me clean up my skills interactively"
Output: Explain the flow in two sentences, then give the exact command to run: !bash ~/.claude/skills/skills-janitor/scripts/swipe.sh — and offer to review the results afterwards.
Example 2: Resume saved decisions
Input: "I saved my swipe decisions yesterday — apply them."
Output: !bash ~/.claude/skills/skills-janitor/scripts/swipe.sh --apply ~/.skills-janitor/swipe-<timestamp>.json (list the files in ~/.skills-janitor/ to find the right one).
Resources
- TUI script (plugin-relative):
{baseDir}/../../scripts/swipe.sh; deck builder:{baseDir}/../../scripts/swipe-build-deck.sh - Deletion log:
~/.skills-janitor/log.jsonl /janitor-report— same data as a non-interactive list/janitor-value— the token + usage data underneath the swipe deck/janitor-fix --prune— automated broken-symlink cleanup, no interactive review
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
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.