agent-severance

# Agent Severance Skill Orgs learned employee offboarding the hard way: the contractor whose VPN worked for a year after the contract, the shared password nobody rotated. Long-lived agents recreate every one of those failure modes with worse logging — an agent accumulates credentials, memory, integrations, scheduled jobs, and undocumented responsibilities, and then one day it's "turned off" by deleting a chat window while its API keys live on. This skill runs the severance properly: know what it had, keep what's valuable, kill what's live, and hand over what it did. ## What This Skill Produces - An **inventory**: everything the agent could touch (credentials, tools, data stores, channels), everything it knew (memory, context files, fine-tuning or instructions), and everything it *did on a schedule* - An **access-revocation table** with owner and verification step per row — revoked isn't revoked until someone confirmed the key is dead - A **memory disposition record**: exported / retained (where, why, how long) / purged (how verified) — the part compliance will ask about in 2027 - A **successor handover**: the agent's actual duties, including the undocumented ones users discovered, for whoever inherits them ## Required Inputs Ask for (if not already provided): - The agent: platform, what it was for, how long it ran, who owned it - Known integrations and credentials (then treat the list as incomplete on principle — the inventory step hunts for the rest) - Why i...