agentleFS
pushprove-maxpushprove-max/Commandeck/skills/uninstall/SKILL.md

uninstall

Skill3 starsChanged 6 days agoApache-2.0View on GitHub

Take commandeck out of this project and put every file back as it was. Use when the owner runs /commandeck:uninstall or says "uninstall commandeck", "remove the workflow".

15 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use config.

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

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 2 are distinctive, and 1 is 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.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Ask the owner one question: keep the data the plugin gathered for this project (cost and decision ledgers, scratch, hook log, rulings, the …

    line 10
  2. Very specific:

    Run bash ${CLAUDE_PLUGIN_ROOT}/scripts/uninstall.sh, with --delete-data when the owner said delete.

    line 13
  3. Distinctive:

    Run this skill in every project first, while the scripts are still there.

    line 21

“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

/commandeck:uninstall

  1. Ask the owner one question: keep the data the plugin gathered for this project (cost and decision ledgers, scratch, hook log, rulings, the list of finished builds) or delete it. Briefs and review rounds are never touched either way.
  2. Run bash ${CLAUDE_PLUGIN_ROOT}/scripts/uninstall.sh, with --delete-data when the owner said delete.
  3. Show its output whole. A changed since setup line names a file the owner edited after setup: the plugin's entries are out of it, the owner's edits are kept, and it is not byte-for-byte what it was.
  4. The machine's parts (Codex's hooks, the dashboard job, a status line setup set: the one before it comes back) go with the last project; the output says which projects still hold them.
  5. The plugin itself is Claude Code's to remove: claude plugin uninstall commandeck. Run this skill in every project first, while the scripts are still there.

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.