Agent skill · Workflow & Productivity

agent-severance

Offboard an AI agent the way you'd offboard an employee — inventory what it knew and touched, export then purge its memory, revoke every credential and access grant, and write the handover for its successor (human or agent). Use when decommissioning an agent or bot, switching agent vendors, ending an AI pilot, or when someone asks 'what did this thing have access to?'. Produces a severance checklist, an access-revocation table, a memory disposition record, and a successor handover.

mohitagw15856github.com/mohitagw15856GitHub ↗
claude-codecursorMIT
Install
npx skills add mohitagw15856/pm-claude-skills --skill agent-severance --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 5 KB
Bundled scripts: none
Path: skills/agent-severance/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 1,255
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# 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,

What's inside
Steps it walks through
  1. What This Skill Produces
  2. Required Inputs
  3. Process
  4. Output Format
  5. Quality Checks
  6. Anti-Patterns
  7. Related
More from pm-claude-skills
All skills →
About this skill
What does the agent-severance skill do?

Offboard an AI agent the way you'd offboard an employee — inventory what it knew and touched, export then purge its memory, revoke every credential and access grant, and write the handover for its successor (human or agent). Use when decommissioning an agent or bot, switching agent vendors, ending an AI pilot, or when someone asks 'what did this thing have access to?'. Produces a severance checklist, an access-revocation table, a memory disposition record, and a successor handover.

How do I install it?

Run `npx skills add mohitagw15856/pm-claude-skills --skill agent-severance --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From mohitagw15856/pm-claude-skills, a repository with 1,255 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going