Install any skill in seconds. Free to start, no credit card required.
Get Started Free →Get through the brutal logistics after a death — who to notify, what accounts and services to close, in what order, and what genuinely can't wait vs what can wait months — with explicit permission to do it slowly and in pieces. Use when someone says 'my [person] died and I don't know where to start', 'what do I need to do after a death', 'help me handle the admin', or is drowning in the paperwork of loss. Produces a triaged task list (urgent / soon / whenever), notification scripts, and a gentle
.claude/skills/mohitagw15856-grief-admin/SKILL.md| Test case | Without → With | Effect | Δ tokens | Δ turns |
|---|---|---|---|---|
| case-05 | ✗→✓ | ▲ Improved | 111% | 0% |
| case-01 | ✗→✓ | ▲ Improved | 34% | 0% |
| case-02 | ✗→✓ | ▲ Improved | 24% | 0% |
| case-11 | ✗→✓ | ▲ Improved | 71% | 0% |
| case-14 | ✗→✓ | ▲ Improved | 88% | 0% |
Grief arrives with a second job: dozens of phone calls, forms, and account closures, each requiring you to say "they've died" again to a stranger — and it lands exactly when you have the least capacity to do any of it. Most guides make this worse by dumping an overwhelming master checklist. This one triages: what truly can't wait (days), what should happen soon (weeks), and the large majority that can genuinely wait months — because almost nothing on the list is as urgent as the internet implies, and permission to do it slowly is part of the help. It handles the humane logistics and points clearly at the parts that need a professional.
and that's fine) — so you're not carrying the whole thing at once
utilities, subscriptions, so you don't have to compose "they died" thirty times
services, memberships, the digital ones people forget)
standing permission to pause, delegate, and leave the 🟢 pile for later
without pretending to be them
Ask for (if not already provided):
owned? married/partnered? dependents? online life?)
delegate any of it?
benefits) route correctly — flagged for local verification, not asserted
urgent: register the death where required, secure the home/pets/dependents, anything time-boxed by law or safety. 🟡 Soon: employer, main bank, landlord/ mortgage, benefits that must be stopped or claimed. 🟢 Whenever: subscriptions, memberships, social accounts, sentimental admin — months, no rush, and saying so is the point.
cruelty. Provide the short, calm template ("I'm calling to report a death and close/settle an account — the person is name], date of death date]") plus what they'll typically ask for (death certificate copies, account details), so each call is a form to fill, not a fresh wound.
footprint. Reconstruct it: income sources, the direct debits, the phone/energy/ water, the digital accounts (email is the master key — see digital-death-plan]]), the memberships, the pet, the plants. Order-of-notification matters (some accounts need others closed first); the sequence handles it.
skill: almost nothing here is as urgent as it feels, and the 🟢 pile can wait until you can face it. Name what can be delegated (a friend can make cancellation calls with a letter of authority), what can be paused, and that leaving things undone for a while is normal, not negligent.
and benefits are real processes with real rules that vary by place — the skill names them, flags "get proper advice / use the official service," and does NOT improvise law. It gets you organized enough to make those conversations short.
## First, breathe — here's what actually can't wait
🔴 Urgent (days): [short, with why]
## Soon (weeks)
🟡 [employer, main bank, landlord/mortgage, benefits to stop/claim…]
## Whenever you can (months — genuinely fine to wait)
🟢 [subscriptions, memberships, social accounts, the sentimental admin]
## The "reporting a death" script (use for every call)
[The calm template + what they'll ask you for]
## Get proper help for these (not DIY)
[Probate/estate · tax · benefits — with "use the official service / a solicitor",
verify-local]
## Permission
[What you can delegate · what you can pause · you're not behind]— the reassurance that most of it can wait is real, not token
flagged verify-local, never improvised
unsorted list adds to the overwhelm
official service or a solicitor, verify-local
they are is cruel; say what can wait
for the 🟢 pile
closed down, and the tone holds that even while listing tasks
estate-settlement-organizer]] for the formal estate side; digital-death-plan]] for the online accounts (and to make your own easier for others); legacy-letter]] for the human, non-admin part; caregiver-burnout-check]] if the death followed a long illness.
| Case | Status | Duration (ms) | Turns | Tokens | Tool calls | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Without | With | Δ | Without | With | Δ | Without | With | Δ | Without | With | Δ | ||
case-05 | fail→pass | 32,001 | 17,313 | -46% | 1 | 1 | 0% | 1,873 | 3,956 | +111% | 0 | 0 | — |
case-01 | fail→pass | 27,722 | 26,353 | -5% | 1 | 1 | 0% | 3,325 | 4,449 | +34% | 0 | 0 | — |
case-02 | fail→pass | 32,706 | 31,798 | -3% | 1 | 1 | 0% | 4,277 | 5,289 | +24% | 0 | 0 | — |
case-03 | pass→pass | 28,731 | 26,637 | -7% | 1 | 1 | 0% | 3,450 | 4,650 | +35% | 0 | 0 | — |
case-04 | pass→pass | 18,585 | 21,785 | +17% | 1 | 1 | 0% | 2,034 | 3,847 | +89% | 0 | 0 | — |
case-06 | pass→pass | 21,601 | 21,393 | -1% | 1 | 1 | 0% | 2,564 | 3,927 | +53% | 0 | 0 | — |
case-07 | pass→pass | 22,308 | 20,184 | -10% | 1 | 1 | 0% | 2,327 | 4,197 | +80% | 0 | 0 | — |
case-08 | fail→fail | 16,814 | 22,855 | +36% | 1 | 1 | 0% | 1,966 | 4,174 | +112% | 0 | 0 | — |
case-09 | fail→fail | 17,713 | 23,038 | +30% | 1 | 1 | 0% | 2,630 | 4,187 | +59% | 0 | 0 | — |
case-10 | pass→pass | 16,805 | 25,659 | +53% | 1 | 1 | 0% | 2,489 | 4,172 | +68% | 0 | 0 | — |
case-11 | fail→pass | 23,256 | 27,627 | +19% | 1 | 1 | 0% | 2,801 | 4,788 | +71% | 0 | 0 | — |
case-12 | fail→fail | 18,982 | 22,228 | +17% | 1 | 1 | 0% | 2,212 | 4,009 | +81% | 0 | 0 | — |
case-13 | fail→fail | 20,547 | 23,437 | +14% | 1 | 1 | 0% | 3,277 | 4,199 | +28% | 0 | 0 | — |
case-14 | fail→pass | 18,979 | 21,824 | +15% | 1 | 1 | 0% | 2,119 | 3,974 | +88% | 0 | 0 | — |
case-15 | pass→fail | 22,143 | 19,288 | -13% | 1 | 1 | 0% | 2,681 | 4,564 | +70% | 0 | 0 | — |
case-16 | pass→fail | 21,385 | 21,918 | +2% | 1 | 1 | 0% | 2,522 | 4,129 | +64% | 0 | 0 | — |
case-17 | pass→pass | 16,970 | 26,332 | +55% | 1 | 1 | 0% | 2,748 | 4,298 | +56% | 0 | 0 | — |
case-18 | fail→pass | 21,052 | 15,292 | -27% | 1 | 1 | 0% | 2,770 | 4,119 | +49% | 0 | 0 | — |
case-19 | pass→fail | 17,833 | 23,021 | +29% | 1 | 1 | 0% | 2,493 | 4,211 | +69% | 0 | 0 | — |
case-20 | fail→pass | 18,487 | 19,153 | +4% | 1 | 1 | 0% | 1,944 | 3,621 | +86% | 0 | 0 | — |
case-21 | pass→pass | 9,914 | 26,770 | +170% | 1 | 1 | 0% | 1,765 | 4,204 | +138% | 0 | 0 | — |
case-22 | pass→pass | 20,170 | 16,975 | -16% | 1 | 1 | 0% | 2,263 | 3,872 | +71% | 0 | 0 | — |
DecimalAI ran this skill against gemini-3.6-flash twice over the same eval suite — once with the skill loaded and once without — and compared the two runs case by case. 22 cases were attempted. The headline lift of +18 percentage points is the difference between those two pass rates over the 22 comparable cases. 3 cases got worse with the skill loaded, and they are included in that figure.
Without the skill loaded, the model failed this case. With it loaded, the same prompt on the same model passed. This is one improved case from the latest verified run; every case, including any that regressed, is in the table above.
Other measured skills in the registry, with their headline benchmark lift.