agentleFS
FYClamityDestinyFYClamityDestiny/vetted/skills/uninstall/SKILL.md

uninstall

Skill0 starsChanged 6 days agoMITView on GitHub

Cleanly remove something installed through Vetted (or anything else the user names) and what it left behind — plugin, skill, MCP server, package, Docker image/container, VS Code extension, cloned repo, Roblox asset. Use for "uninstall X", "remove X", "get rid of X", /vetted:uninstall <name>.

16 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use doctor, config and 2 more.

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

    doctor

    Diagnose an Amplifier CLI environment through the CLI doctor agent. USE WHEN a user requests CLI runtime, settings or missing-capability inspection. DO NOT USE for project bugs or other hosts.

    Also in 6 projects that use this

  • 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

  • VercelSkill

    setup

    Set up Vercel CLI and project configuration. Use when the user says "set up Vercel", "configure Vercel", "link to Vercel", or "vercel init".

    Also in 7 projects that use this

  • +1 more from microsoft

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 13 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

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

    Find it: Look it up in ~/.claude/vetted-log.md, which records the remove command.

    line 8

“Common” is measured: kept by at least 6 in 10 of the 13 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

Uninstall

  1. Find it. Look it up in ~/.claude/vetted-log.md, which records the remove command. If it isn't there, work out how it was installed from where it lives (plugin list, ~/.claude/skills, claude mcp list, package files, docker ps -a/docker images, code --list-extensions).
  2. Show the plan, then wait for a yes. List exactly what will be removed: the package or plugin, its config entries (MCP config, hooks in settings.json), the files it created, its Docker containers, images and volumes (volumes hold data, so name them separately and ask), and any environment variables or API keys it asked for (remind the user to revoke those keys).
  3. Remove with the matching command:
    • plugin: claude plugin uninstall <name>
    • skill: delete its folder
    • MCP server: claude mcp remove <name>
    • npm/pip: uninstall it and remove it from the manifest
    • VS Code: code --uninstall-extension <id>
    • Docker: docker rm, then docker rmi
    • cloned repo: move it to the trash (not a permanent delete) unless the user says otherwise
    • Roblox asset: list the instances to delete in Studio
  4. Verify it's gone (run the same list commands again), then mark the log entry removed <date>.
  5. If it was rated ⛔ or ⚠️, also suggest checking for anything it may have left running: scheduled tasks, startup entries, unknown processes. And rotate any keys it could read.

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.