agentleFS
zoo3323zoo3323/usage-statusline/skills/uninstall/SKILL.md

uninstall

Skill1 starsChanged 32 days agoMITView on GitHub

Remove the usage-statusline status line — its scripts, its caches and the statusLine entry in settings.json. The plugin itself stays until it is uninstalled with /plugin.

15 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use doctor, config and 1 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

  • +1 more from microsoft

The file

Files
SKILL.md

Remove the status line

This undoes what /usage-statusline:setup did. It does not uninstall the plugin.

  1. Tell the user what will be removed and ask them to confirm:
    • the scripts in ~/.claude/scripts/ (statusline-codex.sh, usage-refresh.sh, claude-usage-refresh.sh, codex-usage-refresh.sh)
    • the caches and the saved choices in ~/.claude/codex-status/
    • the cu-refresh link in ~/.local/bin
    • the statusLine entry in ~/.claude/settings.json, when it is this status line
  2. Once they confirm, run:

    bash "${CLAUDE_PLUGIN_ROOT}/uninstall.sh"

    It backs up settings.json first, leaves every other setting alone, and prints what it did. If it fails, show its output.

  3. Say that the line disappears in a new session, and that the plugin itself is removed with /plugin uninstall usage-statusline if they no longer want the skills either.

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.