Agent skill

Digital Legacy Planner

by mohitagw15856 in mohitagw15856/pm-claude-skills

Plan what happens to your digital life — the account inventory, the access plan that doesn't violate terms or law, platform legacy settings, and the memorialize/delete/preserve decisions, written…

MITAuto-check passed

Install Digital Legacy Planner

skills CLI
$ npx skills add mohitagw15856/pm-claude-skills --skill digital-legacy-planner -a claude-code

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

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

At a glance

Plan what happens to your digital life — the account inventory, the access plan that doesn't violate terms or law, platform legacy settings, and the memorialize/delete/preserve decisions, written…

  • Works in 5 steps: Tier by consequence, plan the top: Tier… → Use the platforms' own legacy tools —… → Password-manager emergency access is the… → …
  • Asked what happens to my accounts when I die
  • SKILL.md covers What This Skill Produces, Required Inputs, Framework: The… and Output Format, plus 7 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Digital Legacy Planner is an agent skill from mohitagw15856/pm-claude-skills. Plan what happens to your digital life — the account inventory, the access plan that doesn't violate terms or law, platform legacy settings, and the memorialize/delete/preserve decisions, written down while it's easy. Use when asked what happens to my accounts when I die, set up a digital legacy plan, help an executor deal with online accounts, or how does my family get into my stuff. Produces the tiered inventory, the legal-access setup (password-manager emergency access + platform legacy tools), the wishes…

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

  • Asked what happens to my accounts when I die
  • Set up a digital legacy plan
  • Help an executor deal with online accounts
  • How does my family get into my stuff

Example prompts

  • “/digital-legacy-planner”

Workflow steps

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

  1. Tier by consequence, plan the top: Tier 1 — the keys (primary email, phone account, password manager): whoever holds these holds…
  2. Use the platforms' own legacy tools — they exist and almost nobody sets them: Google's Inactive Account Manager, Apple's Legacy Contact…
  3. Password-manager emergency access is the master move: one well-configured emergency-access grant (with a waiting period) beats every list…
  4. Sharing passwords ad hoc is the anti-plan: it violates most platforms' terms, can create legal ambiguity for the survivor…
  5. Wishes are decisions, written down: memorialize or delete the profiles? Photos to whom? The channel — archived or continued? Silence hands…

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 Legacy Planner loads about 1.7k tokens when it runs. Until then it costs about 146 tokens; SKILL.md has 840 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). 840 words, ~1,659 tokens.

Download SKILL.mdSave it as .claude/skills/digital-legacy-planner/SKILL.md (or your agent's skills folder).
name
digital-legacy-planner
description
Plan what happens to your digital life — the account inventory, the access plan that doesn't violate terms or law, platform legacy settings, and the memorialize/delete/preserve decisions, written down while it's easy. Use when asked what happens to my accounts when I die, set up a digital legacy plan, help an executor deal with online accounts, or how does my family get into my stuff. Produces the tiered inventory, the legal-access setup (password-manager emergency access + platform legacy tools), the wishes document, and the executor's digital checklist.

Digital Legacy Planner Skill

Everyone now dies twice — once in the world and once across forty accounts, and the second death is unplanned in almost every family. The photos are in a cloud account nobody can enter, the subscriptions keep billing, and the email that could reset everything is locked behind the very 2FA that made it safe. This skill plans it while it's easy: inventory by importance, legitimate access routes (platform legacy tools and password-manager emergency access — not "here's my password on a sticky note," which is both fragile and often violates terms or law), and the wishes written where they'll be found.

What This Skill Produces

  • The tiered inventory — accounts by consequence: the keys (email, phone, password manager), the money, the memories, the long tail
  • The access plan — platform legacy settings + password-manager emergency access, configured; the sticky-note anti-pattern replaced
  • The wishes document — memorialize / delete / preserve / hand-to, per account-that-matters, plus the message-to-family
  • The executor's digital checklist — for the other direction: someone died, here's the order of operations

Required Inputs

Ask for these if not provided:

  • Which direction — planning your own (the calm version) or handling someone else's (the checklist version, cross-linked with estate-settlement-organizer)
  • The digital footprint, roughly — main email provider, phone platform, password manager (or its absence — fixing that is step one), where the photos live, anything monetized (channel, store, domains, crypto — the last needs special handling and its absence from this plan is a finding)
  • The people — who should get access, who should decide, and whether those are the same person

Framework: The Legitimacy-First Rules

  1. Tier by consequence, plan the top: Tier 1 — the keys (primary email, phone account, password manager): whoever holds these holds everything, and they get the formal tools. Tier 2 — money (banking handled via the estate; here it's the digital-only value: payment apps, monetized accounts, domains, crypto). Tier 3 — memories (photos, messages — usually what the family actually grieves for). Tier 4 — the long tail (subscriptions to kill, socials to close). The plan is written top-down because time and attention run out bottom-up.
  2. Use the platforms' own legacy tools — they exist and almost nobody sets them: Google's Inactive Account Manager, Apple's Legacy Contact, Facebook's legacy contact/memorialization — each takes minutes now and replaces months of grief-bureaucracy later. The plan lists the user's actual platforms with their tool named as configure-this-week items (flag: features change — verify in settings).
  3. Password-manager emergency access is the master move: one well-configured emergency-access grant (with a waiting period) beats every list of passwords ever written — it stays current automatically, it's revocable, and it's the legitimate version of what the sticky note was trying to do. No password manager yet? That's the plan's first action item, before any legacy configuration.
  4. Sharing passwords ad hoc is the anti-plan: it violates most platforms' terms, can create legal ambiguity for the survivor (unauthorized-access laws don't pause for grief — jurisdiction-varies, flagged), goes stale instantly, and fails exactly when 2FA works. The plan's job is making the legitimate routes so easy the workaround loses.
  5. Wishes are decisions, written down: memorialize or delete the profiles? Photos to whom? The channel — archived or continued? Silence hands these to a grieving committee with no mandate; a one-page wishes document (stored with the will and named in the estate file) hands them answers. Include the human line — the message that says what mattered.
Show full SKILL.md (284 more words)Show less

Output Format

Digital Legacy Plan: [name] — [date]

The Inventory (tiered)

TierAccount/assetLegacy toolStatus

Configure This Week

[The user's actual platforms → each legacy tool, as a checklist · password-manager emergency access: grantee + waiting period · the no-manager-yet branch]

The Wishes Document (store with the will)

[Per Tier-1–3 item: memorialize / delete / preserve / hand to [name] · the crypto/domain special-handling note · the message to family]

Executor's Digital Checklist (the other direction)

[Don't guess passwords (legal risk — flagged) → use legacy tools + death-certificate processes per platform → kill the billing tail → memorialize/close per wishes or family decision]

Platform legacy features change and unauthorized-access laws vary by jurisdiction — verify tools in current settings and route legal questions (especially crypto and cross-border accounts) to the estate's attorney. Not legal advice.

Quality Checks

  • Tier 1 (email, phone, password manager) is planned before anything else
  • Every named platform maps to its actual legacy tool, flagged verify-in-settings
  • The password-sharing anti-pattern is replaced, not just discouraged
  • Crypto/domains/monetized assets get their special-handling note or an explicit absence-finding
  • The wishes document includes decisions, not just access

Anti-Patterns

  • Do not build the plan on a shared password list — stale, terms-violating, and 2FA breaks it
  • Do not advise survivors to log in as the deceased — legal risk, jurisdiction-dependent, flag and route
  • Do not inventory forty accounts with equal weight — the tiers are the plan
  • Do not leave memorialize-vs-delete to the grieving — the wishes document exists to answer it
  • Do not treat this as morbid housekeeping — frame it as the last considerate thing on the to-do list, because it is

Example Trigger Phrases

  • "What happens to my accounts when I die?"
  • "Set up a digital legacy plan."
  • "Help an executor deal with online accounts."
  • "How does my family get into my stuff?"

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

Open the folder on GitHubat commit 1cbf1f0

Compare with similar skills

Digital Legacy Planner 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 Legacy Planner compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Digital Legacy Planner this skillmohitagw15856/pm-claude-skills1.4k—~1.7kAutomated safety check: PassMIT
Legacy Migration Plannertech-leads-club/agent-skills7k—~1.8kAutomated safety check: PassCC-BY-4.0
Plannerpenpot/penpot61k—~2.7kAutomated safety check: PassMPL-2.0
Expense Accountingsickn33/agentic-awesome-skills47k1 repos~6.5kAutomated safety check: PassMIT
Purchase Accountingsickn33/agentic-awesome-skills47k1 repos~5.1kAutomated safety check: PassMIT
Digital Forensicssickn33/agentic-awesome-skills47k1 repos~495Automated safety check: PassMIT

Similar skills

  • Legacy Migration Planner

    tech-leads-club/agent-skills

    Produces evidence-based migration plans using the Strangler Fig pattern for monolith splits, rewrites and framework upgrades, without implementing them.

    7k GitHub stars~1.8k tokensUpdated yesterday
    DevelopmentAuto-check passed
  • Planner

    penpot/penpot

    Read-only planning and architecture analysis — produce a structured implementation plan with task breakdown, acceptance criteria, sizing, and checkpoints.

    61k GitHub stars~2.7k tokensUpdated yesterday
    Agent WorkflowsAuto-check passed
  • Expense Accounting

    sickn33/agentic-awesome-skills

    Expense accounting register: expense number and date, payee with PAN and VAT, bill reference, document type, amount with VAT, ledger account, approver and status.

    47k GitHub starsUsed in 1 repo~6.5k tokens
    Business, Finance & HRAuto-check passed
  • Purchase Accounting

    sickn33/agentic-awesome-skills

    Purchase register: supplier, invoice, gross amount, VAT and TDS, net payable, ledger account and payment balance.

    47k GitHub starsUsed in 1 repo~5.1k tokens
    Business, Finance & HRAuto-check passed
  • 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
  • Odoo Accounting Setup

    sickn33/agentic-awesome-skills

    Expert guide for configuring Odoo Accounting: chart of accounts, journals, fiscal positions, taxes, payment terms, and bank reconciliation.

    47k GitHub starsUsed in 2 repos~1k tokens
    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 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

Questions about Digital Legacy Planner

What does Digital Legacy Planner do?

Plan what happens to your digital life — the account inventory, the access plan that doesn't violate terms or law, platform legacy settings, and the memorialize/delete/preserve decisions, written…. Digital Legacy Planner is an agent skill from mohitagw15856/pm-claude-skills. Plan what happens to your digital life — the account inventory, the access plan that doesn't violate terms or law, platform legacy settings, and the memorialize/delete/preserve decisions, written down while it's easy.

When should I use Digital Legacy Planner?

Digital Legacy Planner fits situations like: asked what happens to my accounts when I die; set up a digital legacy plan; help an executor deal with online accounts; how does my family get into my stuff.

How do I install Digital Legacy Planner in Claude Code?

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

How do I install Digital Legacy Planner in Codex?

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

Can I use Digital Legacy Planner 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-legacy-planner -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-legacy-planner, .gemini/skills/digital-legacy-planner, .github/skills/digital-legacy-planner and .opencode/skills/digital-legacy-planner in your project.

What does Digital Legacy Planner need to run?

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

Does Digital Legacy Planner 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 Legacy Planner 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 Legacy Planner use?

Digital Legacy Planner 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 Legacy Planner use?

About 1.7k tokens (SKILL.md is roughly 6.6k 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 Legacy Planner?

Skills that share tags, products or a category with Digital Legacy Planner: Legacy Migration Planner (tech-leads-club/agent-skills, 7k stars), Planner (penpot/penpot, 61k stars), Expense Accounting (sickn33/agentic-awesome-skills, 47k stars) and Purchase Accounting (sickn33/agentic-awesome-skills, 47k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Digital Legacy Planner?

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.