unharness — Claude Code skill: remove Citadel
unharness is a Claude Code skill that plans Citadel removal from a project and keeps a portable archive. It runs on requests to remove Citadel or clean up the harness.
MIT ★ 937 updated 2026-10-29
/plugin marketplace add SethGammon/Citadel
/plugin install citadel@citadel-localWhat unharness does
unharness checks the Citadel adoption receipt and creates an exit plan without changing the project. The plan lists files to remove or restore, altered items that will stay, the archive location, and runtime registrations whose removal status is unknown.
After explicit approval, the skill applies the saved plan with its exact confirmation token and runs a check. Node.js and the Citadel scripts are required. Older installs need an import first; modified files and registrations with unknown status are not removed or reported as confirmed removals.
What it helps with
- plan Citadel removal without changing project files
- keep a portable archive before leaving Citadel
- retain altered or ambiguous files
- check whether external registrations were actually removed
Example prompts for the agent
- Remove Citadel from this project and show me the plan before making changes.
- Clean the harness out of this project, keep an archive, and list what will remain.
- Export a readable Citadel archive without removing files.
How to install unharness
1Plugin marketplace
/plugin marketplace add SethGammon/Citadel/plugin install citadel@citadel-localThis installs the whole citadel plugin with all its skills
2Skills CLI (Vercel)
npx skills add SethGammon/Citadel --skill unharness -a claude-code3Manually: put the files in place
~/.claude/skills/unharness/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/unharness/
1Skills CLI (Vercel)
npx skills add SethGammon/Citadel --skill unharness -a codex2Manually: put the files in place
.agents/skills/unharness/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add SethGammon/Citadel --skill unharness -a cursor2Manually: put the files in place
.cursor/skills/unharness/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install SethGammon/Citadel skills/unharness2Manually: put the files in place
.github/skills/unharness/SKILL.md1Skills CLI (Vercel)
npx skills add SethGammon/Citadel --skill unharness -a gemini-cli2Platform CLI
gemini skills install https://github.com/SethGammon/Citadel --path skills/unharnessManually: put the files in place
.devin/skills/unharness/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about unharness
How do I install unharness in Claude Code?
Run /plugin marketplace add SethGammon/Citadel, then /plugin install citadel@citadel-local.
What does unharness do?
It prepares a Citadel exit plan, preserves a portable archive, and applies the plan after explicit approval. Modified files and removals with unknown status stay flagged in the report.
What does unharness need to run?
It needs Node.js, the Citadel scripts, and a valid adoption receipt. Older installs must be imported first; applying a plan requires explicit approval and its exact confirmation token.
Source text
SKILL.md · MIT
---
name: unharness
license: MIT
description: >-
Safely leave Citadel using the active adoption receipt. Produces a no-write,
reviewable plan, preserves a portable archive, removes only exact owned
material, and reports modified or externally registered surfaces as retained
or unknown. Legacy installs must be imported before exact leave is claimed.
user-invocable: true
auto-trigger: false
trigger_keywords:
- unharness
- remove citadel
- uninstall citadel
- clean up citadel
- remove harness
- uninstall harness
last-updated: 2026-07-30
---
# /unharness - Receipt-owned exit from Citadel
## Orientation
Use this skill when the user wants Citadel removed from a project. Exit is a
two-step, receipt-owned operation. A plan never mutates the project. Apply
requires the exact saved plan and its confirmation token.
Do not infer ownership from familiar paths. Do not delete `.planning/`,
`.citadel/`, runtime settings, hooks, skills, or registrations merely because
they look Citadel-related.
## Protocol
### 1. Locate Citadel and inspect adoption authority
Read `.citadel/plugin-root.txt` when present. Otherwise use the directory
containing this skill. Check for `.citadel/adoption/active.json`; the adoption
planner also checks the private recovery ledger.
### 2. Create a no-write leave plan
Choose a plan path inside the project, such as
`.planning/adoption/leave.plan.json`, and run:
```bash
node {citadelRoot}/scripts/adopt.js leave plan \
--target {projectRoot} \
--out {planPath} \
--json
```
Show the user:
- exact files that will be removed or restored;
- modified or ambiguous footprint entries that will be retained;
- portable archive path;
- runtime registrations whose removal evidence is `unknown`;
- the plan digest and confirmation token.
If the result is `NOT_ADOPTED`, stop. Create a conservative legacy inventory:
```bash
node {citadelRoot}/scripts/adopt.js import plan {citadelRoot} \
--target {projectRoot} \
--out {importPlanPath} \
--json
```
Apply that import only after its own explicit approval. Then create a new leave
plan from the resulting receipt. Never describe legacy cleanup as exact
removal.
### 3. Obtain explicit approval
Leaving is destructive. Ask the user to approve the displayed plan and exact
confirmation token. Do not apply from an unsaved or regenerated plan.
### 4. Apply and verify
After approval:
```bash
node {citadelRoot}/scripts/adopt.js leave apply {planPath} \
--confirm {confirmationToken} \
--json
node {citadelRoot}/scripts/adopt.js doctor \
--target {projectRoot} \
--json
```
Doctor may report `not_adopted` after a clean leave. Report the leave receipt,
archive path, removed entries, retained conflicts, and every `unknown`
unregistration observation. “Citadel removed” is permitted only when the
receipt proves every required local and external removal.
## Export-only compatibility
When the user explicitly wants a human-readable export without leaving:
```bash
node {citadelRoot}/scripts/unharness.js {projectRoot} --export-only
```
This writes the legacy Markdown archive but does not remove harness material.
## Fringe Cases
- If `.planning/` does not exist, treat it as an empty portable-state set and
show the setup/import hint; do not create it merely to leave.
- Missing or invalid adoption authority blocks leave. Use `import plan` or
private-ledger recovery; never guess ownership.
- A changed saved plan, source, target, or pre-image requires a fresh plan.
- An unavailable runtime unregister API stays `unknown`; report the manual
observation required.
- If the Citadel root cannot be located, stop with the exact missing path.
## Quality gates
- Planning is read-only unless the user explicitly requests `--out`.
- Apply consumes the exact saved plan and revalidates source, target, and
pre-images.
- Modified owned material is retained with an explicit conflict.
- Shared runtime files restore exact pre-images only while installed bytes
remain exact.
- Missing receipts, malformed receipts, and unenumerable registrations are
`unknown` or blocked, never successful.
- The portable archive and private receipt ledger remain available for restore
and recovery.
## Exit Protocol
Return the leave operation ID and receipt digest, portable archive path, exact
removed/restored counts, retained conflicts, and unknown external removals.
State plainly whether exact exit was proved. Do not claim success from a
completed command when required removal evidence is missing.
© SethGammon · MIT · SethGammon/Citadel