Agent skill · Workflow & Productivity

when-someone-dies

The first two weeks after a death, organized — what genuinely needs doing now, what only feels urgent, who to notify in what order, and the documents everything else will require. Use when asked someone just died what do I do, checklist after a death, help me handle my parent's affairs, or what needs to happen this week. Produces the triaged timeline (today / this week / can wait), the notification order, the death-certificate math, and the scripts for the hardest calls — written for someone who cannot think straight, because that's who's reading.

mohitagw158561,255★ · 1 repos on radarProfile →
claude-codecursorMIT
Install
npx skills add mohitagw15856/pm-claude-skills --skill when-someone-dies --agent claude-code

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

Facts
Files in the skill folder: 1
SKILL.md size: 6 KB
Bundled scripts: none
Path: skills/when-someone-dies/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

# When Someone Dies Skill Grief and logistics arrive together, and the logistics are designed for someone at their sharpest handed to someone at their worst. The merciful truth this skill is built on: **almost nothing is as urgent as it feels.** A handful of things genuinely need doing in the first days; most can wait weeks; some *should* wait (major financial decisions have no place in the first month). This skill triages the chaos into today / this week / can-wait, provides the call scripts, and repeats the one logistical rule everyone learns too late: order more death certificates than seems reasonable. ## What This Skill Produces - **The triaged timeline** — today, this week, this month, can-wait-and-should — with the feels-urgent-but-isn't items explicitly parked - **The notification order** — who must be told, by whom, in what sequence, with scripts for the hardest ones - **The document engine** — death certificates (how many, from where), and the papers every later step will demand - **The protection list** — the immediate steps that prevent problems (securing the home, mail, subscriptions-becoming-fraud-vectors) without touching anything that belongs to the estate process #

What's inside
Steps it walks through
  1. What This Skill Produces
  2. Required Inputs
  3. Framework: The Triage Rules
  4. Output Format
  5. Today (and only this)
  6. This Week
  7. The Calls
  8. This Month / Can Wait / Should Wait
  9. Quality Checks
  10. Anti-Patterns
More from pm-claude-skills
All skills →
About this skill
What does the when-someone-dies skill do?

The first two weeks after a death, organized — what genuinely needs doing now, what only feels urgent, who to notify in what order, and the documents everything else will require. Use when asked someone just died what do I do, checklist after a death, help me handle my parent's affairs, or what needs to happen this week. Produces the triaged timeline (today / this week / can wait), the notification order, the death-certificate math, and the scripts for the hardest calls — written for someone who cannot think straight, because that's who's reading.

How do I install it?

Run `npx skills add mohitagw15856/pm-claude-skills --skill when-someone-dies --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