Agent skill

Digital Death Plan

by mohitagw15856 in mohitagw15856/pm-claude-skills

Plan what happens to your digital life when you die — accounts, photos, passwords, money, and social profiles — so someone you trust can actually find, access, memorialize, or close them without a…

MITAuto-check passed

Install Digital Death Plan

skills CLI
$ npx skills add mohitagw15856/pm-claude-skills --skill digital-death-plan -a claude-code

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

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

At a glance

Plan what happens to your digital life when you die — accounts, photos, passwords, money, and social profiles — so someone you trust can actually find, access, memorialize, or close them without a…

  • Works in 5 steps: Email is the master key — start there.… → Sort assets by desired outcome, not by… → Use the legitimate rails, not… → …
  • Someone says what happens to my accounts when I die
  • 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

Digital Death Plan is an agent skill from mohitagw15856/pm-claude-skills. Plan what happens to your digital life when you die — accounts, photos, passwords, money, and social profiles — so someone you trust can actually find, access, memorialize, or close them without a legal nightmare. Use when someone says 'what happens to my accounts when I die', 'digital legacy', 'help my family access my stuff if something happens', or is doing estate planning and forgot the online half. Produces a digital asset inventory, an access plan using built-in legacy tools, and instructions for your…

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.

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 what happens to my accounts when I die
  • Help my family access my stuff if something happens
  • Is doing estate planning and forgot the online half

Example prompts

  • “what happens to my accounts when I die”
  • “digital legacy”
  • “help my family access my stuff if something happens”
  • “/digital-death-plan”

Workflow steps

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

  1. Email is the master key — start there. Whoever controls the primary email can
  2. Sort assets by desired outcome, not by app. For each account: memorialize
  3. Use the legitimate rails, not password-sharing. The durable routes are the
  4. Protect the money and the memories specifically. Two failure modes dominate
  5. Write the human instructions, and make them findable. A plan nobody can locate

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

Digital Death Plan loads about 1.7k tokens when it runs. Until then it costs about 146 tokens; SKILL.md has 814 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~146
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). 814 words, ~1,723 tokens.

Download SKILL.mdSave it as .claude/skills/digital-death-plan/SKILL.md (or your agent's skills folder).
name
digital-death-plan
description
Plan what happens to your digital life when you die — accounts, photos, passwords, money, and social profiles — so someone you trust can actually find, access, memorialize, or close them without a legal nightmare. Use when someone says 'what happens to my accounts when I die', 'digital legacy', 'help my family access my stuff if something happens', or is doing estate planning and forgot the online half. Produces a digital asset inventory, an access plan using built-in legacy tools, and instructions for your person. Not legal advice — pairs with a real will.

Digital Death Plan Skill

Your life is mostly online now, and none of it is in your will. When someone dies, their family routinely loses irreplaceable photos, can't close accounts that keep billing, gets locked out of email (which is the master key to everything), and spends months fighting platform bureaucracy — all avoidable with an afternoon of planning while alive. This skill builds that plan: inventory the digital assets that matter, set up the legitimate access routes (the built-in legacy features, not password-sharing that violates terms and breaks on death), and write your trusted person clear instructions so grief isn't compounded by a login wall.

What This Skill Produces

  • A digital asset inventory: accounts and content sorted by what should happen to each — memorialize, transfer, download-then-close, or delete — with the sentimental and the financial both covered
  • An access plan using legitimate mechanisms: platform legacy/inactive-account tools (the ones that actually survive death), where credentials live (a password manager's emergency access, not a sticky note), and what your executor is legally entitled to
  • Instructions for your person: a plain letter telling your trusted someone what exists, where the keys are, and what you want done — findable, not buried
  • A "what to protect" note: the accounts that keep charging, the ones with real money, the irreplaceable photos, and the ones you'd want closed for privacy

Required Inputs

Ask for (if not already provided):

  • The digital footprint: email(s), photo/cloud storage, social media, financial and crypto, subscriptions, domains/websites, gaming, anything with money or memories
  • Who the trusted person / executor is, and how tech-comfortable they are
  • What the user wants for the sensitive stuff — memorialize socials or delete? who gets the photos? anything to be closed privately without others seeing?
  • Whether there's a will/executor already, so this plugs into it rather than floating

Framework

  1. Email is the master key — start there. Whoever controls the primary email can reset almost everything else, so it's the highest-priority and highest-risk asset. Plan its access first (legacy contact / emergency access), and note that this power is exactly why it must go to the right person.
  2. Sort assets by desired outcome, not by app. For each account: memorialize (socials with a legacy-contact feature), transfer (photos, domains, money), download-then-close (subscriptions, most services), or delete (privacy). The outcome dictates the mechanism.
  3. Use the legitimate rails, not password-sharing. The durable routes are the built-in ones — major platforms have legacy-contact / inactive-account / memorial processes, and a good password manager has emergency-access delegation. Sharing raw passwords often violates terms, breaks when passwords rotate, and can create legal ambiguity. The plan uses what's designed to survive death, and flags that an executor's legal access rights vary by place (verify-local).
  4. Protect the money and the memories specifically. Two failure modes dominate: accounts that quietly keep billing a dead person, and irreplaceable photos lost behind a login. Flag both explicitly — what has real value, what recurs, what can never be recovered — so they get handled first. Crypto especially: no seed phrase, no recovery, ever.
  5. Write the human instructions, and make them findable. A plan nobody can locate is no plan. The letter to your person: what exists, where the keys are (the password manager, the emergency-access setup, the safe), what you want done with each category, and where THIS document lives — stored with your will or told to the executor, never left only on the device that's now locked.
Show full SKILL.md (250 more words)Show less

Output Format

## Digital asset inventory
| Account/asset | Has money? | Irreplaceable? | Desired outcome | Access mechanism |

## Access plan (legitimate rails)
Email (master key): [legacy/emergency access setup] · Password manager emergency
access: … · Platform legacy tools to set up now: … · Executor's legal access:
[verify-local]

## Protect first
[Recurring charges to stop · real money (incl. crypto — seed phrase!) · the photos]

## Letter to your person (draft)
[What exists · where the keys are · what to do with each category · where this plan lives]

## Set up this week
[The 3-4 legacy/emergency-access features to actually switch on now]

Quality Checks

  • Email is prioritized as the master key
  • Every asset has a desired outcome and a legitimate access mechanism — not "share the password"
  • Money (recurring charges, accounts, crypto seed phrases) and irreplaceable photos are called out for first handling
  • The instructions to the trusted person are drafted and their storage location is specified (not on the locked device)
  • Executor legal-access and platform specifics are flagged verify-local, and it's noted this pairs with — doesn't replace — a will

Anti-Patterns

  • Do not recommend a shared plaintext password list — it breaks on rotation, often violates terms, and creates legal mess; use legacy tools and emergency access
  • Do not give legal advice on wills, executors, or estate law — flag verify-local and route to a will/solicitor; this is the digital companion to that, not a substitute
  • Do not skip crypto's brutal finality — no key means the money is simply gone
  • Do not create a plan that lives only on the user's device — findability is the whole point
  • Do not assume the "trusted person" should get everything — some accounts the user may want closed privately; honor per-category wishes

[[legacy-letter]] for the emotional message that rides alongside; [[grief-admin]] is what your people will be doing — this makes it survivable; [[estate-planning-kit]] for the will this plugs into; [[password]] hygiene now makes all of this easier.

Example Trigger Phrases

  • "What happens to my accounts when I die?"
  • "Help my family access my stuff if something happens."
  • "Plan my digital legacy."
  • "Who gets my photos and passwords?"

© 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/digital-death-plan of mohitagw15856/pm-claude-skills.

Open the folder on GitHubat commit 1cbf1f0

Compare with similar skills

Digital Death Plan 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.

Digital Death Plan compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Digital Death Plan this skillmohitagw15856/pm-claude-skills1.4k—~1.7kAutomated safety check: PassMIT
Digital Forensicssickn33/agentic-awesome-skills47k1 repos~495Automated safety check: PassMIT
Digital Forensicszhaoxuya520/reverse-skill41k2 repos~389Automated safety check: WarnMIT
Implementing Digital Signatures With Ed25519mukul975/Anthropic-Cybersecurity-Skills34k—~875Automated safety check: PassApache-2.0
Digital Ocean AutomationComposioHQ/awesome-claude-skills77k3 repos~751Automated safety check: PassNone
Life Meaning Reflection Guidekangarooking/cangjie-skill11k—~644Automated safety check: PassMIT

Similar skills

  • Digital Forensics

    sickn33/agentic-awesome-skills

    Authorized digital forensics: memory dumps, disk timelines, PCAP investigation, artifact triage, and incident-response evidence preservation.

    47k GitHub starsUsed in 1 repo~495 tokens
    SecurityAuto-check passed
  • Digital Forensics

    zhaoxuya520/reverse-skill

    A skill your agent uses for authorized digital forensics including memory dumps, disk timelines, PCAP investigation, artifact triage, and IR evidence preservation.

    41k GitHub starsUsed in 2 repos~389 tokens
    SecurityAuto-check: warnings
  • Implementing Digital Signatures With Ed25519

    mukul975/Anthropic-Cybersecurity-Skills

    Implements digital signatures using the Ed25519 algorithm (Curve25519), covering key-pair generation, signing, signature verification, and security tradeoffs versus RSA and ECDSA.

    34k GitHub stars~875 tokensUpdated 1 mo ago
    SecurityAuto-check passed
  • Digital Ocean Automation

    ComposioHQ/awesome-claude-skills

    Automate DigitalOcean tasks via Rube MCP (Composio). An agent skill from ComposioHQ/awesome-claude-skills.

    77k GitHub starsUsed in 3 repos~751 tokens
    Productivity & AutomationAuto-check passed
  • Life Meaning Reflection Guide

    kangarooking/cangjie-skill

    Guides a reflective conversation about the meaning of life, emptiness or lack of direction, using three answers from a book about Naval and four practical steps.

    11k GitHub stars~644 tokensUpdated 9 days ago
    Knowledge ManagementAuto-check passed
  • Swiss-grid fintech deck template in black / warm paper / neon-lime contrast.

    100k GitHub stars~461 tokensUpdated yesterday
    Business, Finance & HRAuto-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 Digital Death Plan

What does Digital Death Plan do?

Plan what happens to your digital life when you die — accounts, photos, passwords, money, and social profiles — so someone you trust can actually find, access, memorialize, or close them without a…. Digital Death Plan is an agent skill from mohitagw15856/pm-claude-skills. Plan what happens to your digital life when you die — accounts, photos, passwords, money, and social profiles — so someone you trust can actually find, access, memorialize, or close them without a legal nightmare.

When should I use Digital Death Plan?

Digital Death Plan fits situations like: someone says what happens to my accounts when I die; help my family access my stuff if something happens; is doing estate planning and forgot the online half.

How do I install Digital Death Plan in Claude Code?

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

How do I install Digital Death Plan in Codex?

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

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

What does Digital Death Plan need to run?

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

Does Digital Death Plan 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 Digital Death Plan 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 Digital Death Plan use?

Digital Death Plan 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 Digital Death Plan use?

About 1.7k tokens (SKILL.md is roughly 6.9k 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 Digital Death Plan?

Skills that share tags, products or a category with Digital Death Plan: Digital Forensics (sickn33/agentic-awesome-skills, 47k stars), Digital Forensics (zhaoxuya520/reverse-skill, 41k stars), Implementing Digital Signatures With Ed25519 (mukul975/Anthropic-Cybersecurity-Skills, 34k stars) and Digital Ocean Automation (ComposioHQ/awesome-claude-skills, 77k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Digital Death Plan?

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.