unharness

Removes Citadel from a project using receipt-owned plans with explicit approval and verification.

916|82|Updated Mar 20, 2026
One-click install
npx skills add https://github.com/SethGammon/Citadel --skill unharness
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: unharness
Source: https://github.com/SethGammon/Citadel/tree/main/skills/unharness
Command: npx skills add https://github.com/SethGammon/Citadel --skill unharness

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Removing a coding-agent operating layer like Citadel by hand risks deleting files you do not own, leaving orphaned hooks and registrations, or destroying state you later need. This Skill performs a safe, receipt-owned exit: it plans removal without writing anything, requires explicit approval, and proves exactly what was removed, retained, or left unknown.

Core Features & Use Cases

  • No-write leave planning: Generates a reviewable plan listing exact files to remove or restore, modified entries to retain, and a portable archive path before any change occurs.
  • Receipt-owned apply with confirmation token: Applies only the exact saved plan after explicit user approval, revalidating source, target, and pre-images, then runs a doctor check to verify the result.
  • Legacy install handling: Detects non-adopted (legacy) installs, requires an import plan with its own approval first, and never claims exact removal without receipt evidence.
  • Use Case: You installed Citadel in a repository and now want it gone. The Skill shows you the exact removal plan and archive location, waits for your approval token, removes only owned material, and reports retained conflicts and unknown external registrations.

Quick Start

Ask the agent to unharness Citadel from this project and show me the removal plan before deleting anything.

Frequently Asked Questions about unharness

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I uninstall Citadel from my repository?

Run the unharness skill, which first creates a no-write leave plan listing exact files to remove or restore. After you approve the plan with its confirmation token, it applies the removal and verifies the result with a doctor check.

How do I remove Citadel if it was installed before adoption receipts existed?

Legacy installs return NOT_ADOPTED, so the skill creates a conservative import plan that must be explicitly approved first. Only after importing can a new leave plan claim exact removal; legacy cleanup is never described as exact removal.

Does uninstalling Citadel delete my .planning or .citadel directories automatically?

No. The skill never infers ownership from familiar paths and removes only exact owned material proven by the adoption receipt. Modified or ambiguous entries are retained and reported as explicit conflicts.

Can I export my Citadel state without uninstalling it?

Yes. Running the export-only mode writes a human-readable Markdown archive of the harness state without removing any material, useful for review or migration purposes.

What happens if the adoption receipt is missing or invalid?

Missing or malformed adoption authority blocks the leave operation entirely. The skill falls back to an import plan or private-ledger recovery and never guesses ownership or claims success without evidence.