What problem does it solve? Uninstalling an agent capability by hand leaves behind cron jobs, symlinks, marker blocks, config keys, and orphaned agents scattered across your harness. This Skill removes an installed aos capability exactly and completely by walking its recorded lockfile entry backwards, so nothing is left behind and removal is verifiable. ## Core Features & Use Cases - Lockfile-driven removal: Reads the capability's recorded artifacts, links, schedules, config keys, and scripts via aos-cap show, then un-writes each one in the correct order. - Scoped or whole removal: Supports removing a capability from a single harness while it stays installed elsewhere, or removing it entirely across all harnesses. - Safety checks: Detects dependent capabilities before removal, preserves the user's personalized MOD.md answers, and asks before deleting machine-local state like kb-principal.yml. - Use Case: You installed a knowledge-base capability months ago and no longer use it. Ask your agent to remove it, and it deletes the jobs, symlinks, marker blocks, and tool binary, verifies nothing remains, and confirms your personalization file survives for a future reinstall. ## Quick Start Tell your agent to remove the installed capability by name, for example: remove the kb capability from my harness.
