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
- aldisf/sg-stay-wheretheir own version, first seen Nov 16, 2026
- FYClamityDestiny/vettedtheir own version, first seen Nov 15, 2026
- Dariusplayer09/adaptive-skillstheir own version, first seen Nov 8, 2026
- sachingulati/claude-statuslinetheir own version, first seen Nov 1, 2026
- talal-ai/handoff-nowtheir own version, first seen Oct 20, 2026
- pushprove-max/Commandecktheir own version, first seen Oct 17, 2026
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.
MicrosoftSkillconfig
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
VercelSkillsetup
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
Other versions17 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 17
- anthropics/claude-for-legal★ 9.5ksame name
- openclaw/openclaw-windows-node★ 2.2ksame name
- shanselman/openclaw-windows-hub★ 2.2ksame name
- tmck-code/yet-another-statusline★ 244same name
- tanerincode/jedi-statusline★ 18same name
- HAX-Studio/mnemonica★ 3same name
- pushprove-max/Commandeck★ 3same name
- aldisf/sg-stay-where★ 2same name
- sachingulati/claude-statusline★ 2same name
- yang1997434/claude-code-hud★ 2same name
7 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository56 other files it gives its agents.
- .claude/agents/CLAUDE.mdCLAUDE.md
- .claude/hooks/CLAUDE.mdCLAUDE.md
- CLAUDE.mdCLAUDE.md
- .claude/prompts/CLAUDE.mdCLAUDE.md
- .claude/rules/CLAUDE.mdCLAUDE.md
- .claude/skills/CLAUDE.mdCLAUDE.md
- docs/CLAUDE.mdCLAUDE.md
- vision/CLAUDE.mdCLAUDE.md
- llms.txtllms.txt
- scaffold/llms.txtllms.txt
- architecture-checkSkill
- backlog-reviewSkill
- bootstrapSkill
- brainstormSkill
- buildSkill
- claude-sense-checkSkill
- code-qualitySkill
- commitSkill
- continueSkill
- custom-hooksSkill
- dashboardSkill
- debug-sessionSkill
- deploySkill
- discoverSkill
- doctorSkill
- fix-issueSkill
- framework-upgradeSkill
- handoffSkill
- help-meSkill
- ideateSkill
- lanesSkill
- manual-testSkill
- merge-downSkill
- merge-upSkill
- optimizeSkill
- parallel-workSkill
- performance-checkSkill
- phase-reviewSkill
- pr-statusSkill
- quality-checkSkill
- quickstartSkill
- refine-loopSkill
- researchSkill
- retrospectiveSkill
- security-auditSkill
- skill-createSkill
- skill-evalSkill
- sprint-endSkill
- sprint-startSkill
- story-cycleSkill
- testing-cycleSkill
- test-validatorSkill
- UAT-cycleSkill
- undo-workSkill
- weekly-maintenanceSkill
- wrap-upSkill
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
- Very specific: line 16
Remove the Exosuit framework from this project.
- Distinctive: line 24
Ask the user to confirm using AskUserQuestion:
- Distinctive: line 32
Before removing, inventory what exists:
- Distinctive: line 112
If CLAUDE.md exists, offer to simplify it:
- Distinctive: line 113
Remove the Skills section (skill references won't work)
- Distinctive: line 114
Remove the Compaction Directive (framework-specific)
- Distinctive: line 115
Keep: Project Overview, Commands, Architecture, Git Workflow, Current Focus, Backlog references, Testing
- Distinctive: line 120
Remove framework-specific patterns from .gitignore:
- Distinctive: line 125
Only remove these if no other tool uses them.
- Distinctive: line 156
NEVER remove files without explicit user confirmation
- Distinctive: line 157
ALWAYS show what will be removed AND what will be preserved before acting
- Distinctive: line 158
NEVER remove source code, test files, or non-framework project files
- Very specific: line 159
ALWAYS offer to backup .claude/settings.local.json (contains user customizations)
- Very specific: line 160
If .claude/ directory has non-framework files, warn and skip those files
- Distinctive: line 161
After removal, verify the project still has a valid .git directory
“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.
Files
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/nullProject-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/nullTechnology-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
donePresent 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.mddocs/reference/CODING_STANDARDS.mddocs/reference/TESTING_STRATEGY.mddocs/reference/GROUND_RULES.mddocs/context/*docs/progress.mddocs/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 directoryDoes 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
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.

