Skills Janitor plugin

A plugin that shows which skills, subagents and MCP servers waste context, then helps you remove the surplus

  • 125 ★ on the repository
  • Last commit
  • MIT
Plugin

Extended access

Why this level

  • Reads session transcripts and configs and deletes chosen skills and server entries after confirmation; it backs up configs before editing.
All reasons and checks

khendzel/skills-janitor

Install

In your terminal, with SkillFoxx CLI

npx skillfoxx add plugins/skills-janitor

Detects the agents on your machine, shows the access level and pins the version.

Other ways to install

Access and checks

How we review

Extended accessThe tool runs code or makes network calls and only reads external data.

  • Reads session transcripts and configs and deletes chosen skills and server entries after confirmation; it backs up configs before editing.

This is third-party code. Review the repository files before installing.

What it does

Skills Janitor walks through skill locations (user, project, Codex and everything installed through plugins), plus subagents and MCP servers. It finds duplicates, broken symlinks, unused skills and servers that are connected but never called. Usage counts come from real session transcripts. There are six commands: /janitor-report, /janitor-fix, /janitor-value, /janitor-security, /janitor-discover and /janitor-swipe. The last opens a terminal interface where skills and MCP servers are swiped like cards: left deletes, right keeps. The security scan looks for instruction-override phrases, hidden text and scripts that pipe network content into a shell.

Who it is for. People whose Claude Code or Codex setup has grown to dozens of skills and servers that fill the context before the first prompt.

Good fit when

  • The context is full from the start of a session and it is unclear which skill is to blame.
  • Before installing someone else's skill you want to scan it for hidden instructions.
  • The same skill lives in a project and in a plugin and you need to find such pairs.
  • A work machine keeps dead symlinks and empty folders left from old installs.

Not a fit when

  • You work only in Claude Code and just want to trim context: the built-in /skill-doctor and /doctor commands give the same data.
  • You need token counts for MCP servers: schemas live server-side and the plugin counts calls only.
  • You expect new features: the author moved the project to maintenance mode and accepts fixes only.

Example request

Show which skills and MCP servers went unused over the last eight weeks and suggest what to delete.

Limitations

Since September 2026 the project is in maintenance mode and the author plans no new features. Claude Code now covers most context accounting itself through /skill-doctor and /doctor, which see real usage from inside the harness. The plugin remains useful for the security scan, duplicate detection, Codex support and deleting broken symlinks. Scan verdicts are heuristic: RISK means read before installing and does not prove malice. The scripts need Bash, Python 3 and curl.

How to disable. Run /plugin uninstall skills-janitor, or delete ~/.claude/skills/skills-janitor if you installed by copying. The .bak backups of configs written when servers were removed stay in their folders.

FAQ

How does /janitor-swipe differ from /janitor-fix?

/janitor-swipe opens an interactive deck where you decide one by one whether to delete a skill or MCP server. /janitor-fix repairs found problems automatically, and with --prune it removes broken symlinks and empty folders.

What happens when I delete an MCP server in the deck?

The server entry is removed from its config file and a timestamped .bak backup is saved next to it. Servers bundled in plugins are only flagged for review.

How do I check a skill before installing it?

Run /janitor-discover with the repository URL: it reports overlap with installed skills and the security scan result.

Does the plugin work with Codex?

Yes, the README states support for Claude Code and OpenAI Codex.

Do I need to install anything besides the plugin?

No, there are no dependencies: the scripts need Bash, Python 3 and curl, and no pip packages or node modules.

Discussion

No questions or reviews yet.

Plugins

A desktop app and skm CLI: one copy of each skill in a central hub, symlinked into every AI tool

CLIExtended access1.1KRepository stars

A Windows skill that analyzes drive C across 12 categories and builds a report and a staged cleanup plan.

SkillBroad access394Repository stars

SkillRoster scans skills across all your agents, finds duplicates and broken links and builds a per-agent roster with undo.

CLIExtended access54Repository stars

Carl Skills gathers 17 author workflows with an install registry and three own skills, including a skill cleanup one.

SkillExtended access81Repository stars

Four skills for a person with several AI assistants: a task register, evidence-based acceptance, beginner instructions

PluginMinimal access828Repository stars
Official

The prompthub CLI manages prompts, skills, MCP servers and plugins and distributes one skill to Claude Code, Cursor and Codex.

CLIBroad access1.8KRepository stars

README in short

The plugin installs through the Claude Code marketplace, skills.sh or by cloning into the skills folder. Five older commands were renamed in the upgrade from version 1.2.

README badge

Report a problem