Delete or retire a Tessl skill: unpublish, remove dependencies, delete directory, re-install.
94
94%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Fully remove a skill from the Tessl ecosystem.
ONLY publish to
ambabaworkspace. Alltessl tilecommands MUST use--workspace ambaba. NEVER lose content during retirement merges. Verify target has all source knowledge first. NEVER delete without explicit user confirmation. Present what will be removed and wait for "yes".
Read ~/.claude/memory/brain-topology.md "Synapses IN". If other skills delegate to target, warn and list callers.
tessl tile list --workspace ambaba | grep <skill-name>
tessl tile unpublish --tile ambaba/<skill-name>@<version> # 2-day window
tessl tile delete --tile ambaba/<skill-name> # if unpublish fails
tessl tile archive --tile ambaba/<skill-name> # fallbackIf never published (local-only), skip.
~/.tessl/tessl.jsonrm -rf ~/.claude/skills/<skill-name>Remove from tables, add to Prune Log with date/name/action/reason.
grep -rl '<skill-name>' ~/.claude/skills/*/SKILL.md — warn if found.
tessl install --globalConfirm skill gone from registry, tessl.json, skills dir, topology, and other skills.
Delegate →
tessl__skill-retirer-checklistfor retirement checklist, error recovery, and batch mode.