agentleFS
sachingulatisachingulati/claude-statusline/skills/uninstall/SKILL.md

uninstall

Skill2 starsChanged 12 days agoMITView on GitHub

Remove the SLine status line from your settings before uninstalling the plugin, restoring your previous status line.

15 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use setup 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.
  • 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

  • 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

Files
SKILL.md
  1. Tell the user what will happen: settings.json gets back the status line and subagent rows it had before /sline:init (or none), and the launcher is removed. Accounts config and usage cache are kept unless --purge is given. Ask them to confirm. Stop if they don't.
  2. Run:

    node "${CLAUDE_PLUGIN_ROOT}/cli/sl.js" uninstall $ARGUMENTS --json
  3. Report what changed, including the backup file. If result.leftAlone is true, say that settings.json's status line had been changed since init and was left as is. Likewise, if result.subagentLeftAlone is true, say that settings.json's subagentStatusLine had been changed since init and was left as is.
  4. Finish with the command to remove the plugin itself: /plugin uninstall sline@sachingulati.

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.