agentleFS
HAX-StudioHAX-Studio/mnemonica/skills/uninstall/SKILL.md

uninstall

Skill3 starsChanged 3 months agoMITView on GitHub

This skill should be used when the user asks to "uninstall mnemonica", "remove mnemonica from this project", "stop using mnemonica here", or wants Mnemonica's block and optionally its documentation removed from a project.

15 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use config and handoff.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • MicrosoftSkill

    config

    Show or change TokenEconomizer's settings: turn micro-skills, tool pruning or the loop guard on or off, or tune them, for this repository or (with --global) every repository. Use when the user asks to configure, enable or disable TokenEconomizer or one of its mechanisms.

    Also in 3 projects that use this

  • MicrosoftSkill

    handoff

    Compact the current conversation into a handoff document for another agent to pick up.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

5 rules. 0 are common, 2 are distinctive, and 3 are very specific to this project.

  • 0

    Common

    Most of the 12 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Remove exactly what Mnemonica added to a project — never more.

    line 8
  2. Distinctive:

    If the user's invocation includes extra wording (for example, "uninstall but keep the knowledge folder"), treat it as answering Step 2 in …

    line 16
  3. Very specific:

    Ask the user, explicitly, whether to also delete the knowledge/ folder and its contents.

    line 36
  4. Distinctive:

    Do not delete it without an answer, and do not default to deleting it.

    line 37
  5. Very specific:

    Never touch README.md — it was never Mnemonica's to manage in the first place.

    line 45

“Common” is measured: kept by at least 6 in 10 of the 12 edited versions of this file we could read. “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

Mnemonica: uninstall

Remove exactly what Mnemonica added to a project — never more. This mirrors setup's non-destructive install in reverse: the CLAUDE.md block is safe to remove without asking (removing what this plugin itself added is the same risk category as adding it), but knowledge/ holds real, accumulated documentation that took real reconciliation work to build, so deleting it follows the same "ask before deleting" rule as any other module deletion in knowledge-conventions.md — do not treat uninstall as a blanket exemption from that rule.

If the user's invocation includes extra wording (for example, "uninstall but keep the knowledge folder"), treat it as answering Step 2 in advance rather than asking again — but do not let it skip Step 1's confirmation-free block removal into something riskier than described here, and do not let it turn into deleting anything else in the project.

Step 1: Remove the CLAUDE.md block

Run ${CLAUDE_PLUGIN_ROOT}/scripts/remove-mnemonica-block.sh <project-root>.

  • Exit 2 (NO_CLAUDE_MD) or 3 (NO_BLOCK): there is nothing installed to remove here. Tell the user and stop — do not proceed to Step 2 or touch knowledge/ in this case, since there is no evidence Mnemonica actually manages this project's knowledge/ folder (it may predate Mnemonica, or belong to something else entirely).
  • Exit 0 (BLOCK_REMOVED or FILE_REMOVED): the block is gone; if it was the only content in .claude/CLAUDE.md, the file itself was removed too. Every other line in the file, if any remained, is untouched — verify this by rereading the file rather than assuming the script did the right thing.

Step 2: Ask about knowledge/

Ask the user, explicitly, whether to also delete the knowledge/ folder and its contents. Do not delete it without an answer, and do not default to deleting it. Mention how many module files are in there so the decision is informed (losing N module files' worth of documentation is a bigger ask than losing one). If the user declines or doesn't say, leave knowledge/ exactly as it is — an orphaned knowledge/ folder with no CLAUDE.md pointer to it is harmless clutter, not a broken state, and is trivial to remove by hand later.

Step 3: Leave everything else alone

Never touch README.md — it was never Mnemonica's to manage in the first place. Never touch any part of .claude/CLAUDE.md outside what Step 1 already removed.

Step 4: Report

State plainly what was removed (the block, the file if it was removed entirely, knowledge/ if the user confirmed) and what was left in place, so there's no ambiguity about the project's state afterward.

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.