{"id":"49504932-ec81-4abe-bbc1-a943173d5982","entityType":"agent","slug":"clawhub-voronindenis5-digital-legacy","name":"digital-legacy","canonicalUrl":"https://www.xpersona.co/agent/clawhub-voronindenis5-digital-legacy","canonicalPath":"/agent/clawhub-voronindenis5-digital-legacy","generatedAt":"2026-10-10T02:39:52.128Z","source":"CLAWHUB","claimStatus":"UNCLAIMED","verificationTier":"NONE","summary":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-09T12:56:19.593Z","emptyReason":null},"description":"Plan what happens to your digital life if you die or become incapacitated. Inventory accounts, subscriptions, crypto wallets, important files, social media legacy contacts, and generate a sealed instruction document for trusted family. Includes encrypted digital will template and printable emergency access guide.","descriptionLabel":"Source description","evidenceSummary":"Capability contract not published. No trust telemetry is available yet. 2.6K downloads reported by the source. Last updated 10/9/2026.","installCommand":"clawhub skill install s17b6amkd3wzqgg640v03a9r1n83gxs1:digital-legacy","sourceUrl":"https://clawhub.ai/voronindenis5/digital-legacy","homepage":"https://clawhub.ai/voronindenis5/skills/digital-legacy","primaryLinks":[{"label":"View on ClawHub","url":"https://clawhub.ai/voronindenis5/digital-legacy","kind":"source"},{"label":"Homepage","url":"https://clawhub.ai/voronindenis5/skills/digital-legacy","kind":"homepage"}],"safetyScore":84,"overallRank":62,"popularityScore":68,"trustScore":null,"claimedByName":null,"isOwner":false,"seoDescription":"digital-legacy technical dossier on Xpersona with agent coverage, OPENCLEW support, and live trust metadata."},"coverage":{"evidence":{"source":"public-profile","verified":false,"confidence":"medium","updatedAt":"2026-10-09T12:56:19.593Z","emptyReason":null},"protocols":[{"protocol":"OPENCLEW","label":"OpenClaw","status":"self-declared","notes":"Declared in the public agent profile."}],"capabilities":[],"verifiedCount":0,"selfDeclaredCount":1,"capabilityMatrix":{"rows":[{"key":"OPENCLEW","type":"protocol","support":"unknown","confidenceSource":"profile","notes":"Listed on profile"}],"flattenedTokens":"protocol:OPENCLEW|unknown|profile"}},"adoption":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-09T12:56:19.593Z","emptyReason":null},"stars":null,"forks":null,"downloads":2608,"packageName":null,"latestVersion":"0.1.2","tractionLabel":"2.6K downloads"},"release":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-09T12:56:19.556Z","emptyReason":null},"lastUpdatedAt":"2026-10-09T12:56:19.593Z","lastCrawledAt":"2026-10-09T12:56:19.556Z","lastIndexedAt":null,"nextCrawlAt":"2026-10-10T12:56:19.556Z","lastVerifiedAt":null,"highlights":[{"version":"0.1.2","createdAt":"2026-08-14T06:19:07.620Z","changelog":"- Removed the file skill-card.md. - No other changes made to functionality or documentation.","fileCount":15,"zipByteSize":29828},{"version":"0.1.1","createdAt":"2026-08-11T11:57:35.351Z","changelog":"- Removed the file skill-card.md. - No user-facing features or content were changed in this release.","fileCount":15,"zipByteSize":29802},{"version":"0.1.0","createdAt":"2026-08-05T19:48:27.410Z","changelog":"Initial release of Digital Legacy — a tool to help plan your digital inheritance. - Inventory all digital accounts, subscriptions, crypto wallets, and important files. - Generate an encrypted digital will with access instructions and wishes for each account. - Produce a printable emergency access guide for your trusted contact. - Includes templates, security best practices, and platform policy references. - Workflow covers inventory, specifying wishes, and secure document generation.","fileCount":15,"zipByteSize":29697}]},"execution":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No published capability contract is available yet."},"installCommand":"clawhub skill install s17b6amkd3wzqgg640v03a9r1n83gxs1:digital-legacy","setupComplexity":"low","setupSteps":["Install using `clawhub skill install s17b6amkd3wzqgg640v03a9r1n83gxs1:digital-legacy` in an isolated environment before connecting it to live workloads.","No published capability contract is available yet, so validate auth and request/response behavior manually.","Review the upstream CLAWHUB listing at https://clawhub.ai/voronindenis5/digital-legacy before using production credentials."],"contract":{"contractStatus":"missing","authModes":[],"requires":[],"forbidden":[],"supportsMcp":false,"supportsA2a":false,"supportsStreaming":false,"inputSchemaRef":null,"outputSchemaRef":null,"dataRegion":null,"contractUpdatedAt":null,"sourceUpdatedAt":null,"freshnessSeconds":null},"invocationGuide":{"preferredApi":{"snapshotUrl":"https://www.xpersona.co/api/v1/agents/clawhub-voronindenis5-digital-legacy/snapshot","contractUrl":"https://www.xpersona.co/api/v1/agents/clawhub-voronindenis5-digital-legacy/contract","trustUrl":"https://www.xpersona.co/api/v1/agents/clawhub-voronindenis5-digital-legacy/trust"},"curlExamples":["curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-voronindenis5-digital-legacy/snapshot\"","curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-voronindenis5-digital-legacy/contract\"","curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-voronindenis5-digital-legacy/trust\""],"jsonRequestTemplate":{"query":"summarize this repo","constraints":{"maxLatencyMs":2000,"protocolPreference":["OPENCLEW"]}},"jsonResponseTemplate":{"ok":true,"result":{"summary":"...","confidence":0.9},"meta":{"source":"CLAWHUB","generatedAt":"2026-10-10T02:39:52.124Z"}},"retryPolicy":{"maxAttempts":3,"backoffMs":[500,1500,3500],"retryableConditions":["HTTP_429","HTTP_503","NETWORK_TIMEOUT"]}},"endpoints":{"dossierUrl":"https://www.xpersona.co/api/v1/agents/clawhub-voronindenis5-digital-legacy/dossier","snapshotUrl":"https://www.xpersona.co/api/v1/agents/clawhub-voronindenis5-digital-legacy/snapshot","contractUrl":"https://www.xpersona.co/api/v1/agents/clawhub-voronindenis5-digital-legacy/contract","trustUrl":"https://www.xpersona.co/api/v1/agents/clawhub-voronindenis5-digital-legacy/trust"}},"reliability":{"evidence":{"source":"runtime-metrics","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No trust, reliability, or runtime telemetry is available."},"trust":{"status":"unavailable","handshakeStatus":"UNKNOWN","verificationFreshnessHours":null,"reputationScore":null,"p95LatencyMs":null,"successRate30d":null,"fallbackRate":null,"attempts30d":null,"trustUpdatedAt":null,"trustConfidence":"unknown","sourceUpdatedAt":null,"freshnessSeconds":null},"decisionGuardrails":{"doNotUseIf":["Contract metadata is missing or unavailable for deterministic execution."],"safeUseWhen":[],"riskFlags":["missing_or_unavailable_contract","trust_data_unavailable","schema_references_missing"],"operationalConfidence":"low"},"executionMetrics":{"observedLatencyMsP50":null,"observedLatencyMsP95":null,"estimatedCostUsd":null,"uptime30d":null,"rateLimitRpm":null,"rateLimitBurst":null,"lastVerifiedAt":null,"verificationSource":null},"runtimeMetrics":{"successRate":null,"avgLatencyMs":null,"avgCostUsd":null,"hallucinationRate":null,"retryRate":null,"disputeRate":null,"p50Latency":null,"p95Latency":null,"lastUpdated":null}},"benchmarks":{"evidence":{"source":"no-benchmark-data","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No benchmark suites or observed failure patterns are available."},"suites":[],"failurePatterns":[]},"artifacts":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-09T12:56:19.593Z","emptyReason":null},"readme":"Skill: digital-legacy\n\nOwner: voronindenis5\n\nSummary: Plan what happens to your digital life if you die or become incapacitated. Inventory accounts, subscriptions, crypto wallets, important files, social media legacy contacts, and generate a sealed instruction document for trusted family. Includes encrypted digital will template and printable emergency access guide.\n\nTags: latest:0.1.2\n\nVersion history:\n\nv0.1.2 | 2026-08-14T06:19:07.620Z | auto\n\n- Removed the file skill-card.md.\n- No other changes made to functionality or documentation.\n\nv0.1.1 | 2026-08-11T11:57:35.351Z | auto\n\n- Removed the file skill-card.md.\n- No user-facing features or content were changed in this release.\n\nv0.1.0 | 2026-08-05T19:48:27.410Z | auto\n\nInitial release of Digital Legacy — a tool to help plan your digital inheritance.\n\n- Inventory all digital accounts, subscriptions, crypto wallets, and important files.\n- Generate an encrypted digital will with access instructions and wishes for each account.\n- Produce a printable emergency access guide for your trusted contact.\n- Includes templates, security best practices, and platform policy references.\n- Workflow covers inventory, specifying wishes, and secure document generation.\n\nArchive index:\n\nArchive v0.1.2: 15 files, 29828 bytes\n\nFiles: LICENSE (1059b), README.md (4435b), references (0b), references/account-checklist.md (7637b), references/platform-policies.md (6852b), references/security-best-practices.md (5984b), references/workflow-guide.md (7465b), scripts (0b), scripts/digital_legacy.py (25102b), scripts/templates (0b), scripts/templates/template_guide.html (4957b), scripts/templates/template_will.md (916b), skill-card.md (3062b), SKILL.md (7700b), _meta.json (133b)\n\nFile v0.1.2:SKILL.md\n\n---\nname: digital-legacy\ndescription: >\n Plan what happens to your digital life if you die or become incapacitated.\n Inventory accounts, subscriptions, crypto wallets, important files, social\n media legacy contacts, and generate a sealed instruction document for\n trusted family. Includes encrypted digital will template and printable\n emergency access guide.\nversion: 1.0.0\nauthor: Denis Voronin\nlicense: MIT\ntags:\n - estate-planning\n - digital-inheritance\n - security\n - encryption\n - emergency\n - legacy\n---\n\n# Digital Legacy\n\n> Your digital life outlives you. Plan for it.\n\n`Digital Legacy` is a skill that helps you create a complete digital\ninheritance plan. It inventories your accounts, subscriptions, crypto wallets,\nand important files; configures social media legacy contacts; and generates a\nsealed, encrypted instruction document that trusted family members can access\nin an emergency.\n\n## When to Use\n\nActivate this skill when:\n\n- You want to create a digital will or inheritance plan\n- You need to inventory online accounts and subscriptions\n- You want to document crypto wallet access for heirs\n- You're setting up emergency access for a trusted person\n- You need a printable emergency access guide\n- You're helping someone else organize their digital legacy\n\n## What It Produces\n\nThe skill generates three deliverables:\n\n### 1. Account Inventory (`accounts.json`)\nA structured inventory of all digital accounts:\n- Email, social media, banking, subscriptions\n- Crypto wallets and exchange accounts\n- Cloud storage and backup locations\n- Domain registrations and hosting\n- Status: active, dormant, to-close\n\n### 2. Encrypted Digital Will (`digital_will.enc`)\nA sealed instruction document containing:\n- Access instructions (where to find passwords, recovery keys)\n- Wishes for each account (archive, memorialize, delete, transfer)\n- Crypto wallet seed phrases and access paths\n- Location of important local files\n- Contact information for services with legacy/deceased policies\n\nEncrypted with AES-256 using a passphrase you choose. Only someone with the\npassphrase can open it.\n\n### 3. Emergency Access Guide (`emergency_guide.html`)\nA printable one-page guide for your trusted person:\n- The passphrase hint (NOT the passphrase itself)\n- Where to find the encrypted will file\n- Immediate steps to take\n- Key contacts (lawyer, financial advisor, tech-savvy friend)\n- Services that require death certificates\n\n## Quick Reference\n\n| Need | Command |\n| --------------------------------- | -------------------------------------------------------------------- |\n| Initialize a new legacy plan | `python3 scripts/digital_legacy.py init` |\n| Add an account | `python3 scripts/digital_legacy.py add-account` |\n| Add a subscription | `python3 scripts/digital_legacy.py add-subscription` |\n| Add a crypto wallet | `python3 scripts/digital_legacy.py add-wallet` |\n| List all inventory | `python3 scripts/digital_legacy.py list` |\n| Generate encrypted will | `python3 scripts/digital_legacy.py generate-will` |\n| Generate emergency guide | `python3 scripts/digital_legacy.py emergency-guide` |\n| Full plan (interactive) | `python3 scripts/digital_legacy.py setup` |\n| Decrypt and read the will | `python3 scripts/digital_legacy.py read-will digital_will.enc` |\n\n## Security Model\n\nThis skill uses a **passphrase-based encryption** model:\n\n1. You choose a strong passphrase and give a **hint** (not the passphrase) to\n your trusted person.\n2. The will document is encrypted with AES-256-GCM using a key derived from\n your passphrase via PBKDF2 (100,000 iterations).\n3. The encrypted file can only be opened with the passphrase.\n4. The passphrase is **never stored** anywhere in plaintext.\n\n> **Important:** If you lose the passphrase, the encrypted will cannot be\n> recovered. Store the passphrase securely (password manager + physical copy in\n> a safe deposit box). See `references/security-best-practices.md`.\n\n## Workflow\n\n### Phase 1: Inventory (`setup` or individual `add-*` commands)\n\n1. List all your online accounts (email, social, banking, shopping)\n2. List recurring subscriptions (streaming, software, memberships)\n3. Document crypto wallets (type, access method, approximate value)\n4. Note important local files (taxes, deeds, insurance, will)\n5. Record legacy contact settings (Google, Facebook, Apple)\n\n### Phase 2: Specify Wishes\n\nFor each account, specify what should happen:\n- **Archive**: Save data, then close\n- **Memorialize**: Convert to memorial page (Facebook, Google)\n- **Delete**: Close and delete all data\n- **Transfer**: Transfer ownership to a specific person\n- **Maintain**: Keep active (e.g., domain, email forwarding)\n\n### Phase 3: Generate Documents\n\n1. Run `generate-will` to create the encrypted instruction document\n2. Run `emergency-guide` to create the printable HTML guide\n3. Share the guide with your trusted person\n4. Store the encrypted will in a location your trusted person can access\n\nSee `references/workflow-guide.md` for a detailed step-by-step process.\n\n## Files\n\n- `references/security-best-practices.md` — encryption, passphrase, storage\n- `references/account-checklist.md` — comprehensive list of account types\n- `references/platform-policies.md` — Google, Apple, Facebook, etc. legacy policies\n- `references/workflow-guide.md` — full step-by-step setup process\n- `scripts/digital_legacy.py` — the main inventory and encryption tool\n- `scripts/templates/template_will.md` — plaintext will template\n- `scripts/templates/template_guide.html` — emergency guide HTML template\n\n## Common Pitfalls\n\n1. **Storing the passphrase with the encrypted file.** The passphrase must be\n stored separately. If someone finds both, the encryption is useless.\n\n2. **Forgetting to update.** Your digital life changes constantly. Re-run the\n inventory at least annually, or after major life events (new accounts,\n marriages, deaths).\n\n3. **Not testing decryption.** After generating the will, test that you can\n decrypt it with your passphrase. A typo in the passphrase is a common,\n catastrophic error.\n\n4. **Crypto wallet seed phrases.** Never store seed phrases in a plain text\n file. The encrypted will is acceptable, but also store a physical copy in a\n secure location (safe deposit box).\n\n5. **Assuming family knows your accounts.** Most people have accounts their\n family doesn't know about (old email addresses, dormant exchanges, digital\n purchases). Be thorough in the inventory.\n\n6. **Legal validity.** This tool creates an informational document, not a\n legally binding will. For legal estate planning, consult a lawyer.\n See `references/workflow-guide.md`.\n\n## Verification Checklist\n\n- [ ] All significant accounts inventoried (not just the ones you use daily)\n- [ ] Subscriptions documented with billing cycle and cost\n- [ ] Crypto wallets documented with access method (NOT seed phrase in plaintext)\n- [ ] Wishes specified for each account (archive/delete/transfer/maintain)\n- [ ] Will encrypted with a strong passphrase you've tested\n- [ ] Passphrase stored securely (password manager + physical copy)\n- [ ] Emergency guide printed and shared with trusted person\n- [ ] Trusted person knows where to find the encrypted will file\n- [ ] Plan reviewed and updated within the last 12 months\n\n## License\n\nMIT © Denis Voronin\n\nFile v0.1.2:README.md\n\n# Digital Legacy\n\n> Your digital life outlives you. Plan for it.\n\nA [Hermes Agent](https://hermes-agent.nousresearch.com/docs) / OpenClaw skill\nthat helps you create a **digital inheritance plan**: inventory accounts,\nsubscriptions, and crypto wallets; document your wishes for each; and generate\nan **encrypted digital will** plus a **printable emergency access guide** for\ntrusted family members.\n\n## Why\n\nWhen someone dies or becomes incapacitated, their family faces a maze of\nunknown accounts, unrecoverable passwords, lost crypto wallets, and\nauto-renewing subscriptions. Most people have dozens of digital accounts their\nfamily doesn't know exist. Without a plan, digital assets are lost, bills keep\ncharging, and closing accounts becomes a months-long detective project.\n\nDigital Legacy structures the solution: a complete inventory, clear wishes, and\nencrypted instructions that only your trusted person can open.\n\n## What's Included\n\n- **`SKILL.md`** — core skill: security model, workflow, quick-reference.\n- **`references/`**\n - `security-best-practices.md` — encryption, passphrase management, storage.\n - `account-checklist.md` — 100+ account types across 10 categories.\n - `platform-policies.md` — Google, Apple, Facebook, etc. legacy policies.\n - `workflow-guide.md` — full step-by-step setup and maintenance process.\n- **`scripts/digital_legacy.py`** — main tool: inventory, encryption, guide.\n- **`scripts/templates/template_will.md`** — plaintext will template.\n- **`scripts/templates/template_guide.html`** — emergency guide HTML template.\n\n## Quick Start\n\n```bash\n# Interactive full setup (recommended for first time)\npython3 scripts/digital_legacy.py setup\n\n# Or build incrementally\npython3 scripts/digital_legacy.py init\npython3 scripts/digital_legacy.py add-account\npython3 scripts/digital_legacy.py add-subscription\npython3 scripts/digital_legacy.py add-wallet\n\n# View your inventory\npython3 scripts/digital_legacy.py list\n\n# Generate the encrypted will\npython3 scripts/digital_legacy.py generate-will\n\n# Generate the printable emergency guide\npython3 scripts/digital_legacy.py emergency-guide\n\n# Decrypt and read the will later\npython3 scripts/digital_legacy.py read-will digital_will.enc\n```\n\nExample emergency guide output (HTML):\n\n```html\n

Digital Emergency Access Guide

\n

Prepared for: [Trusted Person Name]

\n

From: [Your Name]

\n
\n

If Something Happens to Me:

\n
    \n
  1. Find the file digital_will.enc on my computer
    2. \n
  2. The passphrase hint is: [your hint]
    3. \n
  3. Run: python3 digital_legacy.py read-will digital_will.enc
    4. \n
  4. Enter the passphrase when prompted
    5. \n
\n```\n\n## Security Model\n\n| Component | How It Works |\n| ---------------------- | ------------------------------------------------- |\n| Encryption | AES-256-GCM |\n| Key derivation | PBKDF2-SHA256, 100,000 iterations |\n| Passphrase storage | NOT stored anywhere. You must remember/secure it. |\n| Encrypted file format | Salt + nonce + ciphertext + auth tag |\n| Inventory file | Plaintext JSON (no secrets — just metadata) |\n\n> The inventory (`accounts.json`) contains **metadata only**: service names,\n> account types, and your wishes. It does NOT contain passwords or seed\n> phrases. Those go only in the encrypted will.\n\n## Three Deliverables\n\n1. **`accounts.json`** — plaintext inventory (metadata, no secrets)\n2. **`digital_will.enc`** — encrypted instructions (access details, wishes)\n3. **`emergency_guide.html`** — printable guide for your trusted person\n\n## Installation (Hermes Agent)\n\nCopy or symlink this directory into your skills folder:\n\n```bash\ncp -r digital-legacy ~/.hermes/skills/\n```\n\nHermes auto-discovers skills with a valid `SKILL.md`. See the\n[skills docs](https://hermes-agent.nousresearch.com/docs) for details.\n\n## Requirements\n\n- Python 3.8+ (stdlib only — no pip install needed)\n- The `hashlib` and `hmac` modules are used for key derivation (stdlib)\n\n## Legal Disclaimer\n\nThis tool creates an informational document to help your family access your\ndigital accounts. It is **not** a legally binding will or estate plan. For\nlegally enforceable estate planning, consult a qualified attorney in your\njurisdiction.\n\n## License\n\nMIT © Denis Voronin\n\nFile v0.1.2:_meta.json\n\n{\n \"ownerId\": \"kn75wwn4x6djaf28jbykeamazd81gtdp\",\n \"slug\": \"digital-legacy\",\n \"version\": \"0.1.2\",\n \"publishedAt\": 1786688347620\n}\n\nFile v0.1.2:references/account-checklist.md\n\n# Account Checklist\n\nA comprehensive list of account types to inventory for your digital legacy\nplan. Use this as a checklist — you likely have accounts in categories you\nhaven't thought about.\n\n## How to Use\n\nGo through each category. For every account you have, add it using:\n```bash\npython3 scripts/digital_legacy.py add-account\n```\n\nDon't worry about being perfect on the first pass. It's better to start and\nupdate than to wait until you have a complete list.\n\n---\n\n## 1. Email Accounts\n\n| Service | Notes |\n| ---------------- | ---------------------------------------- |\n| Gmail | Often the key to resetting all others |\n| Outlook/Hotmail | |\n| Yahoo Mail | |\n| ProtonMail | |\n| Work email | Contact IT about post-employment access |\n| Custom domain | Ensure domain renewal is documented |\n\n> **Email is the master key.** Most password resets go through email.\n> Documenting email access is the single most important step.\n\n## 2. Financial & Banking\n\n| Service | Notes |\n| -------------------- | ---------------------------------- |\n| Primary bank | Online banking login |\n| Credit union | |\n| Credit cards | Each issuer's portal |\n| Investment accounts | Brokerage, 401k, IRA |\n| PayPal | |\n| Venmo | |\n| Cash App | |\n| Tax software | TurboTax, TaxAct |\n| Mortgage servicer | |\n| Insurance portals | Life, auto, home, health |\n\n## 3. Cryptocurrency\n\n| Type | What to Document |\n| ------------------- | ------------------------------------ |\n| Hardware wallet | Make/model, PIN location, seed phrase location |\n| Software wallet | Wallet type, seed phrase location |\n| Exchange accounts | Exchange name, 2FA method |\n| DeFi positions | Platform, access method |\n| NFTs | Marketplace, wallet |\n\n> **Critical**: Never store seed phrases in plaintext. Document their physical\n> location in the encrypted will only.\n\n## 4. Social Media\n\n| Service | Legacy/Memorial Feature |\n| ----------- | ---------------------------------- |\n| Facebook | Legacy Contact / Memorialization |\n| Instagram | Memorialization (via Facebook) |\n| X / Twitter | Deceased account removal |\n| LinkedIn | Deceased profile removal |\n| TikTok | Deceased account removal |\n| Snapchat | Deceased account removal |\n| Pinterest | Deceased account removal |\n| Reddit | Deceased account removal |\n\n## 5. Subscriptions & Recurring Payments\n\n| Category | Examples |\n| ---------------- | --------------------------------------- |\n| Streaming | Netflix, Spotify, Disney+, YouTube Premium |\n| Software | Adobe CC, Microsoft 365, iCloud+ |\n| Cloud storage | Google One, Dropbox, iCloud |\n| News | NYT, WSJ, Substack |\n| Gaming | Xbox Game Pass, PlayStation Plus, Steam |\n| Fitness | Gym membership, Peloton, Strava |\n| Associations | Professional orgs, alumni |\n| Donations | Recurring charity donations |\n\n## 6. Cloud Storage & Backups\n\n| Service | What's There |\n| ------------ | ------------------------------------- |\n| Google Drive | Documents, photos, shared files |\n| iCloud | Photos, device backups, documents |\n| Dropbox | |\n| OneDrive | |\n| AWS S3 | Backups, archives |\n| Backblaze | Computer backup |\n| Time Machine | Local backup drive location |\n\n## 7. Shopping & Commerce\n\n| Service | Notes |\n| --------------- | ---------------------------------- |\n| Amazon | Prime membership, purchase history |\n| eBay | Seller account? |\n| Etsy | |\n| Digital wallets | Apple Pay, Google Pay |\n| Loyalty programs| Airlines, hotels, credit card points |\n\n## 8. Professional & Work\n\n| Service | Notes |\n| ------------------ | ----------------------------------- |\n| GitHub | Repositories, organizations |\n| GitLab | |\n| Portfolio sites | Personal website, Behance, Dribbble |\n| Professional email | Contact IT |\n| VPN | |\n| Web hosting | Domain renewal, hosting plan |\n| SSL certificates | Auto-renewal settings |\n\n## 9. Devices & Hardware\n\n| Device | What to Document |\n| ---------------- | ------------------------------------ |\n| Smartphone | Passcode, biometric backup PIN |\n| Tablet | Passcode |\n| Laptop/Desktop | Disk encryption password (FileVault/BitLocker) |\n| External drives | Encryption password, location |\n| Smart home | Hub access (Home Assistant, SmartThings) |\n| Network | Router admin password |\n\n## 10. Digital Assets & Intellectual Property\n\n| Type | Notes |\n| ----------------- | ------------------------------------ |\n| Domain names | Registrar, renewal date |\n| Websites | Hosting, CMS access |\n| Digital purchases | eBooks, movies, music libraries |\n| Creative work | Unpublished manuscripts, code, art |\n| Online courses | Created courses, student data |\n| Monetized content | YouTube channels, blogs with ad revenue |\n\n## 11. Communication\n\n| Service | Notes |\n| ----------- | ---------------------------------- |\n| WhatsApp | Chat history, groups |\n| Telegram | Channels, saved messages |\n| Signal | |\n| Slack | Workspaces |\n| Discord | Servers owned |\n| Zoom | Recordings, recurring meetings |\n\n## 12. Identity & Security\n\n| Service | Notes |\n| -------------------- | ---------------------------------- |\n| Password manager | Master password location + emergency access kit |\n| 2FA apps | Authenticator apps, backup codes |\n| Password recovery | Security questions and answers |\n| Identity monitoring | LifeLock, CreditKarma |\n| Government portals | SSA, IRS, DMV |\n\n---\n\n## After the Checklist\n\nOnce you've inventoried your accounts:\n\n1. **Specify wishes** for each: archive, memorialize, delete, transfer, maintain\n2. **Document access methods**: where to find passwords, recovery keys, 2FA\n3. **Generate the encrypted will** with all access details\n4. **Generate the emergency guide** for your trusted person\n5. **Review annually**\n\nFile v0.1.2:references/platform-policies.md\n\n# Platform Legacy & Deceased Account Policies\n\nMajor platforms' policies for handling accounts after death or incapacitation.\nUse this to specify the right wishes for each account in your digital legacy\nplan.\n\n## Google (Gmail, Drive, Photos, YouTube)\n\n### Inactive Account Manager\n\nGoogle's built-in feature for digital legacy.\n\n- **Setup**: myaccount.google.com → Data & Privacy → Inactive Account Manager\n- **Timeout**: Choose 3, 6, 12, or 18 months of inactivity\n- **Action**: Share data with up to 10 trusted contacts, then optionally delete\n- **Trigger**: No sign-in for the chosen period\n\n**Recommendation**: Set this up. It's the most automated digital legacy tool\navailable.\n\n### Without Inactive Account Manager\n\n- Family can request account closure with a death certificate\n- Google does NOT provide password or account access to family\n- Data may be obtainable via court order (rare, expensive)\n\n## Apple (iCloud, Apple ID)\n\n### Legacy Contact\n\n- **Setup**: Settings → [Your Name] → Password & Security → Legacy Contact\n- **Available**: iOS 15.2+, macOS 12.1+\n- **How it works**: Designate a contact who gets an Access Key. After death,\n they request access with the key + death certificate.\n- **What they get**: Photos, files, notes, messages — everything in iCloud\n- **What they DON'T get**: Subscriptions, licensed media (movies/music), in-app\n purchases\n\n**Recommendation**: Set up a Legacy Contact immediately if using Apple devices.\n\n### Without Legacy Contact\n\n- Apple requires a court order to transfer data\n- Death certificate alone is NOT sufficient\n- Active subscriptions continue billing until cancelled\n\n## Facebook / Meta\n\n### Legacy Contact\n\n- **Setup**: Settings → Memorialization Settings → Legacy Contact\n- **How it works**: Choose a friend to manage your memorialized profile\n- **What they can do**: Pin a post, respond to friend requests, update profile\n photo\n- **What they CANNOT do**: Read your messages, log in as you, delete posts\n\n### Memorialization\n\n- Profile becomes \"Remembering [Name]\"\n- Friends can still post memories\n- No one can log in\n- Content stays visible per your privacy settings\n\n### Account Deletion\n\n- Family can request permanent deletion with death certificate\n- Use: facebook.com/help/contact/228813257197480\n\n## Instagram\n\n### Memorialization\n\n- Owned by Meta; similar process to Facebook\n- Requires death certificate\n- Account becomes memorialized, no new posts\n\n### Account Removal\n\n- Family can request removal with death certificate\n- Form: facebook.com/help/contact/228813257197480 (shared with FB)\n\n## X / Twitter\n\n### No Legacy Feature\n\n- Twitter/X does NOT have a legacy contact feature\n- Account remains active unless deactivated\n\n### Deceased Account Removal\n\n- Family can request removal with:\n - Death certificate\n - Copy of government ID of the deceased\n - Copy of government ID of the requester\n- Form: help.twitter.com/forms/privacy\n\n### Inactive Accounts\n\n- Twitter removes accounts inactive for 6+ months (policy varies)\n\n## LinkedIn\n\n### Deceased Profile Removal\n\n- Fill out the form at: linkedin.com/help/linkedin/ask/TS-RHA\n- Provide: Profile URL, death certificate, relationship confirmation\n- Profile is removed (not memorialized)\n\n## Microsoft (Outlook, OneDrive, Xbox)\n\n### Next of Kin Process\n\n- Microsoft has a \"Next of Kin\" process\n- Requires: death certificate, proof of account ownership\n- Provides: Access to emails, files (via DVD), closure of account\n- Form: microsoft.com/en-us/concern/nextofkin\n\n### Xbox\n\n- Digital game licenses are tied to the account and are NOT transferable\n- Subscriptions (Game Pass) continue until cancelled\n\n## Amazon\n\n### Account Closure\n\n- Family can close account via customer service\n- Requires: Death certificate, account email\n- Digital content (Kindle books, movies) is licensed, NOT owned — cannot be\n transferred\n\n### Prime Membership\n\n- Continues billing until cancelled\n- Family member can cancel via customer service\n\n## Netflix\n\n### Account Cancellation\n\n- Simple: anyone with the death certificate can cancel via customer service\n- No data transfer (viewing history, profiles)\n\n## Spotify\n\n### Account Closure\n\n- Use the contact form: support.spotify.com\n- Premium subscription continues until cancelled\n\n## PayPal\n\n### Account Closure\n\n- PayPal has a deceased user process\n- Requires: Death certificate, executor documentation\n- Funds in the account go through estate/probate process\n- Link: paypal.com/us/smarthelp/article/how-do-i-close-a-deceased-person's-paypal-account\n\n## Cryptocurrency Exchanges\n\n### Coinbase\n\n- Has a dedicated deceased user process\n- Requires: Death certificate, will/probate documents, government ID\n- Assets transferred to estate\n- Link: help.coinbase.com\n\n### Binance, Kraken, Others\n\n- Process varies by exchange and jurisdiction\n- Generally require: death certificate, probate documents, legal heir\n documentation\n- **Slow**: Can take months\n\n### Hardware Wallets (Ledger, Trezor)\n\n- **No platform to contact** — access is purely through seed phrase + PIN\n- If family has the seed phrase: they have full access\n- If they DON'T have the seed phrase: funds are **permanently lost**\n- This is why documenting seed phrase location is critical\n\n## Domain Registrars\n\n### Namecheap, GoDaddy, Google Domains\n\n- Domains are assets — they have value and can expire\n- Transfer requires: death certificate, executor authority\n- **Auto-renew**: If on, the domain continues. If off, it expires and can be\n purchased by anyone.\n- Document: registrar login, domain list, auto-renew status\n\n## Cloud Storage\n\n### Google Drive, iCloud, Dropbox, OneDrive\n\n- Follow the parent platform's policy (see above)\n- Files may contain critical documents (taxes, deeds, insurance)\n- Ensure backup of these files in the encrypted will\n\n## Password Managers\n\n### 1Password\n\n- Emergency Kit: A printed document with account details + Secret Key\n- Emergency access: Designated person can request access; you have a timeout\n period to deny\n\n### Bitwarden\n\n- Emergency Access: Designate trusted emergency contacts\n- They can request access; after a wait period, they get full access\n\n### KeePass\n\n- Database file + master password\n- No platform to contact — ensure master password is in the encrypted will\n\n## Key Takeaways\n\n1. **Set up automated features** (Google Inactive Account Manager, Apple Legacy\n Contact) — they're the easiest safety net.\n2. **Crypto is special**: No platform to contact. Seed phrase access is\n everything.\n3. **Digital purchases are licenses, not property**: Kindle books, iTunes\n movies, etc. cannot be transferred.\n4. **Document death certificate requirements**: Most platforms require one.\n Ensure your family knows where to get them (vital records office).\n5. **Auto-renew is the enemy**: Cancel subscriptions or document them so family\n can.\n\nFile v0.1.2:references/security-best-practices.md\n\n# Security Best Practices\n\nThis document covers encryption, passphrase management, and secure storage for\nyour Digital Legacy plan.\n\n## Encryption Details\n\n### Algorithm\n\nThe `digital_legacy.py` script encrypts the will document using:\n\n- **Cipher**: AES-256-GCM (Galois/Counter Mode)\n- **Key derivation**: PBKDF2-HMAC-SHA256\n- **Iterations**: 100,000\n- **Salt**: 16 random bytes (unique per encryption)\n- **Nonce**: 12 random bytes (unique per encryption)\n\n### File Format\n\n```\n[16-byte salt][12-byte nonce][N-byte ciphertext][16-byte auth tag]\n```\n\nThe salt and nonce are prepended to the encrypted output in plaintext — this\nis standard and safe. They are not secret; their purpose is to ensure that\nencrypting the same data with the same passphrase produces different\nciphertext each time.\n\n### Why AES-GCM?\n\n- **Authenticated encryption**: GCM provides both confidentiality (encryption)\n and integrity (authentication). If the file is tampered with, decryption\n fails.\n- **Standard**: AES-256-GCM is used by TLS, VPNs, and disk encryption\n worldwide.\n- **Stdlib available**: Python's `hashlib` provides PBKDF2. AES-GCM is\n available via the `cryptography` library, or you can use the script's\n built-in fallback (see below).\n\n### Implementation Note\n\nThe script uses Python stdlib only. For AES-GCM, it uses the `hashlib` module\nfor key derivation and provides a clean interface. If the `cryptography`\nlibrary is available, it will use that; otherwise, it falls back to a\nstdlib-only XOR-based stream cipher (less secure, but functional for personal\nuse — see the script for details).\n\n> **For maximum security**, install the `cryptography` library:\n> `pip install cryptography`. The script auto-detects it.\n\n## Passphrase Management\n\n### Choosing a Passphrase\n\nYour passphrase is the **single point of failure**. If it's weak, the\nencryption can be broken. If you forget it, the will is unrecoverable.\n\n**Strong passphrase criteria:**\n- At least 16 characters\n- Mix of uppercase, lowercase, numbers, and symbols\n- Not a dictionary word or common phrase\n- Not reused from any other account\n- Memorable to you but not guessable by family\n\n**Example pattern** (diceware-style):\n```\ncorrect-horse-battery-staple-7-purple-ocean\n```\n\n### Storing the Passphrase\n\nYou need **two copies** in different locations:\n\n1. **Primary**: In your password manager (1Password, Bitwarden, KeePass)\n2. **Backup**: Written on paper in a sealed envelope, stored in:\n - A safe deposit box, OR\n - A fireproof home safe, OR\n - With your estate attorney\n\n> **Never** store the passphrase:\n> - In the same location as the encrypted file\n> - In a plain text file on your computer\n> - In an email to yourself\n> - In cloud notes (Evernote, Apple Notes) in plaintext\n\n### Passphrase Hint\n\nThe emergency guide includes a **hint** — not the passphrase itself. Good hints:\n\n- \"The name of our first dog + my grandmother's birthday\"\n- \"The phrase from the plaque at our cabin\"\n- \"Check the note in the red envelope in the safe deposit box\"\n\nBad hints:\n- The actual passphrase\n- \"My usual password\" (which one?)\n- Something only you would know that your trusted person also needs to know\n\n## Secure Storage\n\n### The Encrypted Will File\n\nStore `digital_will.enc` in **two locations**:\n\n1. **Primary**: On your computer in a known location (e.g.,\n `~/Documents/DigitalLegacy/digital_will.enc`)\n2. **Backup**: On a USB drive in your safe deposit box, OR in encrypted cloud\n storage (the file is already encrypted, so cloud is fine)\n\n### The Inventory File\n\n`accounts.json` contains **metadata only** (service names, account types,\nwishes) — no passwords. It's safe to store in plaintext, but treat it as\nsensitive personal information. Store it alongside the encrypted will.\n\n### The Emergency Guide\n\n`emergency_guide.html` is designed to be **printed and shared** with your\ntrusted person. It contains:\n- A passphrase hint (not the passphrase)\n- Instructions for finding and decrypting the will\n- Key contacts\n\nPrint it, sign it, and give it to your trusted person physically. Do NOT email\nit (email is not secure).\n\n## Trusted Person Selection\n\nChoose someone who is:\n- **Trustworthy**: They'll have access to your entire digital life\n- **Technically capable**: They need to run a Python script or find someone who can\n- **Organized**: They need to follow through on account closures\n- **Not emotionally overwhelmed**: A grieving person may struggle with technical tasks\n\n**Best practice**: Name a primary and a backup trusted person. The backup can\nbe your estate attorney or a tech-savvy friend.\n\n## Updating Your Plan\n\n- **Review annually**: Set a calendar reminder (e.g., every January)\n- **After major events**: New accounts, marriages, divorces, deaths, major purchases\n- **After security incidents**: If an account is compromised, update the plan\n- **Re-encrypt after changes**: Run `generate-will` again after any update\n\n## Threat Model\n\n### What This Protects Against\n\n- ✅ Family not knowing about accounts after death\n- ✅ Lost crypto wallets\n- ✅ Auto-renewing subscriptions after death\n- ✅ Unauthorized access to the will by casual snoops\n\n### What This Does NOT Protect Against\n\n- ❌ A determined attacker with the encrypted file and unlimited time\n (use a stronger passphrase)\n- ❌ Someone who has both the encrypted file AND the passphrase\n (keep them in separate locations)\n- ❌ Legal compelled disclosure (subpoena, court order)\n- ❌ Keylogger or malware on your computer (encrypt on a clean machine if\n paranoid)\n\n## Emergency Decryption\n\nIf you (the owner) forget the passphrase:\n\n1. **Try your password manager** — it may be saved there\n2. **Check your physical backup** — the sealed envelope\n3. **Ask your trusted person** — they may remember the hint\n\nIf all else fails, the will is **unrecoverable**. This is by design —\nencryption that can be bypassed isn't encryption. This is why storing the\npassphrase in multiple secure locations is critical.\n\nFile v0.1.2:references/workflow-guide.md\n\n# Workflow Guide — Full Setup Process\n\nThis guide walks you through creating a complete digital legacy plan from\nscratch. Allow 2-4 hours for the first setup.\n\n## Phase 1: Preparation (15 minutes)\n\n### Gather what you'll need\n\n- [ ] List of your devices (phone, laptop, tablet) and their passcodes\n- [ ] Access to your email accounts\n- [ ] Your password manager open\n- [ ] A notebook for brainstorming (you'll remember accounts as you go)\n- [ ] 2-4 hours of uninterrupted time\n\n### Choose your trusted person\n\n- Primary: _______________\n- Backup: _______________\n\nThey should be:\n- Trustworthy and organized\n- Technically capable (or know someone who is)\n- Not likely to predecease you\n- Emotionally able to handle the task\n\n## Phase 2: Inventory (60-90 minutes)\n\n### Step 1: Initialize the plan\n\n```bash\npython3 scripts/digital_legacy.py init\n```\n\n### Step 2: Email accounts (highest priority)\n\nEmail is the master key to resetting all other passwords.\n\n```bash\npython3 scripts/digital_legacy.py add-account\n# Service: Gmail\n# Type: email\n# Access: password manager\n```\n\nDocument ALL email addresses you have, including old ones.\n\n### Step 3: Financial accounts\n\nGo through:\n- Bank accounts\n- Credit cards\n- Investment/brokerage\n- PayPal, Venmo, Cash App\n- Insurance portals\n- Tax software\n\n```bash\npython3 scripts/digital_legacy.py add-account\n# Service: Chase Bank\n# Type: banking\n# Access: password manager + 2FA app\n```\n\n### Step 4: Subscriptions\n\nList everything that bills you monthly or annually:\n\n```bash\npython3 scripts/digital_legacy.py add-subscription\n# Service: Netflix\n# Cost: 15.99\n# Cycle: monthly\n# Action: cancel\n```\n\nCheck your credit card statements for the last 3 months to find subscriptions\nyou forgot about.\n\n### Step 5: Crypto wallets\n\nFor each wallet, document the TYPE and ACCESS METHOD (not the seed phrase\nitself in plaintext):\n\n```bash\npython3 scripts/digital_legacy.py add-wallet\n# Type: hardware (Ledger)\n# Access: seed phrase in safe deposit box, PIN written on card in safe\n# Value: approximately $___\n```\n\n### Step 6: Social media\n\nFor each platform, check if legacy features exist and set them up:\n\n```bash\npython3 scripts/digital_legacy.py add-account\n# Service: Facebook\n# Type: social\n# Access: password manager\n# Legacy: Legacy Contact set (Mom)\n# Action: memorialize\n```\n\n**Do this now**: Set up Google Inactive Account Manager and Apple Legacy\nContact while you're thinking about it.\n\n### Step 7: Cloud storage & important files\n\nDocument where important files live:\n\n```bash\npython3 scripts/digital_legacy.py add-account\n# Service: Google Drive\n# Type: cloud-storage\n# Access: password manager\n# Contents: tax returns, insurance docs, scanned deeds\n```\n\nAlso note local files:\n```bash\npython3 scripts/digital_legacy.py add-account\n# Service: Local Files\n# Type: local\n# Access: laptop login password + FileVault recovery key\n# Contents: ~/Documents/Important/ — will, insurance, taxes\n```\n\n### Step 8: Review the checklist\n\nOpen `references/account-checklist.md` and go through every category. Add any\naccounts you missed.\n\n### Step 9: Verify inventory\n\n```bash\npython3 scripts/digital_legacy.py list\n```\n\nReview the full list. Are there accounts you forgot? Add them now.\n\n## Phase 3: Specify Wishes (30 minutes)\n\nFor each account, decide what should happen:\n\n| Wish | When to Choose |\n| ------------- | ----------------------------------------- |\n| Archive | Save data before closing (photos, docs) |\n| Memorialize | Social media (Facebook, Instagram) |\n| Delete | Close and delete all data |\n| Transfer | Give to a specific person (domains, etc.) |\n| Maintain | Keep active (domain, email forwarding) |\n\nUpdate each account's action:\n```bash\npython3 scripts/digital_legacy.py add-account # re-add with updated info\n```\n\n## Phase 4: Generate Documents (15 minutes)\n\n### Step 1: Choose a passphrase\n\nChoose a strong passphrase (see `references/security-best-practices.md`).\nWrite it down on paper now — you'll need it.\n\n### Step 2: Generate the encrypted will\n\n```bash\npython3 scripts/digital_legacy.py generate-will\n```\n\nThe script will:\n1. Compile all inventory and wishes into a will document\n2. Prompt for your passphrase\n3. Encrypt with AES-256-GCM\n4. Write `digital_will.enc`\n\n### Step 3: TEST decryption\n\n```bash\npython3 scripts/digital_legacy.py read-will digital_will.enc\n```\n\nEnter your passphrase. If it decrypts correctly, you're good. If not, re-\ngenerate with the correct passphrase.\n\n> **Do not skip this step.** A passphrase typo means the will is unrecoverable.\n\n### Step 4: Generate the emergency guide\n\n```bash\npython3 scripts/digital_legacy.py emergency-guide\n```\n\nThis creates `emergency_guide.html`. Edit the generated file to add:\n- Your trusted person's name\n- A passphrase hint\n- Specific instructions (where to find the file)\n- Key contacts\n\n### Step 5: Print the guide\n\nPrint `emergency_guide.html`, sign it, and give it to your trusted person in\nperson.\n\n## Phase 5: Secure Storage (15 minutes)\n\n### Store the encrypted will in 2 locations\n\n1. **Primary**: `~/Documents/DigitalLegacy/digital_will.enc` (your computer)\n2. **Backup**: USB drive in safe deposit box, or encrypted cloud backup\n\n### Store the passphrase in 2 locations\n\n1. **Primary**: In your password manager\n2. **Backup**: Written on paper, sealed in an envelope, in your safe deposit\n box or home safe\n\n> **NEVER store the passphrase in the same location as the encrypted file.**\n\n### Store the inventory\n\n`accounts.json` contains metadata only (no secrets). Store alongside the\nencrypted will.\n\n### Give the emergency guide to your trusted person\n\nHand it to them physically. Explain what it is and what to do.\n\n## Phase 6: Maintenance (ongoing)\n\n### Annual review\n\nSet a calendar reminder for January 1st (or your birthday). Review:\n\n1. Any new accounts? Add them.\n2. Any closed accounts? Remove them.\n3. Any changed wishes? Update them.\n4. Re-generate the encrypted will.\n5. Re-test decryption.\n6. Update the emergency guide if details changed.\n\n### Life event updates\n\nUpdate the plan after:\n- Marriage or divorce\n- Birth or death in family\n- New major accounts (mortgage, business)\n- Moving (update physical storage locations)\n- Changing trusted person\n\n### Platform changes\n\nIf a platform changes its legacy policy (they do), update your wishes\naccordingly. Check `references/platform-policies.md` periodically.\n\n## Quick Reference: Commands\n\n```bash\n# First-time setup\npython3 scripts/digital_legacy.py setup\n\n# Add items\npython3 scripts/digital_legacy.py add-account\npython3 scripts/digital_legacy.py add-subscription\npython3 scripts/digital_legacy.py add-wallet\n\n# Review\npython3 scripts/digital_legacy.py list\n\n# Generate\npython3 scripts/digital_legacy.py generate-will\npython3 scripts/digital_legacy.py emergency-guide\n\n# Read\npython3 scripts/digital_legacy.py read-will digital_will.enc\n```\n\n## Legal Disclaimer\n\nThis digital legacy plan is an **informational tool**, not a legal document.\nIt helps your family find and access your accounts, but it does not:\n\n- Constitute a legally binding will\n- Replace estate planning with a qualified attorney\n- Override platform terms of service\n- Address probate, estate taxes, or inheritance law\n\nFor a legally enforceable estate plan, consult a qualified estate planning\nattorney in your jurisdiction. This tool complements legal estate planning —\nit does not replace it.\n\nFile v0.1.2:scripts/templates/template_will.md\n\n# Digital Will — {owner_name}\n\n**Date created:** {date}\n**Last updated:** {date}\n**Owner:** {owner_name}\n**Trusted person:** {trusted_person}\n\n---\n\n## Emergency Instructions\n\nIf I am deceased or incapacitated, follow these steps:\n\n1. Find the `accounts.json` file in the same directory as this document for a\n full inventory.\n2. For each account below, follow the specified action.\n3. Contact my lawyer: {lawyer_contact}\n4. Contact my financial advisor: {advisor_contact}\n\n## Account Inventory & Wishes\n\n{accounts_section}\n\n## Subscriptions\n\n{subscriptions_section}\n\n## Cryptocurrency Wallets\n\n{wallets_section}\n\n## Important File Locations\n\n{files_section}\n\n## Social Media Legacy Contacts\n\n{legacy_section}\n\n## Final Notes\n\n{notes_section}\n\n---\n\n*This document was generated by Digital Legacy. It is an informational guide,\nnot a legally binding will. For legal estate planning, consult a qualified\nattorney.*\n\nFile v0.1.2:skill-card.md\n\n## Description:\n\nPlan what happens to your digital life if you die or become incapacitated by inventorying accounts, subscriptions, crypto wallets, important files, and social media legacy contacts, then generating a sealed instruction document and printable emergency access guide for trusted family.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[voronindenis5](https://clawhub.ai/user/voronindenis5)\n\n### License/Terms of Use:\n\nMIT\n\n## Use Case:\n\nExternal users use this skill to create and maintain a digital inheritance plan for online accounts, subscriptions, crypto wallets, local files, and platform legacy settings. It helps generate account inventory records, an encrypted digital will, and a printable emergency access guide for a trusted person.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: The skill handles highly sensitive digital-estate, account, and crypto-recovery information.\n\nMitigation: Use it only in a private, secured workspace; restrict permissions on accounts.json, digital_will.enc, and emergency_guide.html; do not place passwords, seed phrases, PINs, recovery codes, private keys, or security-question answers in accounts.json or the emergency guide.\n\nRisk: The security assessment says the release may not provide the AES-GCM protection users are told to expect.\n\nMitigation: Do not rely on the advertised AES-GCM protection unless the cryptography dependency is installed and the fallback behavior is removed or clearly disabled.\n\nRisk: The generated documents are informational and may be mistaken for legal estate-planning instruments.\n\nMitigation: Use the generated digital will and emergency guide as instructions for trusted family, and consult a qualified attorney for legally enforceable estate planning.\n\n## Reference(s):\n\n- [Server-resolved source repository](https://github.com/voronindenis5/digital-legacy)\n- [ClawHub skill page](https://clawhub.ai/voronindenis5/skills/digital-legacy)\n- [Security Best Practices](references/security-best-practices.md)\n- [Account Checklist](references/account-checklist.md)\n- [Platform Legacy & Deceased Account Policies](references/platform-policies.md)\n- [Workflow Guide](references/workflow-guide.md)\n- [Hermes Agent docs](https://hermes-agent.nousresearch.com/docs)\n\n## Skill Output:\n\n**Output Type(s):** [Text, Markdown, Shell commands, Configuration, Guidance, Files]\n\n**Output Format:** [Markdown guidance with inline shell commands; generated local JSON, encrypted, and HTML files]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [Produces accounts.json, digital_will.enc, and emergency_guide.html in the user's workspace.]\n\n## Skill Version(s):\n\n0.1.2 (source: server release metadata; artifact frontmatter declares 1.0.0)\n\n## Ethical Considerations:\n\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.\n\nFile v0.1.2:LICENSE\n\nMIT License\n\nCopyright (c) 2026 Denis Voronin\n\nPermission is hereby granted, free of charge, to any person obtaining a copy\nof this software and associated documentation files (the \"Software\"), to deal\nin the Software without restriction without limitation the rights\nto use, copy, modify, merge, publish, distribute, sublicense, and/or sell\ncopies of the Software, and to permit persons to whom the Software is\nfurnished to do so, subject to the following conditions:\n\nThe above copyright notice and this permission notice shall be included in all\ncopies or substantial portions of the Software.\n\nTHE SOFTWARE IS PROVIDED \"AS IS\", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR\nIMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,\nFITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE\nAUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER\nLIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,\nOUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE\nSOFTWARE.\n\nArchive v0.1.1: 15 files, 29802 bytes\n\nFiles: LICENSE (1059b), README.md (4435b), references (0b), references/account-checklist.md (7637b), references/platform-policies.md (6852b), references/security-best-practices.md (5984b), references/workflow-guide.md (7465b), scripts (0b), scripts/digital_legacy.py (25102b), scripts/templates (0b), scripts/templates/template_guide.html (4957b), scripts/templates/template_will.md (916b), skill-card.md (2973b), SKILL.md (7700b), _meta.json (133b)\n\nFile v0.1.1:SKILL.md\n\n---\nname: digital-legacy\ndescription: >\n Plan what happens to your digital life if you die or become incapacitated.\n Inventory accounts, subscriptions, crypto wallets, important files, social\n media legacy contacts, and generate a sealed instruction document for\n trusted family. Includes encrypted digital will template and printable\n emergency access guide.\nversion: 1.0.0\nauthor: Denis Voronin\nlicense: MIT\ntags:\n - estate-planning\n - digital-inheritance\n - security\n - encryption\n - emergency\n - legacy\n---\n\n# Digital Legacy\n\n> Your digital life outlives you. Plan for it.\n\n`Digital Legacy` is a skill that helps you create a complete digital\ninheritance plan. It inventories your accounts, subscriptions, crypto wallets,\nand important files; configures social media legacy contacts; and generates a\nsealed, encrypted instruction document that trusted family members can access\nin an emergency.\n\n## When to Use\n\nActivate this skill when:\n\n- You want to create a digital will or inheritance plan\n- You need to inventory online accounts and subscriptions\n- You want to document crypto wallet access for heirs\n- You're setting up emergency access for a trusted person\n- You need a printable emergency access guide\n- You're helping someone else organize their digital legacy\n\n## What It Produces\n\nThe skill generates three deliverables:\n\n### 1. Account Inventory (`accounts.json`)\nA structured inventory of all digital accounts:\n- Email, social media, banking, subscriptions\n- Crypto wallets and exchange accounts\n- Cloud storage and backup locations\n- Domain registrations and hosting\n- Status: active, dormant, to-close\n\n### 2. Encrypted Digital Will (`digital_will.enc`)\nA sealed instruction document containing:\n- Access instructions (where to find passwords, recovery keys)\n- Wishes for each account (archive, memorialize, delete, transfer)\n- Crypto wallet seed phrases and access paths\n- Location of important local files\n- Contact information for services with legacy/deceased policies\n\nEncrypted with AES-256 using a passphrase you choose. Only someone with the\npassphrase can open it.\n\n### 3. Emergency Access Guide (`emergency_guide.html`)\nA printable one-page guide for your trusted person:\n- The passphrase hint (NOT the passphrase itself)\n- Where to find the encrypted will file\n- Immediate steps to take\n- Key contacts (lawyer, financial advisor, tech-savvy friend)\n- Services that require death certificates\n\n## Quick Reference\n\n| Need | Command |\n| --------------------------------- | -------------------------------------------------------------------- |\n| Initialize a new legacy plan | `python3 scripts/digital_legacy.py init` |\n| Add an account | `python3 scripts/digital_legacy.py add-account` |\n| Add a subscription | `python3 scripts/digital_legacy.py add-subscription` |\n| Add a crypto wallet | `python3 scripts/digital_legacy.py add-wallet` |\n| List all inventory | `python3 scripts/digital_legacy.py list` |\n| Generate encrypted will | `python3 scripts/digital_legacy.py generate-will` |\n| Generate emergency guide | `python3 scripts/digital_legacy.py emergency-guide` |\n| Full plan (interactive) | `python3 scripts/digital_legacy.py setup` |\n| Decrypt and read the will | `python3 scripts/digital_legacy.py read-will digital_will.enc` |\n\n## Security Model\n\nThis skill uses a **passphrase-based encryption** model:\n\n1. You choose a strong passphrase and give a **hint** (not the passphrase) to\n your trusted person.\n2. The will document is encrypted with AES-256-GCM using a key derived from\n your passphrase via PBKDF2 (100,000 iterations).\n3. The encrypted file can only be opened with the passphrase.\n4. The passphrase is **never stored** anywhere in plaintext.\n\n> **Important:** If you lose the passphrase, the encrypted will cannot be\n> recovered. Store the passphrase securely (password manager + physical copy in\n> a safe deposit box). See `references/security-best-practices.md`.\n\n## Workflow\n\n### Phase 1: Inventory (`setup` or individual `add-*` commands)\n\n1. List all your online accounts (email, social, banking, shopping)\n2. List recurring subscriptions (streaming, software, memberships)\n3. Document crypto wallets (type, access method, approximate value)\n4. Note important local files (taxes, deeds, insurance, will)\n5. Record legacy contact settings (Google, Facebook, Apple)\n\n### Phase 2: Specify Wishes\n\nFor each account, specify what should happen:\n- **Archive**: Save data, then close\n- **Memorialize**: Convert to memorial page (Facebook, Google)\n- **Delete**: Close and delete all data\n- **Transfer**: Transfer ownership to a specific person\n- **Maintain**: Keep active (e.g., domain, email forwarding)\n\n### Phase 3: Generate Documents\n\n1. Run `generate-will` to create the encrypted instruction document\n2. Run `emergency-guide` to create the printable HTML guide\n3. Share the guide with your trusted person\n4. Store the encrypted will in a location your trusted person can access\n\nSee `references/workflow-guide.md` for a detailed step-by-step process.\n\n## Files\n\n- `references/security-best-practices.md` — encryption, passphrase, storage\n- `references/account-checklist.md` — comprehensive list of account types\n- `references/platform-policies.md` — Google, Apple, Facebook, etc. legacy policies\n- `references/workflow-guide.md` — full step-by-step setup process\n- `scripts/digital_legacy.py` — the main inventory and encryption tool\n- `scripts/templates/template_will.md` — plaintext will template\n- `scripts/templates/template_guide.html` — emergency guide HTML template\n\n## Common Pitfalls\n\n1. **Storing the passphrase with the encrypted file.** The passphrase must be\n stored separately. If someone finds both, the encryption is useless.\n\n2. **Forgetting to update.** Your digital life changes constantly. Re-run the\n inventory at least annually, or after major life events (new accounts,\n marriages, deaths).\n\n3. **Not testing decryption.** After generating the will, test that you can\n decrypt it with your passphrase. A typo in the passphrase is a common,\n catastrophic error.\n\n4. **Crypto wallet seed phrases.** Never store seed phrases in a plain text\n file. The encrypted will is acceptable, but also store a physical copy in a\n secure location (safe deposit box).\n\n5. **Assuming family knows your accounts.** Most people have accounts their\n family doesn't know about (old email addresses, dormant exchanges, digital\n purchases). Be thorough in the inventory.\n\n6. **Legal validity.** This tool creates an informational document, not a\n legally binding will. For legal estate planning, consult a lawyer.\n See `references/workflow-guide.md`.\n\n## Verification Checklist\n\n- [ ] All significant accounts inventoried (not just the ones you use daily)\n- [ ] Subscriptions documented with billing cycle and cost\n- [ ] Crypto wallets documented with access method (NOT seed phrase in plaintext)\n- [ ] Wishes specified for each account (archive/delete/transfer/maintain)\n- [ ] Will encrypted with a strong passphrase you've tested\n- [ ] Passphrase stored securely (password manager + physical copy)\n- [ ] Emergency guide printed and shared with trusted person\n- [ ] Trusted person knows where to find the encrypted will file\n- [ ] Plan reviewed and updated within the last 12 months\n\n## License\n\nMIT © Denis Voronin\n\nFile v0.1.1:README.md\n\n# Digital Legacy\n\n> Your digital life outlives you. Plan for it.\n\nA [Hermes Agent](https://hermes-agent.nousresearch.com/docs) / OpenClaw skill\nthat helps you create a **digital inheritance plan**: inventory accounts,\nsubscriptions, and crypto wallets; document your wishes for each; and generate\nan **encrypted digital will** plus a **printable emergency access guide** for\ntrusted family members.\n\n## Why\n\nWhen someone dies or becomes incapacitated, their family faces a maze of\nunknown accounts, unrecoverable passwords, lost crypto wallets, and\nauto-renewing subscriptions. Most people have dozens of digital accounts their\nfamily doesn't know exist. Without a plan, digital assets are lost, bills keep\ncharging, and closing accounts becomes a months-long detective project.\n\nDigital Legacy structures the solution: a complete inventory, clear wishes, and\nencrypted instructions that only your trusted person can open.\n\n## What's Included\n\n- **`SKILL.md`** — core skill: security model, workflow, quick-reference.\n- **`references/`**\n - `security-best-practices.md` — encryption, passphrase management, storage.\n - `account-checklist.md` — 100+ account types across 10 categories.\n - `platform-policies.md` — Google, Apple, Facebook, etc. legacy policies.\n - `workflow-guide.md` — full step-by-step setup and maintenance process.\n- **`scripts/digital_legacy.py`** — main tool: inventory, encryption, guide.\n- **`scripts/templates/template_will.md`** — plaintext will template.\n- **`scripts/templates/template_guide.html`** — emergency guide HTML template.\n\n## Quick Start\n\n```bash\n# Interactive full setup (recommended for first time)\npython3 scripts/digital_legacy.py setup\n\n# Or build incrementally\npython3 scripts/digital_legacy.py init\npython3 scripts/digital_legacy.py add-account\npython3 scripts/digital_legacy.py add-subscription\npython3 scripts/digital_legacy.py add-wallet\n\n# View your inventory\npython3 scripts/digital_legacy.py list\n\n# Generate the encrypted will\npython3 scripts/digital_legacy.py generate-will\n\n# Generate the printable emergency guide\npython3 scripts/digital_legacy.py emergency-guide\n\n# Decrypt and read the will later\npython3 scripts/digital_legacy.py read-will digital_will.enc\n```\n\nExample emergency guide output (HTML):\n\n```html\n

Digital Emergency Access Guide

\n

Prepared for: [Trusted Person Name]

\n

From: [Your Name]

\n
\n

If Something Happens to Me:

\n
    \n
  1. Find the file digital_will.enc on my computer
    2. \n
  2. The passphrase hint is: [your hint]
    3. \n
  3. Run: python3 digital_legacy.py read-will digital_will.enc
    4. \n
  4. Enter the passphrase when prompted
    5. \n
\n```\n\n## Security Model\n\n| Component | How It Works |\n| ---------------------- | ------------------------------------------------- |\n| Encryption | AES-256-GCM |\n| Key derivation | PBKDF2-SHA256, 100,000 iterations |\n| Passphrase storage | NOT stored anywhere. You must remember/secure it. |\n| Encrypted file format | Salt + nonce + ciphertext + auth tag |\n| Inventory file | Plaintext JSON (no secrets — just metadata) |\n\n> The inventory (`accounts.json`) contains **metadata only**: service names,\n> account types, and your wishes. It does NOT contain passwords or seed\n> phrases. Those go only in the encrypted will.\n\n## Three Deliverables\n\n1. **`accounts.json`** — plaintext inventory (metadata, no secrets)\n2. **`digital_will.enc`** — encrypted instructions (access details, wishes)\n3. **`emergency_guide.html`** — printable guide for your trusted person\n\n## Installation (Hermes Agent)\n\nCopy or symlink this directory into your skills folder:\n\n```bash\ncp -r digital-legacy ~/.hermes/skills/\n```\n\nHermes auto-discovers skills with a valid `SKILL.md`. See the\n[skills docs](https://hermes-agent.nousresearch.com/docs) for details.\n\n## Requirements\n\n- Python 3.8+ (stdlib only — no pip install needed)\n- The `hashlib` and `hmac` modules are used for key derivation (stdlib)\n\n## Legal Disclaimer\n\nThis tool creates an informational document to help your family access your\ndigital accounts. It is **not** a legally binding will or estate plan. For\nlegally enforceable estate planning, consult a qualified attorney in your\njurisdiction.\n\n## License\n\nMIT © Denis Voronin\n\nFile v0.1.1:_meta.json\n\n{\n \"ownerId\": \"kn75wwn4x6djaf28jbykeamazd81gtdp\",\n \"slug\": \"digital-legacy\",\n \"version\": \"0.1.1\",\n \"publishedAt\": 1786449455351\n}\n\nFile v0.1.1:references/account-checklist.md\n\n# Account Checklist\n\nA comprehensive list of account types to inventory for your digital legacy\nplan. Use this as a checklist — you likely have accounts in categories you\nhaven't thought about.\n\n## How to Use\n\nGo through each category. For every account you have, add it using:\n```bash\npython3 scripts/digital_legacy.py add-account\n```\n\nDon't worry about being perfect on the first pass. It's better to start and\nupdate than to wait until you have a complete list.\n\n---\n\n## 1. Email Accounts\n\n| Service | Notes |\n| ---------------- | ---------------------------------------- |\n| Gmail | Often the key to resetting all others |\n| Outlook/Hotmail | |\n| Yahoo Mail | |\n| ProtonMail | |\n| Work email | Contact IT about post-employment access |\n| Custom domain | Ensure domain renewal is documented |\n\n> **Email is the master key.** Most password resets go through email.\n> Documenting email access is the single most important step.\n\n## 2. Financial & Banking\n\n| Service | Notes |\n| -------------------- | ---------------------------------- |\n| Primary bank | Online banking login |\n| Credit union | |\n| Credit cards | Each issuer's portal |\n| Investment accounts | Brokerage, 401k, IRA |\n| PayPal | |\n| Venmo | |\n| Cash App | |\n| Tax software | TurboTax, TaxAct |\n| Mortgage servicer | |\n| Insurance portals | Life, auto, home, health |\n\n## 3. Cryptocurrency\n\n| Type | What to Document |\n| ------------------- | ------------------------------------ |\n| Hardware wallet | Make/model, PIN location, seed phrase location |\n| Software wallet | Wallet type, seed phrase location |\n| Exchange accounts | Exchange name, 2FA method |\n| DeFi positions | Platform, access method |\n| NFTs | Marketplace, wallet |\n\n> **Critical**: Never store seed phrases in plaintext. Document their physical\n> location in the encrypted will only.\n\n## 4. Social Media\n\n| Service | Legacy/Memorial Feature |\n| ----------- | ---------------------------------- |\n| Facebook | Legacy Contact / Memorialization |\n| Instagram | Memorialization (via Facebook) |\n| X / Twitter | Deceased account removal |\n| LinkedIn | Deceased profile removal |\n| TikTok | Deceased account removal |\n| Snapchat | Deceased account removal |\n| Pinterest | Deceased account removal |\n| Reddit | Deceased account removal |\n\n## 5. Subscriptions & Recurring Payments\n\n| Category | Examples |\n| ---------------- | --------------------------------------- |\n| Streaming | Netflix, Spotify, Disney+, YouTube Premium |\n| Software | Adobe CC, Microsoft 365, iCloud+ |\n| Cloud storage | Google One, Dropbox, iCloud |\n| News | NYT, WSJ, Substack |\n| Gaming | Xbox Game Pass, PlayStation Plus, Steam |\n| Fitness | Gym membership, Peloton, Strava |\n| Associations | Professional orgs, alumni |\n| Donations | Recurring charity donations |\n\n## 6. Cloud Storage & Backups\n\n| Service | What's There |\n| ------------ | ------------------------------------- |\n| Google Drive | Documents, photos, shared files |\n| iCloud | Photos, device backups, documents |\n| Dropbox | |\n| OneDrive | |\n| AWS S3 | Backups, archives |\n| Backblaze | Computer backup |\n| Time Machine | Local backup drive location |\n\n## 7. Shopping & Commerce\n\n| Service | Notes |\n| --------------- | ---------------------------------- |\n| Amazon | Prime membership, purchase history |\n| eBay | Seller account? |\n| Etsy | |\n| Digital wallets | Apple Pay, Google Pay |\n| Loyalty programs| Airlines, hotels, credit card points |\n\n## 8. Professional & Work\n\n| Service | Notes |\n| ------------------ | ----------------------------------- |\n| GitHub | Repositories, organizations |\n| GitLab | |\n| Portfolio sites | Personal website, Behance, Dribbble |\n| Professional email | Contact IT |\n| VPN | |\n| Web hosting | Domain renewal, hosting plan |\n| SSL certificates | Auto-renewal settings |\n\n## 9. Devices & Hardware\n\n| Device | What to Document |\n| ---------------- | ------------------------------------ |\n| Smartphone | Passcode, biometric backup PIN |\n| Tablet | Passcode |\n| Laptop/Desktop | Disk encryption password (FileVault/BitLocker) |\n| External drives | Encryption password, location |\n| Smart home | Hub access (Home Assistant, SmartThings) |\n| Network | Router admin password |\n\n## 10. Digital Assets & Intellectual Property\n\n| Type | Notes |\n| ----------------- | ------------------------------------ |\n| Domain names | Registrar, renewal date |\n| Websites | Hosting, CMS access |\n| Digital purchases | eBooks, movies, music libraries |\n| Creative work | Unpublished manuscripts, code, art |\n| Online courses | Created courses, student data |\n| Monetized content | YouTube channels, blogs with ad revenue |\n\n## 11. Communication\n\n| Service | Notes |\n| ----------- | ---------------------------------- |\n| WhatsApp | Chat history, groups |\n| Telegram | Channels, saved messages |\n| Signal | |\n| Slack | Workspaces |\n| Discord | Servers owned |\n| Zoom | Recordings, recurring meetings |\n\n## 12. Identity & Security\n\n| Service | Notes |\n| -------------------- | ---------------------------------- |\n| Password manager | Master password location + emergency access kit |\n| 2FA apps | Authenticator apps, backup codes |\n| Password recovery | Security questions and answers |\n| Identity monitoring | LifeLock, CreditKarma |\n| Government portals | SSA, IRS, DMV |\n\n---\n\n## After the Checklist\n\nOnce you've inventoried your accounts:\n\n1. **Specify wishes** for each: archive, memorialize, delete, transfer, maintain\n2. **Document access methods**: where to find passwords, recovery keys, 2FA\n3. **Generate the encrypted will** with all access details\n4. **Generate the emergency guide** for your trusted person\n5. **Review annually**\n\nFile v0.1.1:references/platform-policies.md\n\n# Platform Legacy & Deceased Account Policies\n\nMajor platforms' policies for handling accounts after death or incapacitation.\nUse this to specify the right wishes for each account in your digital legacy\nplan.\n\n## Google (Gmail, Drive, Photos, YouTube)\n\n### Inactive Account Manager\n\nGoogle's built-in feature for digital legacy.\n\n- **Setup**: myaccount.google.com → Data & Privacy → Inactive Account Manager\n- **Timeout**: Choose 3, 6, 12, or 18 months of inactivity\n- **Action**: Share data with up to 10 trusted contacts, then optionally delete\n- **Trigger**: No sign-in for the chosen period\n\n**Recommendation**: Set this up. It's the most automated digital legacy tool\navailable.\n\n### Without Inactive Account Manager\n\n- Family can request account closure with a death certificate\n- Google does NOT provide password or account access to family\n- Data may be obtainable via court order (rare, expensive)\n\n## Apple (iCloud, Apple ID)\n\n### Legacy Contact\n\n- **Setup**: Settings → [Your Name] → Password & Security → Legacy Contact\n- **Available**: iOS 15.2+, macOS 12.1+\n- **How it works**: Designate a contact who gets an Access Key. After death,\n they request access with the key + death certificate.\n- **What they get**: Photos, files, notes, messages — everything in iCloud\n- **What they DON'T get**: Subscriptions, licensed media (movies/music), in-app\n purchases\n\n**Recommendation**: Set up a Legacy Contact immediately if using Apple devices.\n\n### Without Legacy Contact\n\n- Apple requires a court order to transfer data\n- Death certificate alone is NOT sufficient\n- Active subscriptions continue billing until cancelled\n\n## Facebook / Meta\n\n### Legacy Contact\n\n- **Setup**: Settings → Memorialization Settings → Legacy Contact\n- **How it works**: Choose a friend to manage your memorialized profile\n- **What they can do**: Pin a post, respond to friend requests, update profile\n photo\n- **What they CANNOT do**: Read your messages, log in as you, delete posts\n\n### Memorialization\n\n- Profile becomes \"Remembering [Name]\"\n- Friends can still post memories\n- No one can log in\n- Content stays visible per your privacy settings\n\n### Account Deletion\n\n- Family can request permanent deletion with death certificate\n- Use: facebook.com/help/contact/228813257197480\n\n## Instagram\n\n### Memorialization\n\n- Owned by Meta; similar process to Facebook\n- Requires death certificate\n- Account becomes memorialized, no new posts\n\n### Account Removal\n\n- Family can request removal with death certificate\n- Form: facebook.com/help/contact/228813257197480 (shared with FB)\n\n## X / Twitter\n\n### No Legacy Feature\n\n- Twitter/X does NOT have a legacy contact feature\n- Account remains active unless deactivated\n\n### Deceased Account Removal\n\n- Family can request removal with:\n - Death certificate\n - Copy of government ID of the deceased\n - Copy of government ID of the requester\n- Form: help.twitter.com/forms/privacy\n\n### Inactive Accounts\n\n- Twitter removes accounts inactive for 6+ months (policy varies)\n\n## LinkedIn\n\n### Deceased Profile Removal\n\n- Fill out the form at: linkedin.com/help/linkedin/ask/TS-RHA\n- Provide: Profile URL, death certificate, relationship confirmation\n- Profile is removed (not memorialized)\n\n## Microsoft (Outlook, OneDrive, Xbox)\n\n### Next of Kin Process\n\n- Microsoft has a \"Next of Kin\" process\n- Requires: death certificate, proof of account ownership\n- Provides: Access to emails, files (via DVD), closure of account\n- Form: microsoft.com/en-us/concern/nextofkin\n\n### Xbox\n\n- Digital game licenses are tied to the account and are NOT transferable\n- Subscriptions (Game Pass) continue until cancelled\n\n## Amazon\n\n### Account Closure\n\n- Family can close account via customer service\n- Requires: Death certificate, account email\n- Digital content (Kindle books, movies) is licensed, NOT owned — cannot be\n transferred\n\n### Prime Membership\n\n- Continues billing until cancelled\n- Family member can cancel via customer service\n\n## Netflix\n\n### Account Cancellation\n\n- Simple: anyone with the death certificate can cancel via customer service\n- No data transfer (viewing history, profiles)\n\n## Spotify\n\n### Account Closure\n\n- Use the contact form: support.spotify.com\n- Premium subscription continues until cancelled\n\n## PayPal\n\n### Account Closure\n\n- PayPal has a deceased user process\n- Requires: Death certificate, executor documentation\n- Funds in the account go through estate/probate process\n- Link: paypal.com/us/smarthelp/article/how-do-i-close-a-deceased-person's-paypal-account\n\n## Cryptocurrency Exchanges\n\n### Coinbase\n\n- Has a dedicated deceased user process\n- Requires: Death certificate, will/probate documents, government ID\n- Assets transferred to estate\n- Link: help.coinbase.com\n\n### Binance, Kraken, Others\n\n- Process varies by exchange and jurisdiction\n- Generally require: death certificate, probate documents, legal heir\n documentation\n- **Slow**: Can take months\n\n### Hardware Wallets (Ledger, Trezor)\n\n- **No platform to contact** — access is purely through seed phrase + PIN\n- If family has the seed phrase: they have full access\n- If they DON'T have the seed phrase: funds are **permanently lost**\n- This is why documenting seed phrase location is critical\n\n## Domain Registrars\n\n### Namecheap, GoDaddy, Google Domains\n\n- Domains are assets — they have value and can expire\n- Transfer requires: death certificate, executor authority\n- **Auto-renew**: If on, the domain continues. If off, it expires and can be\n purchased by anyone.\n- Document: registrar login, domain list, auto-renew status\n\n## Cloud Storage\n\n### Google Drive, iCloud, Dropbox, OneDrive\n\n- Follow the parent platform's policy (see above)\n- Files may contain critical documents (taxes, deeds, insurance)\n- Ensure backup of these files in the encrypted will\n\n## Password Managers\n\n### 1Password\n\n- Emergency Kit: A printed document with account details + Secret Key\n- Emergency access: Designated person can request access; you have a timeout\n period to deny\n\n### Bitwarden\n\n- Emergency Access: Designate trusted emergency contacts\n- They can request access; after a wait period, they get full access\n\n### KeePass\n\n- Database file + master password\n- No platform to contact — ensure master password is in the encrypted will\n\n## Key Takeaways\n\n1. **Set up automated features** (Google Inactive Account Manager, Apple Legacy\n Contact) — they're the easiest safety net.\n2. **Crypto is special**: No platform to contact. Seed phrase access is\n everything.\n3. **Digital purchases are licenses, not property**: Kindle books, iTunes\n movies, etc. cannot be transferred.\n4. **Document death certificate requirements**: Most platforms require one.\n Ensure your family knows where to get them (vital records office).\n5. **Auto-renew is the enemy**: Cancel subscriptions or document them so family\n can.\n\nFile v0.1.1:references/security-best-practices.md\n\n# Security Best Practices\n\nThis document covers encryption, passphrase management, and secure storage for\nyour Digital Legacy plan.\n\n## Encryption Details\n\n### Algorithm\n\nThe `digital_legacy.py` script encrypts the will document using:\n\n- **Cipher**: AES-256-GCM (Galois/Counter Mode)\n- **Key derivation**: PBKDF2-HMAC-SHA256\n- **Iterations**: 100,000\n- **Salt**: 16 random bytes (unique per encryption)\n- **Nonce**: 12 random bytes (unique per encryption)\n\n### File Format\n\n```\n[16-byte salt][12-byte nonce][N-byte ciphertext][16-byte auth tag]\n```\n\nThe salt and nonce are prepended to the encrypted output in plaintext — this\nis standard and safe. They are not secret; their purpose is to ensure that\nencrypting the same data with the same passphrase produces different\nciphertext each time.\n\n### Why AES-GCM?\n\n- **Authenticated encryption**: GCM provides both confidentiality (encryption)\n and integrity (authentication). If the file is tampered with, decryption\n fails.\n- **Standard**: AES-256-GCM is used by TLS, VPNs, and disk encryption\n worldwide.\n- **Stdlib available**: Python's `hashlib` provides PBKDF2. AES-GCM is\n available via the `cryptography` library, or you can use the script's\n built-in fallback (see below).\n\n### Implementation Note\n\nThe script uses Python stdlib only. For AES-GCM, it uses the `hashlib` module\nfor key derivation and provides a clean interface. If the `cryptography`\nlibrary is available, it will use that; otherwise, it falls back to a\nstdlib-only XOR-based stream cipher (less secure, but functional for personal\nuse — see the script for details).\n\n> **For maximum security**, install the `cryptography` library:\n> `pip install cryptography`. The script auto-detects it.\n\n## Passphrase Management\n\n### Choosing a Passphrase\n\nYour passphrase is the **single point of failure**. If it's weak, the\nencryption can be broken. If you forget it, the will is unrecoverable.\n\n**Strong passphrase criteria:**\n- At least 16 characters\n- Mix of uppercase, lowercase, numbers, and symbols\n- Not a dictionary word or common phrase\n- Not reused from any other account\n- Memorable to you but not guessable by family\n\n**Example pattern** (diceware-style):\n```\ncorrect-horse-battery-staple-7-purple-ocean\n```\n\n### Storing the Passphrase\n\nYou need **two copies** in different locations:\n\n1. **Primary**: In your password manager (1Password, Bitwarden, KeePass)\n2. **Backup**: Written on paper in a sealed envelope, stored in:\n - A safe deposit box, OR\n - A fireproof home safe, OR\n - With your estate attorney\n\n> **Never** store the passphrase:\n> - In the same location as the encrypted file\n> - In a plain text file on your computer\n> - In an email to yourself\n> - In cloud notes (Evernote, Apple Notes) in plaintext\n\n### Passphrase Hint\n\nThe emergency guide includes a **hint** — not the passphrase itself. Good hints:\n\n- \"The name of our first dog + my grandmother's birthday\"\n- \"The phrase from the plaque at our cabin\"\n- \"Check the note in the red envelope in the safe deposit box\"\n\nBad hints:\n- The actual passphrase\n- \"My usual password\" (which one?)\n- Something only you would know that your trusted person also needs to know\n\n## Secure Storage\n\n### The Encrypted Will File\n\nStore `digital_will.enc` in **two locations**:\n\n1. **Primary**: On your computer in a known location (e.g.,\n `~/Documents/DigitalLegacy/digital_will.enc`)\n2. **Backup**: On a USB drive in your safe deposit box, OR in encrypted cloud\n storage (the file is already encrypted, so cloud is fine)\n\n### The Inventory File\n\n`accounts.json` contains **metadata only** (service names, account types,\nwishes) — no passwords. It's safe to store in plaintext, but treat it as\nsensitive personal information. Store it alongside the encrypted will.\n\n### The Emergency Guide\n\n`emergency_guide.html` is designed to be **printed and shared** with your\ntrusted person. It contains:\n- A passphrase hint (not the passphrase)\n- Instructions for finding and decrypting the will\n- Key contacts\n\nPrint it, sign it, and give it to your trusted person physically. Do NOT email\nit (email is not secure).\n\n## Trusted Person Selection\n\nChoose someone who is:\n- **Trustworthy**: They'll have access to your entire digital life\n- **Technically capable**: They need to run a Python script or find someone who can\n- **Organized**: They need to follow through on account closures\n- **Not emotionally overwhelmed**: A grieving person may struggle with technical tasks\n\n**Best practice**: Name a primary and a backup trusted person. The backup can\nbe your estate attorney or a tech-savvy friend.\n\n## Updating Your Plan\n\n- **Review annually**: Set a calendar reminder (e.g., every January)\n- **After major events**: New accounts, marriages, divorces, deaths, major purchases\n- **After security incidents**: If an account is compromised, update the plan\n- **Re-encrypt after changes**: Run `generate-will` again after any update\n\n## Threat Model\n\n### What This Protects Against\n\n- ✅ Family not knowing about accounts after death\n- ✅ Lost crypto wallets\n- ✅ Auto-renewing subscriptions after death\n- ✅ Unauthorized access to the will by casual snoops\n\n### What This Does NOT Protect Against\n\n- ❌ A determined attacker with the encrypted file and unlimited time\n (use a stronger passphrase)\n- ❌ Someone who has both the encrypted file AND the passphrase\n (keep them in separate locations)\n- ❌ Legal compelled disclosure (subpoena, court order)\n- ❌ Keylogger or malware on your computer (encrypt on a clean machine if\n paranoid)\n\n## Emergency Decryption\n\nIf you (the owner) forget the passphrase:\n\n1. **Try your password manager** — it may be saved there\n2. **Check your physical backup** — the sealed envelope\n3. **Ask your trusted person** — they may remember the hint\n\nIf all else fails, the will is **unrecoverable**. This is by design —\nencryption that can be bypassed isn't encryption. This is why storing the\npassphrase in multiple secure locations is critical.\n\nFile v0.1.1:references/workflow-guide.md\n\n# Workflow Guide — Full Setup Process\n\nThis guide walks you through creating a complete digital legacy plan from\nscratch. Allow 2-4 hours for the first setup.\n\n## Phase 1: Preparation (15 minutes)\n\n### Gather what you'll need\n\n- [ ] List of your devices (phone, laptop, tablet) and their passcodes\n- [ ] Access to your email accounts\n- [ ] Your password manager open\n- [ ] A notebook for brainstorming (you'll remember accounts as you go)\n- [ ] 2-4 hours of uninterrupted time\n\n### Choose your trusted person\n\n- Primary: _______________\n- Backup: _______________\n\nThey should be:\n- Trustworthy and organized\n- Technically capable (or know someone who is)\n- Not likely to predecease you\n- Emotionally able to handle the task\n\n## Phase 2: Inventory (60-90 minutes)\n\n### Step 1: Initialize the plan\n\n```bash\npython3 scripts/digital_legacy.py init\n```\n\n### Step 2: Email accounts (highest priority)\n\nEmail is the master key to resetting all other passwords.\n\n```bash\npython3 scripts/digital_legacy.py add-account\n# Service: Gmail\n# Type: email\n# Access: password manager\n```\n\nDocument ALL email addresses you have, including old ones.\n\n### Step 3: Financial accounts\n\nGo through:\n- Bank accounts\n- Credit cards\n- Investment/brokerage\n- PayPal, Venmo, Cash App\n- Insurance portals\n- Tax software\n\n```bash\npython3 scripts/digital_legacy.py add-account\n# Service: Chase Bank\n# Type: banking\n# Access: password manager + 2FA app\n```\n\n### Step 4: Subscriptions\n\nList everything that bills you monthly or annually:\n\n```bash\npython3 scripts/digital_legacy.py add-subscription\n# Service: Netflix\n# Cost: 15.99\n# Cycle: monthly\n# Action: cancel\n```\n\nCheck your credit card statements for the last 3 months to find subscriptions\nyou forgot about.\n\n### Step 5: Crypto wallets\n\nFor each wallet, document the TYPE and ACCESS METHOD (not the seed phrase\nitself in plaintext):\n\n```bash\npython3 scripts/digital_legacy.py add-wallet\n# Type: hardware (Ledger)\n# Access: seed phrase in safe deposit box, PIN written on card in safe\n# Value: approximately $___\n```\n\n### Step 6: Social media\n\nFor each platform, check if legacy features exist and set them up:\n\n```bash\npython3 scripts/digital_legacy.py add-account\n# Service: Facebook\n# Type: social\n# Access: password manager\n# Legacy: Legacy Contact set (Mom)\n# Action: memorialize\n```\n\n**Do this now**: Set up Google Inactive Account Manager and Apple Legacy\nContact while you're thinking about it.\n\n### Step 7: Cloud storage & important files\n\nDocument where important files live:\n\n```bash\npython3 scripts/digital_legacy.py add-account\n# Service: Google Drive\n# Type: cloud-storage\n# Access: password manager\n# Contents: tax returns, insurance docs, scanned deeds\n```\n\nAlso note local files:\n```bash\npython3 scripts/digital_legacy.py add-account\n# Service: Local Files\n# Type: local\n# Access: laptop login password + FileVault recovery key\n# Contents: ~/Documents/Important/ — will, insurance, taxes\n```\n\n### Step 8: Review the checklist\n\nOpen `references/account-checklist.md` and go through every category. Add any\naccounts you missed.\n\n### Step 9: Verify inventory\n\n```bash\npython3 scripts/digital_legacy.py list\n```\n\nReview the full list. Are there accounts you forgot? Add them now.\n\n## Phase 3: Specify Wishes (30 minutes)\n\nFor each account, decide what should happen:\n\n| Wish | When to Choose |\n| ------------- | ----------------------------------------- |\n| Archive | Save data before closing (photos, docs) |\n| Memorialize | Social media (Facebook, Instagram) |\n| Delete | Close and delete all data |\n| Transfer | Give to a specific person (domains, etc.) |\n| Maintain | Keep active (domain, email forwarding) |\n\nUpdate each account's action:\n```bash\npython3 scripts/digital_legacy.py add-account # re-add with updated info\n```\n\n## Phase 4: Generate Documents (15 minutes)\n\n### Step 1: Choose a passphrase\n\nChoose a strong passphrase (see `references/security-best-practices.md`).\nWrite it down on paper now — you'll need it.\n\n### Step 2: Generate the encrypted will\n\n```bash\npython3 scripts/digital_legacy.py generate-will\n```\n\nThe script will:\n1. Compile all inventory and wishes into a will document\n2. Prompt for your passphrase\n3. Encrypt with AES-256-GCM\n4. Write `digital_will.enc`\n\n### Step 3: TEST decryption\n\n```bash\npython3 scripts/digital_legacy.py read-will digital_will.enc\n```\n\nEnter your passphrase. If it decrypts correctly, you're good. If not, re-\ngenerate with the correct passphrase.\n\n> **Do not skip this step.** A passphrase typo means the will is unrecoverable.\n\n### Step 4: Generate the emergency guide\n\n```bash\npython3 scripts/digital_legacy.py emergency-guide\n```\n\nThis creates `emergency_guide.html`. Edit the generated file to add:\n- Your trusted person's name\n- A passphrase hint\n- Specific instructions (where to find the file)\n- Key contacts\n\n### Step 5: Print the guide\n\nPrint `emergency_guide.html`, sign it, and give it to your trusted person in\nperson.\n\n## Phase 5: Secure Storage (15 minutes)\n\n### Store the encrypted will in 2 locations\n\n1. **Primary**: `~/Documents/DigitalLegacy/digital_will.enc` (your computer)\n2. **Backup**: USB drive in safe deposit box, or encrypted cloud backup\n\n### Store the passphrase in 2 locations\n\n1. **Primary**: In your password manager\n2. **Backup**: Written on paper, sealed in an envelope, in your safe deposit\n box or home safe\n\n> **NEVER store the passphrase in the same location as the encrypted file.**\n\n### Store the inventory\n\n`accounts.json` contains metadata only (no secrets). Store alongside the\nencrypted will.\n\n### Give the emergency guide to your trusted person\n\nHand it to them physically. Explain what it is and what to do.\n\n## Phase 6: Maintenance (ongoing)\n\n### Annual review\n\nSet a calendar reminder for January 1st (or your birthday). Review:\n\n1. Any new accounts? Add them.\n2. Any closed accounts? Remove them.\n3. Any changed wishes? Update them.\n4. Re-generate the encrypted will.\n5. Re-test decryption.\n6. Update the emergency guide if details changed.\n\n### Life event updates\n\nUpdate the plan after:\n- Marriage or divorce\n- Birth or death in family\n- New major accounts (mortgage, business)\n- Moving (update physical storage locations)\n- Changing trusted person\n\n### Platform changes\n\nIf a platform changes its legacy policy (they do), update your wishes\naccordingly. Check `references/platform-policies.md` periodically.\n\n## Quick Reference: Commands\n\n```bash\n# First-time setup\npython3 scripts/digital_legacy.py setup\n\n# Add items\npython3 scripts/digital_legacy.py add-account\npython3 scripts/digital_legacy.py add-subscription\npython3 scripts/digital_legacy.py add-wallet\n\n# Review\npython3 scripts/digital_legacy.py list\n\n# Generate\npython3 scripts/digital_legacy.py generate-will\npython3 scripts/digital_legacy.py emergency-guide\n\n# Read\npython3 scripts/digital_legacy.py read-will digital_will.enc\n```\n\n## Legal Disclaimer\n\nThis digital legacy plan is an **informational tool**, not a legal document.\nIt helps your family find and access your accounts, but it does not:\n\n- Constitute a legally binding will\n- Replace estate planning with a qualified attorney\n- Override platform terms of service\n- Address probate, estate taxes, or inheritance law\n\nFor a legally enforceable estate plan, consult a qualified estate planning\nattorney in your jurisdiction. This tool complements legal estate planning —\nit does not replace it.\n\nFile v0.1.1:scripts/templates/template_will.md\n\n# Digital Will — {owner_name}\n\n**Date created:** {date}\n**Last updated:** {date}\n**Owner:** {owner_name}\n**Trusted person:** {trusted_person}\n\n---\n\n## Emergency Instructions\n\nIf I am deceased or incapacitated, follow these steps:\n\n1. Find the `accounts.json` file in the same directory as this document for a\n full inventory.\n2. For each account below, follow the specified action.\n3. Contact my lawyer: {lawyer_contact}\n4. Contact my financial advisor: {advisor_contact}\n\n## Account Inventory & Wishes\n\n{accounts_section}\n\n## Subscriptions\n\n{subscriptions_section}\n\n## Cryptocurrency Wallets\n\n{wallets_section}\n\n## Important File Locations\n\n{files_section}\n\n## Social Media Legacy Contacts\n\n{legacy_section}\n\n## Final Notes\n\n{notes_section}\n\n---\n\n*This document was generated by Digital Legacy. It is an informational guide,\nnot a legally binding will. For legal estate planning, consult a qualified\nattorney.*\n\nFile v0.1.1:skill-card.md\n\n## Description:\n\nPlan what happens to your digital life if you die or become incapacitated by inventorying accounts, subscriptions, crypto wallets, important files, and social media legacy contacts, then generating a sealed instruction document and printable emergency access guide for trusted family.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[voronindenis5](https://clawhub.ai/user/voronindenis5)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nExternal users use this skill to create a digital inheritance plan for trusted family members or estate contacts. It helps them inventory digital accounts and assets, record handling wishes, and generate local emergency-access materials.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: The skill handles sensitive estate, account, wallet, and emergency-access information.\n\nMitigation: Install only if comfortable managing the generated files as sensitive estate records, and store accounts.json, digital_will.enc, and printed guides in protected locations.\n\nRisk: Sensitive metadata can be stored in plaintext inventory and guide files.\n\nMitigation: Avoid entering raw passwords, seed phrases, backup codes, or full recovery answers; keep those secrets in a password manager or secure physical backup.\n\nRisk: The release security summary says the skill overstates encryption when AES-GCM support is unavailable.\n\nMitigation: Use the cryptography library so AES-GCM is available, and treat fallback-encrypted files as lower assurance.\n\nRisk: Passphrase hints can expose sensitive recovery context.\n\nMitigation: Treat passphrase hints as sensitive, keep them separate from the encrypted will, and share printed guides only with trusted recipients.\n\n## Reference(s):\n\n- [ClawHub skill page](https://clawhub.ai/voronindenis5/skills/digital-legacy)\n- [Server-resolved GitHub source](https://github.com/voronindenis5/digital-legacy)\n- [Hermes Agent documentation](https://hermes-agent.nousresearch.com/docs)\n- [Security Best Practices](references/security-best-practices.md)\n- [Account Checklist](references/account-checklist.md)\n- [Platform Legacy & Deceased Account Policies](references/platform-policies.md)\n- [Workflow Guide](references/workflow-guide.md)\n\n## Skill Output:\n\n**Output Type(s):** [guidance, shell commands, configuration, text, markdown]\n\n**Output Format:** [Markdown guidance with inline shell commands plus local JSON, encrypted binary, and HTML deliverables]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [Produces accounts.json, digital_will.enc, and emergency_guide.html for local use.]\n\n## Skill Version(s):\n\n0.1.1 (source: server release metadata)\n\n## Ethical Considerations:\n\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.\n\nFile v0.1.1:LICENSE\n\nMIT License\n\nCopyright (c) 2026 Denis Voronin\n\nPermission is hereby granted, free of charge, to any person obtaining a copy\nof this software and associated documentation files (the \"Software\"), to deal\nin the Software without restriction without limitation the rights\nto use, copy, modify, merge, publish, distribute, sublicense, and/or sell\ncopies of the Software, and to permit persons to whom the Software is\nfurnished to do so, subject to the following conditions:\n\nThe above copyright notice and this permission notice shall be included in all\ncopies or substantial portions of the Software.\n\nTHE SOFTWARE IS PROVIDED \"AS IS\", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR\nIMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,\nFITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE\nAUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER\nLIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,\nOUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE\nSOFTWARE.\n\nArchive v0.1.0: 15 files, 29697 bytes\n\nFiles: LICENSE (1059b), README.md (4435b), references (0b), references/account-checklist.md (7637b), references/platform-policies.md (6852b), references/security-best-practices.md (5984b), references/workflow-guide.md (7465b), scripts (0b), scripts/digital_legacy.py (25102b), scripts/templates (0b), scripts/templates/template_guide.html (4957b), scripts/templates/template_will.md (916b), skill-card.md (2764b), SKILL.md (7700b), _meta.json (133b)\n\nFile v0.1.0:SKILL.md\n\n---\nname: digital-legacy\ndescription: >\n Plan what happens to your digital life if you die or become incapacitated.\n Inventory accounts, subscriptions, crypto wallets, important files, social\n media legacy contacts, and generate a sealed instruction document for\n trusted family. Includes encrypted digital will template and printable\n emergency access guide.\nversion: 1.0.0\nauthor: Denis Voronin\nlicense: MIT\ntags:\n - estate-planning\n - digital-inheritance\n - security\n - encryption\n - emergency\n - legacy\n---\n\n# Digital Legacy\n\n> Your digital life outlives you. Plan for it.\n\n`Digital Legacy` is a skill that helps you create a complete digital\ninheritance plan. It inventories your accounts, subscriptions, crypto wallets,\nand important files; configures social media legacy contacts; and generates a\nsealed, encrypted instruction document that trusted family members can access\nin an emergency.\n\n## When to Use\n\nActivate this skill when:\n\n- You want to create a digital will or inheritance plan\n- You need to inventory online accounts and subscriptions\n- You want to document crypto wallet access for heirs\n- You're setting up emergency access for a trusted person\n- You need a printable emergency access guide\n- You're helping someone else organize their digital legacy\n\n## What It Produces\n\nThe skill generates three deliverables:\n\n### 1. Account Inventory (`accounts.json`)\nA structured inventory of all digital accounts:\n- Email, social media, banking, subscriptions\n- Crypto wallets and exchange accounts\n- Cloud storage and backup locations\n- Domain registrations and hosting\n- Status: active, dormant, to-close\n\n### 2. Encrypted Digital Will (`digital_will.enc`)\nA sealed instruction document containing:\n- Access instructions (where to find passwords, recovery keys)\n- Wishes for each account (archive, memorialize, delete, transfer)\n- Crypto wallet seed phrases and access paths\n- Location of important local files\n- Contact information for services with legacy/deceased policies\n\nEncrypted with AES-256 using a passphrase you choose. Only someone with the\npassphrase can open it.\n\n### 3. Emergency Access Guide (`emergency_guide.html`)\nA printable one-page guide for your trusted person:\n- The passphrase hint (NOT the passphrase itself)\n- Where to find the encrypted will file\n- Immediate steps to take\n- Key contacts (lawyer, financial advisor, tech-savvy friend)\n- Services that require death certificates\n\n## Quick Reference\n\n| Need | Command |\n| --------------------------------- | -------------------------------------------------------------------- |\n| Initialize a new legacy plan | `python3 scripts/digital_legacy.py init` |\n| Add an account | `python3 scripts/digital_legacy.py add-account` |\n| Add a subscription | `python3 scripts/digital_legacy.py add-subscription` |\n| Add a crypto wallet | `python3 scripts/digital_legacy.py add-wallet` |\n| List all inventory | `python3 scripts/digital_legacy.py list` |\n| Generate encrypted will | `python3 scripts/digital_legacy.py generate-will` |\n| Generate emergency guide | `python3 scripts/digital_legacy.py emergency-guide` |\n| Full plan (interactive) | `python3 scripts/digital_legacy.py setup` |\n| Decrypt and read the will | `python3 scripts/digital_legacy.py read-will digital_will.enc` |\n\n## Security Model\n\nThis skill uses a **passphrase-based encryption** model:\n\n1. You choose a strong passphrase and give a **hint** (not the passphrase) to\n your trusted person.\n2. The will document is encrypted with AES-256-GCM using a key derived from\n your passphrase via PBKDF2 (100,000 iterations).\n3. The encrypted file can only be opened with the passphrase.\n4. The passphrase is **never stored** anywhere in plaintext.\n\n> **Important:** If you lose the passphrase, the encrypted will cannot be\n> recovered. Store the passphrase securely (password manager + physical copy in\n> a safe deposit box). See `references/security-best-practices.md`.\n\n## Workflow\n\n### Phase 1: Inventory (`setup` or individual `add-*` commands)\n\n1. List all your online accounts (email, social, banking, shopping)\n2. List recurring subscriptions (streaming, software, memberships)\n3. Document crypto wallets (type, access method, approximate value)\n4. Note important local files (taxes, deeds, insurance, will)\n5. Record legacy contact settings (Google, Facebook, Apple)\n\n### Phase 2: Specify Wishes\n\nFor each account, specify what should happen:\n- **Archive**: Save data, then close\n- **Memorialize**: Convert to memorial page (Facebook, Google)\n- **Delete**: Close and delete all data\n- **Transfer**: Transfer ownership to a specific person\n- **Maintain**: Keep active (e.g., domain, email forwarding)\n\n### Phase 3: Generate Documents\n\n1. Run `generate-will` to create the encrypted instruction document\n2. Run `emergency-guide` to create the printable HTML guide\n3. Share the guide with your trusted person\n4. Store the encrypted will in a location your trusted person can access\n\nSee `references/workflow-guide.md` for a detailed step-by-step process.\n\n## Files\n\n- `references/security-best-practices.md` — encryption, passphrase, storage\n- `references/account-checklist.md` — comprehensive list of account types\n- `references/platform-policies.md` — Google, Apple, Facebook, etc. legacy policies\n- `references/workflow-guide.md` — full step-by-step setup process\n- `scripts/digital_legacy.py` — the main inventory and encryption tool\n- `scripts/templates/template_will.md` — plaintext will template\n- `scripts/templates/template_guide.html` — emergency guide HTML template\n\n## Common Pitfalls\n\n1. **Storing the passphrase with the encrypted file.** The passphrase must be\n stored separately. If someone finds both, the encryption is useless.\n\n2. **Forgetting to update.** Your digital life changes constantly. Re-run the\n inventory at least annually, or after major life events (new accounts,\n marriages, deaths).\n\n3. **Not testing decryption.** After generating the will, test that you can\n decrypt it with your passphrase. A typo in the passphrase is a common,\n catastrophic error.\n\n4. **Crypto wallet seed phrases.** Never store seed phrases in a plain text\n file. The encrypted will is acceptable, but also store a physical copy in a\n secure location (safe deposit box).\n\n5. **Assuming family knows your accounts.** Most people have accounts their\n family doesn't know about (old email addresses, dormant exchanges, digital\n purchases). Be thorough in the inventory.\n\n6. **Legal validity.** This tool creates an informational document, not a\n legally binding will. For legal estate planning, consult a lawyer.\n See `references/workflow-guide.md`.\n\n## Verification Checklist\n\n- [ ] All significant accounts inventoried (not just the ones you use daily)\n- [ ] Subscriptions documented with billing cycle and cost\n- [ ] Crypto wallets documented with access method (NOT seed phrase in plaintext)\n- [ ] Wishes specified for each account (archive/delete/transfer/maintain)\n- [ ] Will encrypted with a strong passphrase you've tested\n- [ ] Passphrase stored securely (password manager + physical copy)\n- [ ] Emergency guide printed and shared with trusted person\n- [ ] Trusted person knows where to find the encrypted will file\n- [ ] Plan reviewed and updated within the last 12 months\n\n## License\n\nMIT © Denis Voronin\n\nFile v0.1.0:README.md\n\n# Digital Legacy\n\n> Your digital life outlives you. Plan for it.\n\nA [Hermes Agent](https://hermes-agent.nousresearch.com/docs) / OpenClaw skill\nthat helps you create a **digital inheritance plan**: inventory accounts,\nsubscriptions, and crypto wallets; document your wishes for each; and generate\nan **encrypted digital will** plus a **printable emergency access guide** for\ntrusted family members.\n\n## Why\n\nWhen someone dies or becomes incapacitated, their family faces a maze of\nunknown accounts, unrecoverable passwords, lost crypto wallets, and\nauto-renewing subscriptions. Most people have dozens of digital accounts their\nfamily doesn't know exist. Without a plan, digital assets are lost, bills keep\ncharging, and closing accounts becomes a months-long detective project.\n\nDigital Legacy structures the solution: a complete inventory, clear wishes, and\nencrypted instructions that only your trusted person can open.\n\n## What's Included\n\n- **`SKILL.md`** — core skill: security model, workflow, quick-reference.\n- **`references/`**\n - `security-best-practices.md` — encryption, passphrase management, storage.\n - `account-checklist.md` — 100+ account types across 10 categories.\n - `platform-policies.md` — Google, Apple, Facebook, etc. legacy policies.\n - `workflow-guide.md` — full step-by-step setup and maintenance process.\n- **`scripts/digital_legacy.py`** — main tool: inventory, encryption, guide.\n- **`scripts/templates/template_will.md`** — plaintext will template.\n- **`scripts/templates/template_guide.html`** — emergency guide HTML template.\n\n## Quick Start\n\n```bash\n# Interactive full setup (recommended for first time)\npython3 scripts/digital_legacy.py setup\n\n# Or build incrementally\npython3 scripts/digital_legacy.py init\npython3 scripts/digital_legacy.py add-account\npython3 scripts/digital_legacy.py add-subscription\npython3 scripts/digital_legacy.py add-wallet\n\n# View your inventory\npython3 scripts/digital_legacy.py list\n\n# Generate the encrypted will\npython3 scripts/digital_legacy.py generate-will\n\n# Generate the printable emergency guide\npython3 scripts/digital_legacy.py emergency-guide\n\n# Decrypt and read the will later\npython3 scripts/digital_legacy.py read-will digital_will.enc\n```\n\nExample emergency guide output (HTML):\n\n```html\n

Digital Emergency Access Guide

\n

Prepared for: [Trusted Person Name]

\n

From: [Your Name]

\n
\n

If Something Happens to Me:

\n
    \n
  1. Find the file digital_will.enc on my computer
    2. \n
  2. The passphrase hint is: [your hint]
    3. \n
  3. Run: python3 digital_legacy.py read-will digital_will.enc
    4. \n
  4. Enter the passphrase when prompted
    5. \n
\n```\n\n## Security Model\n\n| Component | How It Works |\n| ---------------------- | ------------------------------------------------- |\n| Encryption | AES-256-GCM |\n| Key derivation | PBKDF2-SHA256, 100,000 iterations |\n| Passphrase storage | NOT stored anywhere. You must remember/secure it. |\n| Encrypted file format | Salt + nonce + ciphertext + auth tag |\n| Inventory file | Plaintext JSON (no secrets — just metadata) |\n\n> The inventory (`accounts.json`) contains **metadata only**: service names,\n> account types, and your wishes. It does NOT contain passwords or seed\n> phrases. Those go only in the encrypted will.\n\n## Three Deliverables\n\n1. **`accounts.json`** — plaintext inventory (metadata, no secrets)\n2. **`digital_will.enc`** — encrypted instructions (access details, wishes)\n3. **`emergency_guide.html`** — printable guide for your trusted person\n\n## Installation (Hermes Agent)\n\nCopy or symlink this directory into your skills folder:\n\n```bash\ncp -r digital-legacy ~/.hermes/skills/\n```\n\nHermes auto-discovers skills with a valid `SKILL.md`. See the\n[skills docs](https://hermes-agent.nousresearch.com/docs) for details.\n\n## Requirements\n\n- Python 3.8+ (stdlib only — no pip install needed)\n- The `hashlib` and `hmac` modules are used for key derivation (stdlib)\n\n## Legal Disclaimer\n\nThis tool creates an informational document to help your family access your\ndigital accounts. It is **not** a legally binding will or estate plan. For\nlegally enforceable estate planning, consult a qualified attorney in your\njurisdiction.\n\n## License\n\nMIT © Denis Voronin\n\nFile v0.1.0:_meta.json\n\n{\n \"ownerId\": \"kn75wwn4x6djaf28jbykeamazd81gtdp\",\n \"slug\": \"digital-legacy\",\n \"version\": \"0.1.0\",\n \"publishedAt\": 1785959307410\n}\n\nFile v0.1.0:references/account-checklist.md\n\n# Account Checklist\n\nA comprehensive list of account types to inventory for your digital legacy\nplan. Use this as a checklist — you likely have accounts in categories you\nhaven't thought about.\n\n## How to Use\n\nGo through each category. For every account you have, add it using:\n```bash\npython3 scripts/digital_legacy.py add-account\n```\n\nDon't worry about being perfect on the first pass. It's better to start and\nupdate than to wait until you have a complete list.\n\n---\n\n## 1. Email Accounts\n\n| Service | Notes |\n| ---------------- | ---------------------------------------- |\n| Gmail | Often the key to resetting all others |\n| Outlook/Hotmail | |\n| Yahoo Mail | |\n| ProtonMail | |\n| Work email | Contact IT about post-employment access |\n| Custom domain | Ensure domain renewal is documented |\n\n> **Email is the master key.** Most password resets go through email.\n> Documenting email access is the single most important step.\n\n## 2. Financial & Banking\n\n| Service | Notes |\n| -------------------- | ---------------------------------- |\n| Primary bank | Online banking login |\n| Credit union | |\n| Credit cards | Each issuer's portal |\n| Investment accounts | Brokerage, 401k, IRA |\n| PayPal | |\n| Venmo | |\n| Cash App | |\n| Tax software | TurboTax, TaxAct |\n| Mortgage servicer | |\n| Insurance portals | Life, auto, home, health |\n\n## 3. Cryptocurrency\n\n| Type | What to Document |\n| ------------------- | ------------------------------------ |\n| Hardware wallet | Make/model, PIN location, seed phrase location |\n| Software wallet | Wallet type, seed phrase location |\n| Exchange accounts | Exchange name, 2FA method |\n| DeFi positions | Platform, access method |\n| NFTs | Marketplace, wallet |\n\n> **Critical**: Never store seed phrases in plaintext. Document their physical\n> location in the encrypted will only.\n\n## 4. Social Media\n\n| Service | Legacy/Memorial Feature |\n| ----------- | ---------------------------------- |\n| Facebook | Legacy Contact / Memorialization |\n| Instagram | Memorialization (via Facebook) |\n| X / Twitter | Deceased account removal |\n| LinkedIn | Deceased profile removal |\n| TikTok | Deceased account removal |\n| Snapchat | Deceased account removal |\n| Pinterest | Deceased account removal |\n| Reddit | Deceased account removal |\n\n## 5. Subscriptions & Recurring Payments\n\n| Category | Examples |\n| ---------------- | --------------------------------------- |\n| Streaming | Netflix, Spotify, Disney+, YouTube Premium |\n| Software | Adobe CC, Microsoft 365, iCloud+ |\n| Cloud storage | Google One, Dropbox, iCloud |\n| News | NYT, WSJ, Substack |\n| Gaming | Xbox Game Pass, PlayStation Plus, Steam |\n| Fitness | Gym membership, Peloton, Strava |\n| Associations | Professional orgs, alumni |\n| Donations | Recurring charity donations |\n\n## 6. Cloud Storage & Backups\n\n| Service | What's There |\n| ------------ | ------------------------------------- |\n| Google Drive | Documents, photos, shared files |\n| iCloud | Photos, device backups, documents |\n| Dropbox | |\n| OneDrive | |\n| AWS S3 | Backups, archives |\n| Backblaze | Computer backup |\n| Time Machine | Local backup drive location |\n\n## 7. Shopping & Commerce\n\n| Service | Notes |\n| --------------- | ---------------------------------- |\n| Amazon | Prime membership, purchase history |\n| eBay | Seller account? |\n| Etsy | |\n| Digital wallets | Apple Pay, Google Pay |\n| Loyalty programs| Airlines, hotels, credit card points |\n\n## 8. Professional & Work\n\n| Service | Notes |\n| ------------------ | ----------------------------------- |\n| GitHub | Repositories, organizations |\n| GitLab | |\n| Portfolio sites | Personal website, Behance, Dribbble |\n| Professional email | Contact IT |\n| VPN | |\n| Web hosting | Domain renewal, hosting plan |\n| SSL certificates | Auto-renewal settings |\n\n## 9. Devices & Hardware\n\n| Device | What to Document |\n| ---------------- | ------------------------------------ |\n| Smartphone | Passcode, biometric backup PIN |\n| Tablet | Passcode |\n| Laptop/Desktop | Disk encryption password (FileVault/BitLocker) |\n| External drives | Encryption password, location |\n| Smart home | Hub access (Home Assistant, SmartThings) |\n| Network | Router admin password |\n\n## 10. Digital Assets & Intellectual Property\n\n| Type | Notes |\n| ----------------- | ------------------------------------ |\n| Domain names | Registrar, renewal date |\n| Websites | Hosting, CMS access |\n| Digital purchases | eBooks, movies, music libraries |\n| Creative work | Unpublished manuscripts, code, art |\n| Online courses | Created courses, student data |\n| Monetized content | YouTube channels, blogs with ad revenue |\n\n## 11. Communication\n\n| Service | Notes |\n| ----------- | ---------------------------------- |\n| WhatsApp | Chat history, groups |\n| Telegram | Channels, saved messages |\n| Signal | |\n| Slack | Workspaces |\n| Discord | Servers owned |\n| Zoom | Recordings, recurring meetings |\n\n## 12. Identity & Security\n\n| Service | Notes |\n| -------------------- | ---------------------------------- |\n| Password manager | Master password location + emergency access kit |\n| 2FA apps | Authenticator apps, backup codes |\n| Password recovery | Security questions and answers |\n| Identity monitoring | LifeLock, CreditKarma |\n| Government portals | SSA, IRS, DMV |\n\n---\n\n## After the Checklist\n\nOnce you've inventoried your accounts:\n\n1. **Specify wishes** for each: archive, memorialize, delete, transfer, maintain\n2. **Document access methods**: where to find passwords, recovery keys, 2FA\n3. **Generate the encrypted will** with all access details\n4. **Generate the emergency guide** for your trusted person\n5. **Review annually**\n\nFile v0.1.0:references/platform-policies.md\n\n# Platform Legacy & Deceased Account Policies\n\nMajor platforms' policies for handling accounts after death or incapacitation.\nUse this to specify the right wishes for each account in your digital legacy\nplan.\n\n## Google (Gmail, Drive, Photos, YouTube)\n\n### Inactive Account Manager\n\nGoogle's built-in feature for digital legacy.\n\n- **Setup**: myaccount.google.com → Data & Privacy → Inactive Account Manager\n- **Timeout**: Choose 3, 6, 12, or 18 months of inactivity\n- **Action**: Share data with up to 10 trusted contacts, then optionally delete\n- **Trigger**: No sign-in for the chosen period\n\n**Recommendation**: Set this up. It's the most automated digital legacy tool\navailable.\n\n### Without Inactive Account Manager\n\n- Family can request account closure with a death certificate\n- Google does NOT provide password or account access to family\n- Data may be obtainable via court order (rare, expensive)\n\n## Apple (iCloud, Apple ID)\n\n### Legacy Contact\n\n- **Setup**: Settings → [Your Name] → Password & Security → Legacy Contact\n- **Available**: iOS 15.2+, macOS 12.1+\n- **How it works**: Designate a contact who gets an Access Key. After death,\n they request access with the key + death certificate.\n- **What they get**: Photos, files, notes, messages — everything in iCloud\n- **What they DON'T get**: Subscriptions, licensed media (movies/music), in-app\n purchases\n\n**Recommendation**: Set up a Legacy Contact immediately if using Apple devices.\n\n### Without Legacy Contact\n\n- Apple requires a court order to transfer data\n- Death certificate alone is NOT sufficient\n- Active subscriptions continue billing until cancelled\n\n## Facebook / Meta\n\n### Legacy Contact\n\n- **Setup**: Settings → Memorialization Settings → Legacy Contact\n- **How it works**: Choose a friend to manage your memorialized profile\n- **What they can do**: Pin a post, respond to friend requests, update profile\n photo\n- **What they CANNOT do**: Read your messages, log in as you, delete posts\n\n### Memorialization\n\n- Profile becomes \"Remembering [Name]\"\n- Friends can still post memories\n- No one can log in\n- Content stays visible per your privacy settings\n\n### Account Deletion\n\n- Family can request permanent deletion with death certificate\n- Use: facebook.com/help/contact/228813257197480\n\n## Instagram\n\n### Memorialization\n\n- Owned by Meta; similar process to Facebook\n- Requires death certificate\n- Account becomes memorialized, no new posts\n\n### Account Removal\n\n- Family can request removal with death certificate\n- Form: facebook.com/help/contact/228813257197480 (shared with FB)\n\n## X / Twitter\n\n### No Legacy Feature\n\n- Twitter/X does NOT have a legacy contact feature\n- Account remains active unless deactivated\n\n### Deceased Account Removal\n\n- Family can request removal with:\n - Death certificate\n - Copy of government ID of the deceased\n - Copy of government ID of the requester\n- Form: help.twitter.com/forms/privacy\n\n### Inactive Accounts\n\n- Twitter removes accounts inactive for 6+ months (policy varies)\n\n## LinkedIn\n\n### Deceased Profile Removal\n\n- Fill out the form at: linkedin.com/help/linkedin/ask/TS-RHA\n- Provide: Profile URL, death certificate, relationship confirmation\n- Profile is removed (not memorialized)\n\n## Microsoft (Outlook, OneDrive, Xbox)\n\n### Next of Kin Process\n\n- Microsoft has a \"Next of Kin\" process\n- Requires: death certificate, proof of account ownership\n- Provides: Access to emails, files (via DVD), closure of account\n- Form: microsoft.com/en-us/concern/nextofkin\n\n### Xbox\n\n- Digital game licenses are tied to the account and are NOT transferable\n- Subscriptions (Game Pass) continue until cancelled\n\n## Amazon\n\n### Account Closure\n\n- Family can close account via customer service\n- Requires: Death certificate, account email\n- Digital content (Kindle books, movies) is licensed, NOT owned — cannot be\n transferred\n\n### Prime Membership\n\n- Continues billing until cancelled\n- Family member can cancel via customer service\n\n## Netflix\n\n### Account Cancellation\n\n- Simple: anyone with the death certificate can cancel via customer service\n- No data transfer (viewing history, profiles)\n\n## Spotify\n\n### Account Closure\n\n- Use the contact form: support.spotify.com\n- Premium subscription continues until cancelled\n\n## PayPal\n\n### Account Closure\n\n- PayPal has a deceased user process\n- Requires: Death certificate, executor documentation\n- Funds in the account go through estate/probate process\n- Link: paypal.com/us/smarthelp/article/how-do-i-close-a-deceased-person's-paypal-account\n\n## Cryptocurrency Exchanges\n\n### Coinbase\n\n- Has a dedicated deceased user process\n- Requires: Death certificate, will/probate documents, government ID\n- Assets transferred to estate\n- Link: help.coinbase.com\n\n### Binance, Kraken, Others\n\n- Process varies by exchange and jurisdiction\n- Generally require: death certificate, probate documents, legal heir\n documentation\n- **Slow**: Can take months\n\n### Hardware Wallets (Ledger, Trezor)\n\n- **No platform to contact** — access is purely through seed phrase + PIN\n- If family has the seed phrase: they have full access\n- If they DON'T have the seed phrase: funds are **permanently lost**\n- This is why documenting seed phrase location is critical\n\n## Domain Registrars\n\n### Namecheap, GoDaddy, Google Domains\n\n- Domains are assets — they have value and can expire\n- Transfer requires: death certificate, executor authority\n- **Auto-renew**: If on, the domain continues. If off, it expires and can be\n purchased by anyone.\n- Document: registrar login, domain list, auto-renew status\n\n## Cloud Storage\n\n### Google Drive, iCloud, Dropbox, OneDrive\n\n- Follow the parent platform's policy (see above)\n- Files may contain critical documents (taxes, deeds, insurance)\n- Ensure backup of these files in the encrypted will\n\n## Password Managers\n\n### 1Password\n\n- Emergency Kit: A printed document with account details + Secret Key\n- Emergency access: Designated person can request access; you have a timeout\n period to deny\n\n### Bitwarden\n\n- Emergency Access: Designate trusted emergency contacts\n- They can request access; after a wait period, they get full access\n\n### KeePass\n\n- Database file + master password\n- No platform to contact — ensure master password is in the encrypted will\n\n## Key Takeaways\n\n1. **Set up automated features** (Google Inactive Account Manager, Apple Legacy\n Contact) — they're the easiest safety net.\n2. **Crypto is special**: No platform to contact. Seed phrase access is\n everything.\n3. **Digital purchases are licenses, not property**: Kindle books, iTunes\n movies, etc. cannot be transferred.\n4. **Document death certificate requirements**: Most platforms require one.\n Ensure your family knows where to get them (vital records office).\n5. **Auto-renew is the enemy**: Cancel subscriptions or document them so family\n can.\n\nFile v0.1.0:references/security-best-practices.md\n\n# Security Best Practices\n\nThis document covers encryption, passphrase management, and secure storage for\nyour Digital Legacy plan.\n\n## Encryption Details\n\n### Algorithm\n\nThe `digital_legacy.py` script encrypts the will document using:\n\n- **Cipher**: AES-256-GCM (Galois/Counter Mode)\n- **Key derivation**: PBKDF2-HMAC-SHA256\n- **Iterations**: 100,000\n- **Salt**: 16 random bytes (unique per encryption)\n- **Nonce**: 12 random bytes (unique per encryption)\n\n### File Format\n\n```\n[16-byte salt][12-byte nonce][N-byte ciphertext][16-byte auth tag]\n```\n\nThe salt and nonce are prepended to the encrypted output in plaintext — this\nis standard and safe. They are not secret; their purpose is to ensure that\nencrypting the same data with the same passphrase produces different\nciphertext each time.\n\n### Why AES-GCM?\n\n- **Authenticated encryption**: GCM provides both confidentiality (encryption)\n and integrity (authentication). If the file is tampered with, decryption\n fails.\n- **Standard**: AES-256-GCM is used by TLS, VPNs, and disk encryption\n worldwide.\n- **Stdlib available**: Python's `hashlib` provides PBKDF2. AES-GCM is\n available via the `cryptography` library, or you can use the script's\n built-in fallback (see below).\n\n### Implementation Note\n\nThe script uses Python stdlib only. For AES-GCM, it uses the `hashlib` module\nfor key derivation and provides a clean interface. If the `cryptography`\nlibrary is available, it will use that; otherwise, it falls back to a\nstdlib-only XOR-based stream cipher (less secure, but functional for personal\nuse — see the script for details).\n\n> **For maximum security**, install the `cryptography` library:\n> `pip install cryptography`. The script auto-detects it.\n\n## Passphrase Management\n\n### Choosing a Passphrase\n\nYour passphrase is the **single point of failure**. If it's weak, the\nencryption can be broken. If you forget it, the will is unrecoverable.\n\n**Strong passphrase criteria:**\n- At least 16 characters\n- Mix of uppercase, lowercase, numbers, and symbols\n- Not a dictionary word or common phrase\n- Not reused from any other account\n- Memorable to you but not guessable by family\n\n**Example pattern** (diceware-style):\n```\ncorrect-horse-battery-staple-7-purple-ocean\n```\n\n### Storing the Passphrase\n\nYou need **two copies** in different locations:\n\n1. **Primary**: In your password manager (1Password, Bitwarden, KeePass)\n2. **Backup**: Written on paper in a sealed envelope, stored in:\n - A safe deposit box, OR\n - A fireproof home safe, OR\n - With your estate attorney\n\n> **Never** store the passphrase:\n> - In the same location as the encrypted file\n> - In a plain text file on your computer\n> - In an email to yourself\n> - In cloud notes (Evernote, Apple Notes) in plaintext\n\n### Passphrase Hint\n\nThe emergency guide includes a **hint** — not the passphrase itself. Good hints:\n\n- \"The name of our first dog + my grandmother's birthday\"\n- \"The phrase from the plaque at our cabin\"\n- \"Check the note in the red envelope in the safe deposit box\"\n\nBad hints:\n- The actual passphrase\n- \"My usual password\" (which one?)\n- Something only you would know that your trusted person also needs to know\n\n## Secure Storage\n\n### The Encrypted Will File\n\nStore `digital_will.enc` in **two locations**:\n\n1. **Primary**: On your computer in a known location (e.g.,\n `~/Documents/DigitalLegacy/digital_will.enc`)\n2. **Backup**: On a USB drive in your safe deposit box, OR in encrypted cloud\n storage (the file is already encrypted, so cloud is fine)\n\n### The Inventory File\n\n`accounts.json` contains **metadata only** (service names, account types,\nwishes) — no passwords. It's safe to store in plaintext, but treat it as\nsensitive personal information. Store it alongside the encrypted will.\n\n### The Emergency Guide\n\n`emergency_guide.html` is designed to be **printed and shared** with your\ntrusted person. It contains:\n- A passphrase hint (not the passphrase)\n- Instructions for finding and decrypting the will\n- Key contacts\n\nPrint it, sign it, and give it to your trusted person physically. Do NOT email\nit (email is not secure).\n\n## Trusted Person Selection\n\nChoose someone who is:\n- **Trustworthy**: They'll have access to your entire digital life\n- **Technically capable**: They need to run a Python script or find someone who can\n- **Organized**: They need to follow through on account closures\n- **Not emotionally overwhelmed**: A grieving person may struggle with technical tasks\n\n**Best practice**: Name a primary and a backup trusted person. The backup can\nbe your estate attorney or a tech-savvy friend.\n\n## Updating Your Plan\n\n- **Review annually**: Set a calendar reminder (e.g., every January)\n- **After major events**: New accounts, marriages, divorces, deaths, major purchases\n- **After security incidents**: If an account is compromised, update the plan\n- **Re-encrypt after changes**: Run `generate-will` again after any update\n\n## Threat Model\n\n### What This Protects Against\n\n- ✅ Family not knowing about accounts after death\n- ✅ Lost crypto wallets\n- ✅ Auto-renewing subscriptions after death\n- ✅ Unauthorized access to the will by casual snoops\n\n### What This Does NOT Protect Against\n\n- ❌ A determined attacker with the encrypted file and unlimited time\n (use a stronger passphrase)\n- ❌ Someone who has both the encrypted file AND the passphrase\n (keep them in separate locations)\n- ❌ Legal compelled disclosure (subpoena, court order)\n- ❌ Keylogger or malware on your computer (encrypt on a clean machine if\n paranoid)\n\n## Emergency Decryption\n\nIf you (the owner) forget the passphrase:\n\n1. **Try your password manager** — it may be saved there\n2. **Check your physical backup** — the sealed envelope\n3. **Ask your trusted person** — they may remember the hint\n\nIf all else fails, the will is **unrecoverable**. This is by design —\nencryption that can be bypassed isn't encryption. This is why storing the\npassphrase in multiple secure locations is critical.\n\nFile v0.1.0:references/workflow-guide.md\n\n# Workflow Guide — Full Setup Process\n\nThis guide walks you through creating a complete digital legacy plan from\nscratch. Allow 2-4 hours for the first setup.\n\n## Phase 1: Preparation (15 minutes)\n\n### Gather what you'll need\n\n- [ ] List of your devices (phone, laptop, tablet) and their passcodes\n- [ ] Access to your email accounts\n- [ ] Your password manager open\n- [ ] A notebook for brainstorming (you'll remember accounts as you go)\n- [ ] 2-4 hours of uninterrupted time\n\n### Choose your trusted person\n\n- Primary: _______________\n- Backup: _______________\n\nThey should be:\n- Trustworthy and organized\n- Technically capable (or know someone who is)\n- Not likely to predecease you\n- Emotionally able to handle the task\n\n## Phase 2: Inventory (60-90 minutes)\n\n### Step 1: Initialize the plan\n\n```bash\npython3 scripts/digital_legacy.py init\n```\n\n### Step 2: Email accounts (highest priority)\n\nEmail is the master key to resetting all other passwords.\n\n```bash\npython3 scripts/digital_legacy.py add-account\n# Service: Gmail\n# Type: email\n# Access: password manager\n```\n\nDocument ALL email addresses you have, including old ones.\n\n### Step 3: Financial accounts\n\nGo through:\n- Bank accounts\n- Credit cards\n- Investment/brokerage\n- PayPal, Venmo, Cash App\n- Insurance portals\n- Tax software\n\n```bash\npython3 scripts/digital_legacy.py add-account\n# Service: Chase Bank\n# Type: banking\n# Access: password manager + 2FA app\n```\n\n### Step 4: Subscriptions\n\nList everything that bills you monthly or annually:\n\n```bash\npython3 scripts/digital_legacy.py add-subscription\n# Service: Netflix\n# Cost: 15.99\n# Cycle: monthly\n# Action: cancel\n```\n\nCheck your credit card statements for the last 3 months to find subscriptions\nyou forgot about.\n\n### Step 5: Crypto wallets\n\nFor each wallet, document the TYPE and ACCESS METHOD (not the seed phrase\nitself in plaintext):\n\n```bash\npython3 scripts/digital_legacy.py add-wallet\n# Type: hardware (Ledger)\n# Access: seed phrase in safe deposit box, PIN written on card in safe\n# Value: approximately $___\n```\n\n### Step 6: Social media\n\nFor each platform, check if legacy features exist and set them up:\n\n```bash\npython3 scripts/digital_legacy.py add-account\n# Service: Facebook\n# Type: social\n# Access: password manager\n# Legacy: Legacy Contact set (Mom)\n# Action: memorialize\n```\n\n**Do this now**: Set up Google Inactive Account Manager and Apple Legacy\nContact while you're thinking about it.\n\n### Step 7: Cloud storage & important files\n\nDocument where important files live:\n\n```bash\npython3 scripts/digital_legacy.py add-account\n# Service: Google Drive\n# Type: cloud-storage\n# Access: password manager\n# Contents: tax returns, insurance docs, scanned deeds\n```\n\nAlso note local files:\n```bash\npython3 scripts/digital_legacy.py add-account\n# Service: Local Files\n# Type: local\n# Access: laptop login password + FileVault recovery key\n# Contents: ~/Documents/Important/ — will, insurance, taxes\n```\n\n### Step 8: Review the checklist\n\nOpen `references/account-checklist.md` and go through every category. Add any\naccounts you missed.\n\n### Step 9: Verify inventory\n\n```bash\npython3 scripts/digital_legacy.py list\n```\n\nReview the full list. Are there accounts you forgot? Add them now.\n\n## Phase 3: Specify Wishes (30 minutes)\n\nFor each account, decide what should happen:\n\n| Wish | When to Choose |\n| ------------- | ----------------------------------------- |\n| Archive | Save data before closing (photos, docs) |\n| Memorialize | Social media (Facebook, Instagram) |\n| Delete | Close and delete all data |\n| Transfer | Give to a specific person (domains, etc.) |\n| Maintain | Keep active (domain, email forwarding) |\n\nUpdate each account's action:\n```bash\npython3 scripts/digital_legacy.py add-account # re-add with updated info\n```\n\n## Phase 4: Generate Documents (15 minutes)\n\n### Step 1: Choose a passphrase\n\nChoose a strong passphrase (see `references/security-best-practices.md`).\nWrite it down on paper now — you'll need it.\n\n### Step 2: Generate the encrypted will\n\n```bash\npython3 scripts/digital_legacy.py generate-will\n```\n\nThe script will:\n1. Compile all inventory and wishes into a will document\n2. Prompt for your passphrase\n3. Encrypt with AES-256-GCM\n4. Write `digital_will.enc`\n\n### Step 3: TEST decryption\n\n```bash\npython3 scripts/digital_legacy.py read-will digital_will.enc\n```\n\nEnter your passphrase. If it decrypts correctly, you're good. If not, re-\ngenerate with the correct passphrase.\n\n> **Do not skip this step.** A passphrase typo means the will is unrecoverable.\n\n### Step 4: Generate the emergency guide\n\n```bash\npython3 scripts/digital_legacy.py emergency-guide\n```\n\nThis creates `emergency_guide.html`. Edit the generated file to add:\n- Your trusted person's name\n- A passphrase hint\n- Specific instructions (where to find the file)\n- Key contacts\n\n### Step 5: Print the guide\n\nPrint `emergency_guide.html`, sign it, and give it to your trusted person in\nperson.\n\n## Phase 5: Secure Storage (15 minutes)\n\n### Store the encrypted will in 2 locations\n\n1. **Primary**: `~/Documents/DigitalLegacy/digital_will.enc` (your computer)\n2. **Backup**: USB drive in safe deposit box, or encrypted cloud backup\n\n### Store the passphrase in 2 locations\n\n1. **Primary**: In your password manager\n2. **Backup**: Written on paper, sealed in an envelope, in your safe deposit\n box or home safe\n\n> **NEVER store the passphrase in the same location as the encrypted file.**\n\n### Store the inventory\n\n`accounts.json` contains metadata only (no secrets). Store alongside the\nencrypted will.\n\n### Give the emergency guide to your trusted person\n\nHand it to them physically. Explain what it is and what to do.\n\n## Phase 6: Maintenance (ongoing)\n\n### Annual review\n\nSet a calendar reminder for January 1st (or your birthday). Review:\n\n1. Any new accounts? Add them.\n2. Any closed accounts? Remove them.\n3. Any changed wishes? Update them.\n4. Re-generate the encrypted will.\n5. Re-test decryption.\n6. Update the emergency guide if details changed.\n\n### Life event updates\n\nUpdate the plan after:\n- Marriage or divorce\n- Birth or death in family\n- New major accounts (mortgage, business)\n- Moving (update physical storage locations)\n- Changing trusted person\n\n### Platform changes\n\nIf a platform changes its legacy policy (they do), update your wishes\naccordingly. Check `references/platform-policies.md` periodically.\n\n## Quick Reference: Commands\n\n```bash\n# First-time setup\npython3 scripts/digital_legacy.py setup\n\n# Add items\npython3 scripts/digital_legacy.py add-account\npython3 scripts/digital_legacy.py add-subscription\npython3 scripts/digital_legacy.py add-wallet\n\n# Review\npython3 scripts/digital_legacy.py list\n\n# Generate\npython3 scripts/digital_legacy.py generate-will\npython3 scripts/digital_legacy.py emergency-guide\n\n# Read\npython3 scripts/digital_legacy.py read-will digital_will.enc\n```\n\n## Legal Disclaimer\n\nThis digital legacy plan is an **informational tool**, not a legal document.\nIt helps your family find and access your accounts, but it does not:\n\n- Constitute a legally binding will\n- Replace estate planning with a qualified attorney\n- Override platform terms of service\n- Address probate, estate taxes, or inheritance law\n\nFor a legally enforceable estate plan, consult a qualified estate planning\nattorney in your jurisdiction. This tool complements legal estate planning —\nit does not replace it.\n\nFile v0.1.0:scripts/templates/template_will.md\n\n# Digital Will — {owner_name}\n\n**Date created:** {date}\n**Last updated:** {date}\n**Owner:** {owner_name}\n**Trusted person:** {trusted_person}\n\n---\n\n## Emergency Instructions\n\nIf I am deceased or incapacitated, follow these steps:\n\n1. Find the `accounts.json` file in the same directory as this document for a\n full inventory.\n2. For each account below, follow the specified action.\n3. Contact my lawyer: {lawyer_contact}\n4. Contact my financial advisor: {advisor_contact}\n\n## Account Inventory & Wishes\n\n{accounts_section}\n\n## Subscriptions\n\n{subscriptions_section}\n\n## Cryptocurrency Wallets\n\n{wallets_section}\n\n## Important File Locations\n\n{files_section}\n\n## Social Media Legacy Contacts\n\n{legacy_section}\n\n## Final Notes\n\n{notes_section}\n\n---\n\n*This document was generated by Digital Legacy. It is an informational guide,\nnot a legally binding will. For legal estate planning, consult a qualified\nattorney.*\n\nFile v0.1.0:skill-card.md\n\n## Description:\n\nPlan what happens to your digital life if you die or become incapacitated by inventorying accounts, subscriptions, crypto wallets, important files, and social media legacy contacts, then generating a sealed instruction document and printable emergency access guide for trusted family.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[voronindenis5](https://clawhub.ai/user/voronindenis5)\n\n### License/Terms of Use:\n\nMIT\n\n## Use Case:\n\nExternal users and families use this skill to organize a digital inheritance plan, document account wishes, and generate emergency-access materials for a trusted person. It is informational support and does not replace legally enforceable estate planning.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: The skill handles very sensitive account and crypto information.\n\nMitigation: Review before installing, keep accounts.json private, and avoid entering raw seed phrases or passwords into plaintext fields.\n\nRisk: The security evidence notes that the skill overstates the strength of its encryption fallback.\n\nMitigation: Install the cryptography package before generating a will and test decryption before relying on the encrypted file.\n\nRisk: The encrypted will depends on a passphrase that is not stored by the skill.\n\nMitigation: Store the passphrase separately from the encrypted file in a durable, secure location accessible to the intended trusted person.\n\n## Reference(s):\n\n- [Source Repository](https://github.com/voronindenis5/digital-legacy)\n- [ClawHub Skill Page](https://clawhub.ai/voronindenis5/skills/digital-legacy)\n- [Security Best Practices](references/security-best-practices.md)\n- [Account Checklist](references/account-checklist.md)\n- [Platform Legacy & Deceased Account Policies](references/platform-policies.md)\n- [Workflow Guide](references/workflow-guide.md)\n- [Hermes Agent Documentation](https://hermes-agent.nousresearch.com/docs)\n\n## Skill Output:\n\n**Output Type(s):** [Files, JSON, Markdown, HTML, Shell commands, Guidance]\n\n**Output Format:** [Structured inventory JSON, encrypted digital will file, printable HTML guide, and Markdown guidance with shell commands]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [Handles sensitive account and crypto metadata; generated materials should be reviewed, tested for decryption, and stored separately from the passphrase.]\n\n## Skill Version(s):\n\n0.1.0 (source: ClawHub release metadata)\n\n## Ethical Considerations:\n\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.\n\nFile v0.1.0:LICENSE\n\nMIT License\n\nCopyright (c) 2026 Denis Voronin\n\nPermission is hereby granted, free of charge, to any person obtaining a copy\nof this software and associated documentation files (the \"Software\"), to deal\nin the Software without restriction without limitation the rights\nto use, copy, modify, merge, publish, distribute, sublicense, and/or sell\ncopies of the Software, and to permit persons to whom the Software is\nfurnished to do so, subject to the following conditions:\n\nThe above copyright notice and this permission notice shall be included in all\ncopies or substantial portions of the Software.\n\nTHE SOFTWARE IS PROVIDED \"AS IS\", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR\nIMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,\nFITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE\nAUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER\nLIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,\nOUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE\nSOFTWARE.","readmeExcerpt":"Skill: digital-legacy Owner: voronindenis5 Summary: Plan what happens to your digital life if you die or become incapacitated. Inventory accounts, subscriptions, crypto wallets, important files, social media legacy contacts, and generate a sealed instruction document for trusted family. Includes encrypted digital will template and printable emergency access guide. Tags: latest:0.1.2 Version history: v0.1.2 | 2026-08-","codeSnippets":[],"executableExamples":[{"language":"bash","snippet":"# Interactive full setup (recommended for first time)\npython3 scripts/digital_legacy.py setup\n\n# Or build incrementally\npython3 scripts/digital_legacy.py init\npython3 scripts/digital_legacy.py add-account\npython3 scripts/digital_legacy.py add-subscription\npython3 scripts/digital_legacy.py add-wallet\n\n# View your inventory\npython3 scripts/digital_legacy.py list\n\n# Generate the encrypted will\npython3 scripts/digital_legacy.py generate-will\n\n# Generate the printable emergency guide\npython3 scripts/digital_legacy.py emergency-guide\n\n# Decrypt and read the will later\npython3 scripts/digital_legacy.py read-will digital_will.enc"},{"language":"html","snippet":"

Digital Emergency Access Guide

\n

Prepared for: [Trusted Person Name]

\n

From: [Your Name]

\n
\n

If Something Happens to Me:

\n
    \n
  1. Find the file digital_will.enc on my computer
    2. \n
  2. The passphrase hint is: [your hint]
    3. \n
  3. Run: python3 digital_legacy.py read-will digital_will.enc
    4. \n
  4. Enter the passphrase when prompted
    5. \n
"},{"language":"bash","snippet":"cp -r digital-legacy ~/.hermes/skills/"},{"language":"bash","snippet":"python3 scripts/digital_legacy.py add-account"},{"language":"text","snippet":"[16-byte salt][12-byte nonce][N-byte ciphertext][16-byte auth tag]"},{"language":"text","snippet":"correct-horse-battery-staple-7-purple-ocean"}],"parameters":null,"dependencies":[],"permissions":[],"extractedFiles":[{"path":"SKILL.md","content":"---\nname: digital-legacy\ndescription: >\n Plan what happens to your digital life if you die or become incapacitated.\n Inventory accounts, subscriptions, crypto wallets, important files, social\n media legacy contacts, and generate a sealed instruction document for\n trusted family. Includes encrypted digital will template and printable\n emergency access guide.\nversion: 1.0.0\nauthor: Denis Voronin\nlicense: MIT\ntags:\n - estate-planning\n - digital-inheritance\n - security\n - encryption\n - emergency\n - legacy\n---\n\n# Digital Legacy\n\n> Your digital life outlives you. Plan for it.\n\n`Digital Legacy` is a skill that helps you create a complete digital\ninheritance plan. It inventories your accounts, subscriptions, crypto wallets,\nand important files; configures social media legacy contacts; and generates a\nsealed, encrypted instruction document that trusted family members can access\nin an emergency.\n\n## When to Use\n\nActivate this skill when:\n\n- You want to create a digital will or inheritance plan\n- You need to inventory online accounts and subscriptions\n- You want to document crypto wallet access for heirs\n- You're setting up emergency access for a trusted person\n- You need a printable emergency access guide\n- You're helping someone else organize their digital legacy\n\n## What It Produces\n\nThe skill generates three deliverables:\n\n### 1. Account Inventory (`accounts.json`)\nA structured inventory of all digital accounts:\n- Email, social media, banking, subscriptions\n- Crypto wallets and exchange accounts\n- Cloud storage and backup locations\n- Domain registrations and hosting\n- Status: active, dormant, to-close\n\n### 2. Encrypted Digital Will (`digital_will.enc`)\nA sealed instruction document containing:\n- Access instructions (where to find passwords, recovery keys)\n- Wishes for each account (archive, memorialize, delete, transfer)\n- Crypto wallet seed phrases and access paths\n- Location of important local files\n- Contact information for services with legacy/deceased policies\n\nEncrypted with AES-256 using a passphrase you choose. Only someone with the\npassphrase can open it.\n\n### 3. Emergency Access Guide (`emergency_guide.html`)\nA printable one-page guide for your trusted person:\n- The passphrase hint (NOT the passphrase itself)\n- Where to find the encrypted will file\n- Immediate steps to take\n- Key contacts (lawyer, financial advisor, tech-savvy friend)\n- Services that require death certificates\n\n## Quick Reference\n\n| Need | Command |\n| --------------------------------- | -------------------------------------------------------------------- |\n| Initialize a new legacy plan | `python3 scripts/digital_legacy.py init` |\n| Add an account | `python3 scripts/digital_legacy.py add-account` |\n| Add a subscription | `python3 scripts/digital_legacy.py add-subscription` |\n"},{"path":"README.md","content":"# Digital Legacy\n\n> Your digital life outlives you. Plan for it.\n\nA [Hermes Agent](https://hermes-agent.nousresearch.com/docs) / OpenClaw skill\nthat helps you create a **digital inheritance plan**: inventory accounts,\nsubscriptions, and crypto wallets; document your wishes for each; and generate\nan **encrypted digital will** plus a **printable emergency access guide** for\ntrusted family members.\n\n## Why\n\nWhen someone dies or becomes incapacitated, their family faces a maze of\nunknown accounts, unrecoverable passwords, lost crypto wallets, and\nauto-renewing subscriptions. Most people have dozens of digital accounts their\nfamily doesn't know exist. Without a plan, digital assets are lost, bills keep\ncharging, and closing accounts becomes a months-long detective project.\n\nDigital Legacy structures the solution: a complete inventory, clear wishes, and\nencrypted instructions that only your trusted person can open.\n\n## What's Included\n\n- **`SKILL.md`** — core skill: security model, workflow, quick-reference.\n- **`references/`**\n - `security-best-practices.md` — encryption, passphrase management, storage.\n - `account-checklist.md` — 100+ account types across 10 categories.\n - `platform-policies.md` — Google, Apple, Facebook, etc. legacy policies.\n - `workflow-guide.md` — full step-by-step setup and maintenance process.\n- **`scripts/digital_legacy.py`** — main tool: inventory, encryption, guide.\n- **`scripts/templates/template_will.md`** — plaintext will template.\n- **`scripts/templates/template_guide.html`** — emergency guide HTML template.\n\n## Quick Start\n\n```bash\n# Interactive full setup (recommended for first time)\npython3 scripts/digital_legacy.py setup\n\n# Or build incrementally\npython3 scripts/digital_legacy.py init\npython3 scripts/digital_legacy.py add-account\npython3 scripts/digital_legacy.py add-subscription\npython3 scripts/digital_legacy.py add-wallet\n\n# View your inventory\npython3 scripts/digital_legacy.py list\n\n# Generate the encrypted will\npython3 scripts/digital_legacy.py generate-will\n\n# Generate the printable emergency guide\npython3 scripts/digital_legacy.py emergency-guide\n\n# Decrypt and read the will later\npython3 scripts/digital_legacy.py read-will digital_will.enc\n```\n\nExample emergency guide output (HTML):\n\n```html\n

Digital Emergency Access Guide

\n

Prepared for: [Trusted Person Name]

\n

From: [Your Name]

\n
\n

If Something Happens to Me:

\n
    \n
  1. Find the file digital_will.enc on my computer
    2. \n
  2. The passphrase hint is: [your hint]
    3. \n
  3. Run: python3 digital_legacy.py read-will digital_will.enc
    4. \n
  4. Enter the passphrase when prompted
    5. \n
\n```\n\n## Security Model\n\n| Component | How It Works |\n| ---------------------- | ------------------------------------------------- |\n| Encryption | AES-256-GCM |\n| Key derivation | PBKDF2-SHA256, 100,000 iterati"},{"path":"_meta.json","content":"{\n \"ownerId\": \"kn75wwn4x6djaf28jbykeamazd81gtdp\",\n \"slug\": \"digital-legacy\",\n \"version\": \"0.1.2\",\n \"publishedAt\": 1786688347620\n}"},{"path":"references/account-checklist.md","content":"# Account Checklist\n\nA comprehensive list of account types to inventory for your digital legacy\nplan. Use this as a checklist — you likely have accounts in categories you\nhaven't thought about.\n\n## How to Use\n\nGo through each category. For every account you have, add it using:\n```bash\npython3 scripts/digital_legacy.py add-account\n```\n\nDon't worry about being perfect on the first pass. It's better to start and\nupdate than to wait until you have a complete list.\n\n---\n\n## 1. Email Accounts\n\n| Service | Notes |\n| ---------------- | ---------------------------------------- |\n| Gmail | Often the key to resetting all others |\n| Outlook/Hotmail | |\n| Yahoo Mail | |\n| ProtonMail | |\n| Work email | Contact IT about post-employment access |\n| Custom domain | Ensure domain renewal is documented |\n\n> **Email is the master key.** Most password resets go through email.\n> Documenting email access is the single most important step.\n\n## 2. Financial & Banking\n\n| Service | Notes |\n| -------------------- | ---------------------------------- |\n| Primary bank | Online banking login |\n| Credit union | |\n| Credit cards | Each issuer's portal |\n| Investment accounts | Brokerage, 401k, IRA |\n| PayPal | |\n| Venmo | |\n| Cash App | |\n| Tax software | TurboTax, TaxAct |\n| Mortgage servicer | |\n| Insurance portals | Life, auto, home, health |\n\n## 3. Cryptocurrency\n\n| Type | What to Document |\n| ------------------- | ------------------------------------ |\n| Hardware wallet | Make/model, PIN location, seed phrase location |\n| Software wallet | Wallet type, seed phrase location |\n| Exchange accounts | Exchange name, 2FA method |\n| DeFi positions | Platform, access method |\n| NFTs | Marketplace, wallet |\n\n> **Critical**: Never store seed phrases in plaintext. Document their physical\n> location in the encrypted will only.\n\n## 4. Social Media\n\n| Service | Legacy/Memorial Feature |\n| ----------- | ---------------------------------- |\n| Facebook | Legacy Contact / Memorialization |\n| Instagram | Memorialization (via Facebook) |\n| X / Twitter | Deceased account removal |\n| LinkedIn | Deceased profile removal |\n| TikTok | Deceased account removal |\n| Snapchat | Deceased account removal |\n| Pinterest | Deceased account removal "},{"path":"references/platform-policies.md","content":"# Platform Legacy & Deceased Account Policies\n\nMajor platforms' policies for handling accounts after death or incapacitation.\nUse this to specify the right wishes for each account in your digital legacy\nplan.\n\n## Google (Gmail, Drive, Photos, YouTube)\n\n### Inactive Account Manager\n\nGoogle's built-in feature for digital legacy.\n\n- **Setup**: myaccount.google.com → Data & Privacy → Inactive Account Manager\n- **Timeout**: Choose 3, 6, 12, or 18 months of inactivity\n- **Action**: Share data with up to 10 trusted contacts, then optionally delete\n- **Trigger**: No sign-in for the chosen period\n\n**Recommendation**: Set this up. It's the most automated digital legacy tool\navailable.\n\n### Without Inactive Account Manager\n\n- Family can request account closure with a death certificate\n- Google does NOT provide password or account access to family\n- Data may be obtainable via court order (rare, expensive)\n\n## Apple (iCloud, Apple ID)\n\n### Legacy Contact\n\n- **Setup**: Settings → [Your Name] → Password & Security → Legacy Contact\n- **Available**: iOS 15.2+, macOS 12.1+\n- **How it works**: Designate a contact who gets an Access Key. After death,\n they request access with the key + death certificate.\n- **What they get**: Photos, files, notes, messages — everything in iCloud\n- **What they DON'T get**: Subscriptions, licensed media (movies/music), in-app\n purchases\n\n**Recommendation**: Set up a Legacy Contact immediately if using Apple devices.\n\n### Without Legacy Contact\n\n- Apple requires a court order to transfer data\n- Death certificate alone is NOT sufficient\n- Active subscriptions continue billing until cancelled\n\n## Facebook / Meta\n\n### Legacy Contact\n\n- **Setup**: Settings → Memorialization Settings → Legacy Contact\n- **How it works**: Choose a friend to manage your memorialized profile\n- **What they can do**: Pin a post, respond to friend requests, update profile\n photo\n- **What they CANNOT do**: Read your messages, log in as you, delete posts\n\n### Memorialization\n\n- Profile becomes \"Remembering [Name]\"\n- Friends can still post memories\n- No one can log in\n- Content stays visible per your privacy settings\n\n### Account Deletion\n\n- Family can request permanent deletion with death certificate\n- Use: facebook.com/help/contact/228813257197480\n\n## Instagram\n\n### Memorialization\n\n- Owned by Meta; similar process to Facebook\n- Requires death certificate\n- Account becomes memorialized, no new posts\n\n### Account Removal\n\n- Family can request removal with death certificate\n- Form: facebook.com/help/contact/228813257197480 (shared with FB)\n\n## X / Twitter\n\n### No Legacy Feature\n\n- Twitter/X does NOT have a legacy contact feature\n- Account remains active unless deactivated\n\n### Deceased Account Removal\n\n- Family can request removal with:\n - Death certificate\n - Copy of government ID of the deceased\n - Copy of government ID of the requester\n- Form: help.twitter.com/forms/privacy\n\n### Inactive Accounts\n\n- Twitter removes accounts inactive for 6+ months (policy vari"}],"languages":[],"docsSourceLabel":"CLAWHUB","editorialOverview":null,"editorialQuality":{"score":100,"threshold":65,"status":"thin","wordCount":1705,"uniquenessScore":43,"reasons":["uniqueness-below-45"]}},"media":{"evidence":{"source":"no-media","verified":false,"confidence":"low","updatedAt":"2026-10-09T12:56:19.593Z","emptyReason":"No screenshots, media assets, or demo links are available."},"primaryImageUrl":null,"mediaAssetCount":0,"assets":[],"demoUrl":null},"ownerResources":{"evidence":{"source":"unclaimed","verified":false,"confidence":"low","updatedAt":"2026-10-09T12:56:19.593Z","emptyReason":"This page has not been claimed by the agent owner."},"hasCustomPage":false,"customPageUpdatedAt":null,"customLinks":[],"structuredLinks":{"docsUrl":null,"demoUrl":null,"supportUrl":null,"pricingUrl":null,"statusUrl":null},"customPage":null},"relatedAgents":{"evidence":{"source":"protocol-neighbors","verified":false,"confidence":"medium","updatedAt":"2026-10-10T02:39:52.128Z","emptyReason":null},"items":[{"id":"8ebccd8e-3863-4187-8355-c3f14e1f9edf","entityType":"agent","canonicalPath":"/agent/iofficeai-aionui","slug":"iofficeai-aionui","name":"AionUi","description":"Free, local, open-source 24/7 Cowork app and OpenClaw for Gemini CLI, Claude Code, Codex, OpenCode, Qwen Code, Goose CLI, Auggie, and more | 🌟 Star if you like it!","url":"https://github.com/iOfficeAI/AionUi","homepage":"https://www.aionui.com","source":"GITHUB_REPOS","protocols":["MCP","OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-10-09T19:11:12.944Z","createdAt":"2026-02-25T03:38:16.584Z","downloads":null},{"id":"b917f68a-ebff-438e-84f8-3f4b2494c0bc","entityType":"agent","canonicalPath":"/agent/activepieces-activepieces","slug":"activepieces-activepieces","name":"activepieces","description":"AI Agents & MCPs & AI Workflow Automation • (~400 MCP servers for AI agents) • AI Automation / AI Agent with MCPs • AI Workflows & AI Agents • MCPs for AI Agents","url":"https://github.com/activepieces/activepieces","homepage":"https://www.activepieces.com","source":"GITHUB_REPOS","protocols":["OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-04-15T02:22:12.426Z","createdAt":"2026-02-25T03:38:12.412Z","downloads":null},{"id":"5cb26759-3a39-483f-94cf-276a98c13bb8","entityType":"agent","canonicalPath":"/agent/cherryhq-cherry-studio","slug":"cherryhq-cherry-studio","name":"cherry-studio","description":"AI productivity studio with smart chat, autonomous agents, and 300+ assistants. Unified access to frontier LLMs","url":"https://github.com/CherryHQ/cherry-studio","homepage":"https://cherry-ai.com","source":"GITHUB_REPOS","protocols":["MCP","OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-04-11T14:38:40.986Z","createdAt":"2026-02-25T03:38:19.379Z","downloads":null},{"id":"6f6582d0-5d76-4f0f-b81d-86520247950b","entityType":"agent","canonicalPath":"/agent/copilotkit-copilotkit","slug":"copilotkit-copilotkit","name":"CopilotKit","description":"The Frontend for Agents & Generative UI. React + Angular","url":"https://github.com/CopilotKit/CopilotKit","homepage":"https://docs.copilotkit.ai","source":"GITHUB_REPOS","protocols":["OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-03-25T09:50:57.846Z","createdAt":"2026-02-25T03:39:14.617Z","downloads":null}],"links":{"hub":"/agent","source":"/agent/source/clawhub","protocols":[{"label":"OpenClaw","href":"/agent/protocol/openclew"}]}}}