Agent skill

Grief Admin

by mohitagw15856 in mohitagw15856/pm-claude-skills

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…

MITAuto-check passedAgent Workflows

Install Grief Admin

skills CLI
$ npx skills add mohitagw15856/pm-claude-skills --skill grief-admin -a claude-code

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

GitHub CLI
$ gh skill install mohitagw15856/pm-claude-skills grief-admin --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/grief-admin .claude/skills/grief-admin && 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
grief-admin
GitHub stars
1.4k
Token cost
~1.7k tokens
SKILL.md length
811 words
Files
1
Skills in repo
1,348
Repo updated
First seen
Licence
MIT

At a glance

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…

  • Works in 5 steps: Triage hard — most of it can wait. The… → Script the "they died" call once. The… → Build the list from THIS life. Generic… → …
  • Someone says my [person] died and I dont know where to start
  • SKILL.md covers What This Skill Produces, Required Inputs, Framework and Output Format, plus 4 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Grief Admin is an agent skill from mohitagw15856/pm-claude-skills. 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 sequence. Not…

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

It sits in Agent Workflows, covering Task breakdown. 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

  • Someone says my [person] died and I dont know where to start
  • What do I need to do after a death
  • Help me handle the admin
  • Is drowning in the paperwork of loss

Example prompts

  • “my [person] died and I don”
  • “what do I need to do after a death”
  • “help me handle the admin”
  • “/grief-admin”

Workflow steps

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

  1. Triage hard — most of it can wait. The relief is in the sorting. 🔴 Truly
  2. Script the "they died" call once. The repeated disclosure is a specific
  3. Build the list from THIS life. Generic checklists miss the person's actual
  4. Permission to go slow and delegate. The most useful sentence in the whole
  5. Hand off the professional parts cleanly. Probate/estate administration, tax,

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

Grief Admin loads about 1.7k tokens when it runs. Until then it costs about 153 tokens; SKILL.md has 811 words of instructions outside code blocks.

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

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). 811 words, ~1,698 tokens.

Download SKILL.mdSave it as .claude/skills/grief-admin/SKILL.md (or your agent's skills folder).
name
grief-admin
description
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 sequence. Not legal or tax advice — the humane logistics, with pointers to the professional bits.

Grief Admin Skill

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.

What This Skill Produces

  • A triaged task list: 🔴 urgent (days) · 🟡 soon (weeks) · 🟢 whenever (months, and that's fine) — so you're not carrying the whole thing at once
  • Notification scripts: the short, kind phone/email lines for banks, employers, utilities, subscriptions, so you don't have to compose "they died" thirty times
  • A who-to-tell-and-close list built for this person's actual life (accounts, services, memberships, the digital ones people forget)
  • A do-it-in-pieces sequence: the order that reduces stress, with the explicit standing permission to pause, delegate, and leave the 🟢 pile for later
  • Clear hand-offs to the professional bits (probate/estate, tax, benefits) without pretending to be them

Required Inputs

Ask for (if not already provided):

  • The relationship to the person and the rough shape of their life (worked? rented/ owned? married/partnered? dependents? online life?)
  • What's already been handled (death certificate, funeral) and what's looming
  • The user's own state and support — are they doing this alone, exhausted, able to delegate any of it?
  • Country/region, so the professional-process pointers (registration, probate, benefits) route correctly — flagged for local verification, not asserted

Framework

  1. Triage hard — most of it can wait. The relief is in the sorting. 🔴 Truly 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.
  2. Script the "they died" call once. The repeated disclosure is a specific 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.
  3. Build the list from THIS life. Generic checklists miss the person's actual 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.
  4. Permission to go slow and delegate. The most useful sentence in the whole 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.
  5. Hand off the professional parts cleanly. Probate/estate administration, tax, 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.
Show full SKILL.md (237 more words)Show less

Output Format

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

Quality Checks

  • The list is triaged into days/weeks/months, and the 🟢 pile is genuinely large — the reassurance that most of it can wait is real, not token
  • The reporting-a-death script exists so the user composes it once, not thirty times
  • The task list reflects this person's actual life, including digital accounts
  • Legal/tax/benefits/probate are handed to professionals and the official process, flagged verify-local, never improvised
  • Explicit permission to go slow and delegate is present and prominent

Anti-Patterns

  • Do not dump an undifferentiated master checklist — the triage IS the help; an unsorted list adds to the overwhelm
  • Do not give legal, tax, or probate advice — name the process, route to the official service or a solicitor, verify-local
  • Do not manufacture urgency — most tasks aren't time-critical, and pretending they are is cruel; say what can wait
  • Do not rush the person or imply they're behind — grief has no admin deadline for the 🟢 pile
  • Do not forget the person's dignity in the logistics — this is a life being 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.

Example Trigger Phrases

  • "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."

© 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/grief-admin of mohitagw15856/pm-claude-skills.

Open the folder on GitHubat commit 1cbf1f0

Compare with similar skills

Grief Admin 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.

Grief Admin compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Grief Admin this skillmohitagw15856/pm-claude-skills1.4k—~1.7kAutomated safety check: PassMIT
MemPalace Task HandoffMemPalace/mempalace59k—~1.9kAutomated safety check: PassMIT
Planning And Task Breakdownabashev/vfs-s31068 repos~1.9kAutomated safety check: PassApache-2.0
Incremental Implementationaddyosmani/agent-skills103k1 repos~2.3kAutomated safety check: PassMIT
ULW Plan Workflowcode-yeongyu/oh-my-openagent70k—~3.9kAutomated safety check: PassCustom licence
Ask NavigatorYeachan-Heo/oh-my-claudecode40k—~4.1kAutomated safety check: PassMIT

Similar skills

  • MemPalace Task Handoff

    MemPalace/mempalace

    Creates, hands off, claims, executes and closes agent tasks through the MemPalace logstream, with approval of the exact task before it is recorded.

    59k GitHub stars~1.9k tokensUpdated 2 days ago
    Agent WorkflowsAuto-check passed
  • Breaks work into ordered tasks. An agent skill from abashev/vfs-s3.

    106 GitHub starsUsed in 8 repos~1.9k tokens
    Agent WorkflowsAuto-check passed
  • Incremental Implementation

    addyosmani/agent-skills

    Delivers a change in thin vertical slices, each implemented, tested, verified and committed before the next, using vertical, contract-first or risk-first slicing.

    103k GitHub starsUsed in 1 repo~2.3k tokens
    Agent WorkflowsAuto-check passed
  • ULW Plan Workflow

    code-yeongyu/oh-my-openagent

    Explore-first planning that turns a vague or large request into one decision-complete work plan, written only after your approval and executed by a separate worker.

    70k GitHub stars~3.9k tokensUpdated today
    Agent WorkflowsAuto-check passed
  • Ask Navigator

    Yeachan-Heo/oh-my-claudecode

    Charts a foggy effort into a map of decision tickets on the repo's issue tracker and works through them one per session, producing decisions rather than deliverables.

    40k GitHub stars~4.1k tokensUpdated yesterday
    Agent WorkflowsAuto-check passed
  • Implementation Plan Creator

    tailcallhq/forgecode

    Writes a structured Markdown implementation plan with checkbox tasks, verification criteria and risks, then checks it with a validation script; no code changes.

    7.6k GitHub starsUsed in 1 repo~1.1k tokens
    Agent WorkflowsAuto-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 yesterday
    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 yesterday
    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 yesterday
    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 yesterday
    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 yesterday
    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 yesterday
    Auto-check passed

Categories

Questions about Grief Admin

What does Grief Admin do?

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

When should I use Grief Admin?

Grief Admin fits situations like: someone says my [person] died and I dont know where to start; what do I need to do after a death; help me handle the admin; is drowning in the paperwork of loss.

How do I install Grief Admin in Claude Code?

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

How do I install Grief Admin in Codex?

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

Can I use Grief Admin 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 grief-admin -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/grief-admin, .gemini/skills/grief-admin, .github/skills/grief-admin and .opencode/skills/grief-admin in your project.

What does Grief Admin need to run?

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

Does Grief Admin 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 Grief Admin 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 Grief Admin use?

Grief Admin 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 Grief Admin use?

About 1.7k tokens (SKILL.md is roughly 6.8k 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 Grief Admin?

Skills that share tags, products or a category with Grief Admin: MemPalace Task Handoff (MemPalace/mempalace, 59k stars), Planning And Task Breakdown (abashev/vfs-s3, 106 stars), Incremental Implementation (addyosmani/agent-skills, 103k stars) and ULW Plan Workflow (code-yeongyu/oh-my-openagent, 70k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Grief Admin?

mohitagw15856 (a GitHub user) maintains it in mohitagw15856/pm-claude-skills, which has 1,433 GitHub stars. The repository holds 1,348 skills in this directory. The repository was last updated on October 8, 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.