Janitor Swipe logo

Janitor Swipe

Community
khendzel
janitor-swipe

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'.

Overview

Publisherkhendzel
Repositoryskills-janitor
Skill namejanitor-swipe
Stars
124
Forks
19
Bundled files
Instructions only
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by khendzel on GitHub. Read the source before you install it.

Installation

Install the Janitor Swipe AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/khendzel/skills-janitor/tree/main/skills/janitor-swipe
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/khendzel/skills-janitor.git /tmp/skills-janitor
mkdir -p .claude/skills
cp -r /tmp/skills-janitor/skills/janitor-swipe .claude/skills/janitor-swipe
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Janitor Swipe in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Janitor Swipe on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Janitor Swipe is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

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.sh and swipe-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.sh

When 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 — skip
  • u — 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)

ScopeWhat happens on swipe left
user, project, codex-user, codex-projectPath is staged for rm -rf (or unlink if symlink)
plugin, plugin-sourceNOT 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-pluginNOT 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.jsonl with path and frontmatter snapshot)
  • N — cancel
  • save — write decisions to ~/.skills-janitor/swipe-<timestamp>.json for later application via swipe.sh --apply <file>

Error Handling

  1. 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.

  2. Error: "Swipe needs at least 50 columns / 22 rows" Solution: The terminal window is too small — resize and retry.

  3. Error: No skills to swipe Solution: Nothing is installed (exits 0 with a message) — suggest /janitor-discover to find skills.

  4. Error: The user wants a non-interactive view instead Solution: Point them at /janitor-report or /janitor-value for 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

Frequently asked questions

What does the Janitor Swipe AI skill do?

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'.

Why use Janitor Swipe on TypingMind?

Because you install it once and use it with any model. Janitor Swipe is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Janitor Swipe in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/khendzel/skills-janitor/tree/main/skills/janitor-swipe. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Janitor Swipe?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Janitor Swipe?

As many as you like. As long as a model supports skills, you can use Janitor Swipe with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Janitor Swipe AI skill free?

Yes. It is published on GitHub by khendzel under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇