agentleFS
Sign inStart free
lamb92009lamb92009/claude-skill-loader/skill-cleanup/SKILL.md

skill-cleanup

Skill4 starsChanged 9 months agoMITView on GitHub

Removes session-fetched skills from ~/.claude/skills/ using the .session-skills manifest, keeping the directory lean between sessions.

  • Deletes or force-pushes
  • In this repositoryOne other file it gives its agents.

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
  1. Very specific:

    Must match the PERMANENT_SKILLS list in skill-loader.

    line 15
  2. Very specific:

    Remove skills that were fetched for this session, restoring ~/.claude/skills/ to its lean baseline.

    line 22
  3. Distinctive:

    If the file does not exist or is empty, report:

    line 30

≈ “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.

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

Skill Cleanup

<!-- ============================================================ CONFIGURATION — must match your skill-loader configuration ============================================================ --><!-- PERMANENT_SKILLS: skills that are always locally installed and must never be removed, even if they appear in the manifest. Must match the PERMANENT_SKILLS list in skill-loader. -->

PERMANENT_SKILLS: skill-loader, skill-cleanup (add any others here, e.g. a brand-reference skill)

<!-- ============================================================ -->

Remove skills that were fetched for this session, restoring ~/.claude/skills/ to its lean baseline.

Step 1 — Check for manifest

cat ~/.claude/skills/.session-skills 2>/dev/null

If the file does not exist or is empty, report:

No session skills found — ~/.claude/skills/ is already clean.

Then stop.

Step 2 — Read the manifest

Parse the list of skill names (one per line). These are the skills to remove.

Step 3 — Remove session skills

For each skill name in the manifest:

rm -rf ~/.claude/skills/<skill-name>
echo "Removed: <skill-name>"

Never remove permanent residents (defined in PERMANENT_SKILLS above) — even if they appear in the manifest. Skip any name that matches a permanent skill.

(Replace this safeguard list with your configured PERMANENT_SKILLS values)

  • skill-loader
  • skill-cleanup

Step 4 — Remove the manifest

rm -f ~/.claude/skills/.session-skills
echo "Manifest removed."

Step 5 — Confirm

Show what remains:

ls ~/.claude/skills/

Report what was removed and what permanent skills remain.

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.

Check your setup, free