agent-severance

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