agentleFS
Sign inStart free
aquahittaquahitt/claude-code-limit-alerts/skills/uninstall/SKILL.md

uninstall

Skill1 starsChanged 4 months agoMITView on GitHub

Use when the user wants to remove limit-alerts, disable the plugin cleanly, or undo the statusline and background agent it configured.

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

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

  • 0

    Common

    Most of the 12 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Remove both by turning the options off and re-running the bootstrap:

    line 10

“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

Remove what the plugin wrote outside itself

Disabling a plugin does not undo writes it made elsewhere. Two things outlive it: the statusLine entry in settings.json (~/.claude/settings.json, or the one in $CLAUDE_CONFIG_DIR when the session runs with it) and the launchd agent com.claude.usage-monitor.plugin. Under CLAUDE_CONFIG_DIR the agent is removed only if this installation created it; the default configuration's agent stays.

Remove both by turning the options off and re-running the bootstrap:

UM_STATE_DIR="${CLAUDE_PLUGIN_DATA}" \
CLAUDE_PLUGIN_OPTION_STATUSLINE=false \
CLAUDE_PLUGIN_OPTION_LAUNCHD=false \
bash "${CLAUDE_PLUGIN_ROOT}/scripts/plugin-bootstrap.sh"

This restores whatever statusline was in place before the plugin took over, or removes the key if there was none, and unloads and deletes the agent's plist.

Then tell the user to disable or uninstall the plugin itself with /plugin.

State and cache live in ${CLAUDE_PLUGIN_DATA} and go away with the plugin's data directory. Do not delete that directory while the plugin is still enabled — the next session start would just recreate it.

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