From pm-layoff
The first-72-hours money plan after a layoff — runway computed, deadlines caught, bleeding stopped, in priority order. Use when asked I just got laid off what do I do about money, build my layoff budget, how long can I last, or what needs to happen this week. Produces the runway number, the deadline list (healthcare, unemployment filing, equity exercise windows), the spending triage, and a one-week action checklist.
How this skill is triggered — by the user, by Claude, or both
Slash command
/pm-layoff:layoff-financial-triageThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
The first week after a layoff has three jobs: know the runway number, catch the deadlines that expire silently, and stop the optional bleeding. Grief and job-searching come after solvency. This skill runs the triage in that order — numbers first, calmly, with dates.
The first week after a layoff has three jobs: know the runway number, catch the deadlines that expire silently, and stop the optional bleeding. Grief and job-searching come after solvency. This skill runs the triage in that order — numbers first, calmly, with dates.
Ask for these if not provided:
subscription-auditor) · Cancel/renegotiate (the discretionary layer). Total the recovery per month.severance-agreement-decoder), then gig/contract stopgaps.Runway: [n.n] months at triage spending ([current] → [triage] $/mo)
| Deadline | Date | What expires | Action |
|---|
| Item | $/mo | Verdict | Note | Recovered: $[n]/mo → runway extends to [n.n] months
[The panic moves, each with its real cost]
Mon: … Tue: … (file unemployment day 1–2, always)
npx claudepluginhub mohitagw15856/pm-claude-skills --plugin pm-layoffGuides creation and editing of skills using test-driven development with pressure scenarios and subagents to verify agent compliance.
Forks private projects, strips secrets/internal references, verifies cleanliness, and packages them with CLAUDE.md, README, and setup.sh for safe public release.