agentleFS
joris887joris887/exosuit/.claude/skills/uninstall/SKILL.md

uninstall

Skill9 starsChanged 3 months agoMITView on GitHub

Cleanly remove the Exosuit framework from a project while preserving project-specific content.

  • Pipes a download into a shell
  • Deletes or force-pushes

17 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use config and setup.

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

  • 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

The file

Show its rules and text

We split this skill into the rules it gives an agent

15 rules. 0 are common, 12 are distinctive, and 3 are very specific to this project.

  • 0

    Common

    Most of the 14 edited versions we read keep these.

  • 12

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

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

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

    Remove the Exosuit framework from this project.

    line 16
  2. Distinctive:

    Ask the user to confirm using AskUserQuestion:

    line 24
  3. Distinctive:

    Before removing, inventory what exists:

    line 32
  4. Distinctive:

    If CLAUDE.md exists, offer to simplify it:

    line 112
  5. Distinctive:

    Remove the Skills section (skill references won't work)

    line 113
  6. Distinctive:

    Remove the Compaction Directive (framework-specific)

    line 114
  7. Distinctive:

    Keep: Project Overview, Commands, Architecture, Git Workflow, Current Focus, Backlog references, Testing

    line 115
  8. Distinctive:

    Remove framework-specific patterns from .gitignore:

    line 120
  9. Distinctive:

    Only remove these if no other tool uses them.

    line 125
  10. Distinctive:

    NEVER remove files without explicit user confirmation

    line 156
  11. Distinctive:

    ALWAYS show what will be removed AND what will be preserved before acting

    line 157
  12. Distinctive:

    NEVER remove source code, test files, or non-framework project files

    line 158
  13. Very specific:

    ALWAYS offer to backup .claude/settings.local.json (contains user customizations)

    line 159
  14. Very specific:

    If .claude/ directory has non-framework files, warn and skip those files

    line 160
  15. Distinctive:

    After removal, verify the project still has a valid .git directory

    line 161

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

Remove the Exosuit framework from this project.

Phase 0: Confirm Intent

<HARD-GATE> This will remove framework files from the project. Present what will happen and require explicit confirmation before proceeding. </HARD-GATE>

Ask the user to confirm using AskUserQuestion:

  • "Full removal" — description: "Remove all framework files (.claude/, framework docs, scripts). Keep source code, tests, and project docs untouched."
  • "Keep documentation" — description: "Remove framework machinery (.claude/) but keep generated docs (ARCHITECTURE.md, CODING_STANDARDS.md, GROUND_RULES.md, etc.)"
  • "Cancel" — description: "Don't remove anything"

Phase 1: Inventory

Before removing, inventory what exists:

Framework Files (will be removed)

# Core framework
echo "=== Core Framework ==="
ls -d .claude/skills/ .claude/hooks/ .claude/rules/ .claude/agents/ .claude/prompts/ .claude/commands/ .claude/output-styles/ .claude/scripts/ 2>/dev/null

# Settings and config
echo "=== Settings ==="
ls .claude/settings.json .claude/settings.local.json.template .claude/keybindings.json.template 2>/dev/null

# Framework scripts
echo "=== Scripts ==="
ls scripts/pm/*.sh 2>/dev/null

# Framework root files
echo "=== Root Files ==="
ls install.sh AGENTS.md llms.txt CLAUDE.local.md.template 2>/dev/null

Project-Specific Content (will be PRESERVED)

echo "=== Preserved ==="
ls docs/architecture/ docs/reference/ docs/context/ docs/testing/ docs/sessions/ docs/adr/ docs/progress.md docs/technical-debt.md CLAUDE.md 2>/dev/null

Technology-Specific Skills (ask user)

# Skills generated by /skill-create for the project's stack
echo "=== Technology Skills (project-specific) ==="
for skill_dir in .claude/skills/*/; do
    skill_name=$(basename "$skill_dir")
    # Check if it's a framework skill or a tech skill
    case "$skill_name" in
        bootstrap|sprint-start|story-cycle|sprint-end|continue|handoff|brainstorm|ideate|research|skill-create|code-quality|test-validator|security-audit|architecture-check|manual-test|testing-cycle|UAT-cycle|claude-sense-check|debug-session|fix-issue|undo-work|commit|parallel-work|weekly-maintenance|retrospective|backlog-review|doctor|framework-upgrade|pr-status|skill-eval|refine-loop|optimize|quickstart|help-me|dashboard|custom-hooks|uninstall|performance-check)
            ;; # Framework skill — will be removed
        *)
            echo "  $skill_name (technology-specific)"
            ;;
    esac
done

Present the inventory and ask: "Technology-specific skills were generated for your stack. Should I preserve or remove them?"

Phase 2: Remove Framework Files

Based on user's choice:

Full Removal

# Remove core framework (preserve settings.local.json if it exists)
cp .claude/settings.local.json /tmp/claude-settings-backup.json 2>/dev/null
rm -rf .claude/skills/ .claude/hooks/ .claude/rules/ .claude/agents/ .claude/prompts/ .claude/commands/ .claude/output-styles/ .claude/scripts/
rm -f .claude/settings.json .claude/settings.local.json.template .claude/keybindings.json.template
rm -rf .claude-plugin/

# Remove framework scripts
rm -rf scripts/pm/

# Remove framework root files
rm -f install.sh AGENTS.md llms.txt CLAUDE.local.md.template

# Remove vision (if user confirms it's not needed)
# Ask: "Remove vision/ directory? (Contains braindump templates)"

Keep Documentation Mode

Same as above, but ALSO preserve:

  • docs/architecture/ARCHITECTURE.md
  • docs/reference/CODING_STANDARDS.md
  • docs/reference/TESTING_STRATEGY.md
  • docs/reference/GROUND_RULES.md
  • docs/context/*
  • docs/progress.md
  • docs/technical-debt.md

Phase 3: Clean Up CLAUDE.md

If CLAUDE.md exists, offer to simplify it:

  • Remove the Skills section (skill references won't work)
  • Remove the Compaction Directive (framework-specific)
  • Keep: Project Overview, Commands, Architecture, Git Workflow, Current Focus, Backlog references, Testing
  • The result is a standard project CLAUDE.md without framework workflow references

Phase 4: Clean Up .gitignore

Remove framework-specific patterns from .gitignore:

  • CLAUDE.local.md
  • .claude/settings.local.json
  • *.session-handoff.md

Only remove these if no other tool uses them.

Phase 5: Summary

### Framework Removed

**Removed:**
- .claude/skills/ ([N] skills)
- .claude/hooks/ ([N] hook scripts)
- .claude/rules/ ([N] rules)
- .claude/agents/ ([N] agents)
- .claude/prompts/ ([N] prompt snippets)
- scripts/pm/ ([N] PM scripts)
- [other removed files]

**Preserved:**
- [list of preserved docs/files]
- [technology-specific skills if kept]

**CLAUDE.md:** [Simplified / Untouched]

**To re-install later:**
```bash
curl -fsSL https://raw.githubusercontent.com/joris887/exosuit/main/install.sh | bash

(Windows: powershell -ExecutionPolicy Bypass -c "irm https://raw.githubusercontent.com/joris887/exosuit/main/install.ps1 | iex")


## Rules

- NEVER remove files without explicit user confirmation
- ALWAYS show what will be removed AND what will be preserved before acting
- NEVER remove source code, test files, or non-framework project files
- ALWAYS offer to backup .claude/settings.local.json (contains user customizations)
- If .claude/ directory has non-framework files, warn and skip those files
- After removal, verify the project still has a valid .git directory

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.