Agent skill

When Someone Dies

by mohitagw15856 in mohitagw15856/pm-claude-skills

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.

MITAuto-check passed

Install When Someone Dies

skills CLI
$ npx skills add mohitagw15856/pm-claude-skills --skill when-someone-dies -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install mohitagw15856/pm-claude-skills when-someone-dies --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/when-someone-dies .claude/skills/when-someone-dies && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
when-someone-dies
GitHub stars
1.4k
Token cost
~1.6k tokens
SKILL.md length
833 words
Files
1
Skills in repo
1,348
Repo updated
First seen
Licence
MIT

At a glance

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.

  • Works in 5 steps: Today is smaller than it feels: the… → This week: the funeral home /… → The notification cascade has an order:… → …
  • Asked someone just died what do I do
  • SKILL.md covers What This Skill Produces, Required Inputs, Framework: The Triage Rules and Output Format, plus 7 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

When Someone Dies is an agent skill from mohitagw15856/pm-claude-skills. 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…

Its SKILL.md is about 1.6k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

The repository describes itself as: 1255 professional Agent Skills for Claude, ChatGPT, Gemini, Cursor & Codex — PRDs, postmortems, leases, medical bills, layoffs, go-bags, new countries. Plain markdown, MIT, in… The licence is MIT.

When your agent uses it

  • Asked someone just died what do I do
  • Checklist after a death
  • Help me handle my parents affairs
  • What needs to happen this week

Example prompts

  • “/when-someone-dies”

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. Today is smaller than it feels: the legal pronouncement and transport (the institution largely drives this), care of dependents and pets…
  2. This week: the funeral home / arrangements conversation (bring someone; decisions made alone in grief get upsold — the [funeral-cost…
  3. The notification cascade has an order: family → employer → the estate's professionals (attorney/executor) → government agencies and…
  4. The should-wait list is protective, not lazy: selling the house, large distributions, paying most non-secured claims, moving in/out…
  5. The reader is not okay, and the artifact knows it: every list is short, sequenced, and delegation-ready ("hand this section to your…

What it can do on your machine

Read from SKILL.md and the folder at commit 1cbf1f0. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

When Someone Dies loads about 1.6k tokens when it runs. Until then it costs about 143 tokens; SKILL.md has 833 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~143
When it runs · the whole SKILL.md, loaded when a task matches
~1.6k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from mohitagw15856/pm-claude-skills at commit 1cbf1f0, republished under its MIT licence (© mohitagw15856). 833 words, ~1,605 tokens.

Download SKILL.mdSave it as .claude/skills/when-someone-dies/SKILL.md (or your agent's skills folder).
name
when-someone-dies
description
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.

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

Required Inputs

Ask for these if not provided:

  • The relationship and the role — next of kin? named executor? helpful sibling? The task list differs sharply by role, and doing another role's tasks creates real problems
  • The situation basics — where it happened (home/hospital/hospice changes the first hours), whether arrangements exist (pre-plan, known wishes, nothing), and the country/region — death administration is deeply jurisdiction-specific; this skill sequences the universal shape and flags every local step as verify-locally
  • The household reality — dependents, pets, an empty home, urgent bills that genuinely can't wait

Framework: The Triage Rules

  1. Today is smaller than it feels: the legal pronouncement and transport (the institution largely drives this), care of dependents and pets, securing the home if now empty, and telling the innermost circle. That's the list. Everything else pitching itself as today is grief wearing a clipboard.
  2. This week: the funeral home / arrangements conversation (bring someone; decisions made alone in grief get upsold — the [funeral-cost conversation] deserves its own sitting), employer notification, starting the death-certificate order (10–15 certified copies — banks, insurers, registrars, and utilities each want their own; ordering twice takes weeks), locating the will and any pre-arrangements, and beginning the notification cascade with scripts.
  3. The notification cascade has an order: family → employer → the estate's professionals (attorney/executor) → government agencies and pension/benefits providers → financial institutions → the long tail (subscriptions, socials, mail forwarding). Each call answered by "I'll need a certified copy" — which is why the certificates come first.
  4. The should-wait list is protective, not lazy: selling the house, large distributions, paying most non-secured claims, moving in/out — parked for at least a month, both because grief prices badly and because paying the wrong things in the wrong order can create personal liability where none existed (that's the estate process's job — see estate-settlement-organizer).
  5. The reader is not okay, and the artifact knows it: every list is short, sequenced, and delegation-ready ("hand this section to your brother") — the format is the kindness. And one line appears verbatim: you do not have to do all of this, and you do not have to do it alone.
Show full SKILL.md (309 more words)Show less

Output Format

The Next Two Weeks: [name, relationship] — [role]

Today (and only this)

[The 3–5 items · dependents/pets/home lines · who's told first]

This Week

[Arrangements (bring someone) · certificates: order [N] certified copies from [vital records / registrar — verify locally] · will located · employer told · the cascade begun]

The Calls

[Scripts: the hardest family call · the employer call · the institution template: "I'm calling to report the death of [name] on [date]; what does your process require and where do I send the certified copy?"]

This Month / Can Wait / Should Wait

[The parked list, each with why parking it is safe or protective]

Death administration varies by country and region — registration deadlines, who may order certificates, and estate steps are all local; verify each flagged step with the registrar, the institution, or an attorney. You do not have to do all of this, and you do not have to do it alone.

Quality Checks

  • Today's list has ≤5 items and no financial decisions
  • The certificate order (with a number) appears in week one
  • Every institution call routes through the same certified-copy script
  • The should-wait list explains its protective logic
  • Every jurisdiction-specific step carries the verify-locally flag
  • The you-are-not-alone line appears verbatim

Anti-Patterns

  • Do not produce the 90-item master checklist on day one — triage IS the product; the wall of tasks is what this skill replaces
  • Do not let feels-urgent into today — probate, accounts, and the house are week-three-or-later conversations
  • Do not advise paying estate debts or distributing anything — that's the estate process, with its own skill and its own professionals
  • Do not state legal deadlines as universal — flag and route locally
  • Do not write in checklist-cheerful tone — plain, warm, and short; the reader is grieving

Example Trigger Phrases

  • "Someone just died: what do I do?"
  • "Give me a checklist after a death."
  • "Help me handle my parent's affairs."
  • "What needs to happen this week?"

© mohitagw15856, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/when-someone-dies of mohitagw15856/pm-claude-skills.

Open the folder on GitHubat commit 1cbf1f0

Compare with similar skills

When Someone Dies next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

When Someone Dies compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
When Someone Dies this skillmohitagw15856/pm-claude-skills1.4k—~1.6kAutomated safety check: PassMIT
Organizationthedaviddias/Front-End-Checklist74k—~609Automated safety check: PassMIT
Weekly Project Digeststhedotmack/claude-mem99k—~3.5kAutomated safety check: PassApache-2.0
File Organizerdavila7/claude-code-templates33k7 repos~1.6kAutomated safety check: PassMIT
Weekly Review PlanningNousResearch/hermes-agent252k—~994Automated safety check: PassMIT
Weekly Reviewalirezarezvani/claude-skills28k—~1.4kAutomated safety check: PassMIT

Similar skills

  • Organization

    thedaviddias/Front-End-Checklist

    A skill your agent uses when auditing structured data on a business or brand website homepage.

    74k GitHub stars~609 tokensUpdated 4 days ago
    Marketing & SEOAuto-check passed
  • Weekly Project Digests

    thedotmack/claude-mem

    Turns a project's claude-mem timeline into a week-by-week narrative, splitting it by ISO week and running one subagent per week that receives the prior week's carry-forward block.

    99k GitHub stars~3.5k tokensUpdated 2 days ago
    Agent WorkflowsAuto-check passed
  • File Organizer

    davila7/claude-code-templates

    Intelligently organizes files and folders by understanding context, finding duplicates, and suggesting better organizational structures.

    33k GitHub starsUsed in 7 repos~1.6k tokens
    Productivity & AutomationAuto-check passed
  • Weekly Review Planning

    NousResearch/hermes-agent

    Weekly reset: commitments, stalled work, next-week plan. An agent skill from NousResearch/hermes-agent.

    252k GitHub stars~994 tokensUpdated yesterday
    Knowledge ManagementAuto-check passed
  • Weekly Review

    alirezarezvani/claude-skills

    A skill your agent uses when someone wants to run a weekly review, close open loops, audit stalled projects and commitments, get their system back to trusted, restart a lapsed review habit, or says…

    28k GitHub stars~1.4k tokensUpdated 1 mo ago
    Knowledge ManagementAuto-check passed
  • Organize Space

    asgeirtj/system_prompts_leaks

    Organize existing ChatGPT Pages and Space structure when the user requests changes to that structure.

    69k GitHub stars~1.6k tokensUpdated yesterday
    Auto-check passed

More from mohitagw15856/pm-claude-skills

All 1,348 skills in this repo
  • Car Tco

    mohitagw15856/pm-claude-skills

    Compare the total cost of car ownership across buy-new, buy-used, lease, and keep-your-current-car — depreciation, insurance, maintenance ramp, and fuel over a real horizon, not just the monthly…

    1.4k GitHub stars~1.1k tokensUpdated 2 days ago
    Auto-check passed
  • Cs Health Scorecard

    mohitagw15856/pm-claude-skills

    Build a customer health scorecard for a specific account. An agent skill from mohitagw15856/pm-claude-skills.

    1.4k GitHub stars~2.4k tokensUpdated 2 days ago
    Auto-check passed
  • Exit Waterfall

    mohitagw15856/pm-claude-skills

    Compute who gets what at each exit price from a cap table — liquidation preferences, conversion points, and where the founders' share collapses.

    1.4k GitHub stars~1.1k tokensUpdated 2 days ago
    Auto-check passed
  • Feature Prioritisation

    mohitagw15856/pm-claude-skills

    Apply prioritisation frameworks (RICE, MoSCoW, Kano, ICE, Opportunity Scoring) to rank features and backlog items.

    1.4k GitHub stars~2k tokensUpdated 2 days ago
    Auto-check passed
  • Fire Number

    mohitagw15856/pm-claude-skills

    Compute a financial-independence (FIRE) target and years-to-reach with every assumption labeled as an assumption — plus a sensitivity table instead of a single false-precision answer.

    1.4k GitHub stars~1.1k tokensUpdated 2 days ago
    Auto-check passed
  • Freelance Rate

    mohitagw15856/pm-claude-skills

    Derive a freelance day/hourly rate backwards from target income, honest billable utilization, overhead, and the self-employment tax premium — the arithmetic that proves a rate is not salary÷2000.

    1.4k GitHub stars~1.2k tokensUpdated 2 days ago
    Auto-check passed

Questions about When Someone Dies

What does When Someone Dies 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. When Someone Dies is an agent skill from mohitagw15856/pm-claude-skills. 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.

When should I use When Someone Dies?

When Someone Dies fits situations like: asked someone just died what do I do; checklist after a death; help me handle my parents affairs; what needs to happen this week.

How do I install When Someone Dies in Claude Code?

Run `npx skills add mohitagw15856/pm-claude-skills --skill when-someone-dies -a claude-code`. Or copy the skill folder (skills/when-someone-dies in mohitagw15856/pm-claude-skills) into .claude/skills/when-someone-dies in your project. Claude Code loads it when a task matches its description.

How do I install When Someone Dies in Codex?

Run `npx skills add mohitagw15856/pm-claude-skills --skill when-someone-dies -a codex`. Or copy the skill folder (skills/when-someone-dies in mohitagw15856/pm-claude-skills) into .agents/skills/when-someone-dies in your project. Codex loads it when a task matches its description.

Can I use When Someone Dies in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mohitagw15856/pm-claude-skills --skill when-someone-dies -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/when-someone-dies, .gemini/skills/when-someone-dies, .github/skills/when-someone-dies and .opencode/skills/when-someone-dies in your project.

What does When Someone Dies need to run?

SKILL.md names no scripts, command-line tools or credentials: When Someone Dies is instructions for the agent only.

Does When Someone Dies access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is When Someone Dies safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does When Someone Dies use?

When Someone Dies is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does When Someone Dies use?

About 1.6k tokens (SKILL.md is roughly 6.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to When Someone Dies?

Skills that share tags, products or a category with When Someone Dies: Organization (thedaviddias/Front-End-Checklist, 74k stars), Weekly Project Digests (thedotmack/claude-mem, 99k stars), File Organizer (davila7/claude-code-templates, 33k stars) and Weekly Review Planning (NousResearch/hermes-agent, 252k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains When Someone Dies?

mohitagw15856 (a GitHub user) maintains it in mohitagw15856/pm-claude-skills, which has 1,434 GitHub stars. The repository holds 1,348 skills in this directory. The repository was last updated on October 9, 2026.

Source: mohitagw15856/pm-claude-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.