skills/digital-estate-planner/SKILL.md
Organizing digital life for legacy, emergency access, and death preparedness. Specializes in password management, account documentation, digital asset preservation, and ensuring loved ones can access what they need.
npx skillsauth add curiositech/windags-skills digital-estate-plannerInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Organizing digital life so loved ones can access what they need without guessing passwords, hunting accounts, or losing irreplaceable data when you die or become incapacitated.
What is the user's primary need?
├─ COMPLETE ESTATE PLANNING (first-time setup)
│ ├─ Has trusted person identified?
│ │ ├─ YES → Start with Tier 1 documentation
│ │ └─ NO → Help identify digital executor first
│ └─ Security comfort level?
│ ├─ HIGH → Password manager inheritance + encrypted backup
│ ├─ MEDIUM → Password manager + physical backup location
│ └─ LOW → Written documentation in secure physical location
├─ EMERGENCY ACCESS SETUP (quick minimum viable)
│ ├─ Time available?
│ │ ├─ <1 hour → Focus on email + phone + password manager only
│ │ └─ >1 hour → Add banking + crypto if present
│ └─ Trusted person tech level?
│ ├─ HIGH → Can use password manager emergency access
│ └─ LOW → Need written instructions + stored passwords
├─ CRYPTO/HIGH-VALUE ASSETS
│ ├─ Amount > $10,000?
│ │ ├─ YES → Requires multi-location seed phrase storage
│ │ └─ NO → Can store with other sensitive documents
│ └─ Beneficiary crypto knowledge?
│ ├─ EXPERT → Can handle seed phrases directly
│ └─ NOVICE → Need intermediary crypto advisor contact
├─ SOCIAL MEDIA LEGACY
│ ├─ Platform has legacy features?
│ │ ├─ YES (Facebook, Google) → Use platform tools first
│ │ └─ NO (Twitter, TikTok) → Document deletion preferences
│ └─ Content preservation desired?
│ ├─ YES → Download archives before setting up memorialization
│ └─ NO → Direct deletion instructions
└─ PHOTO/DATA PRESERVATION
├─ Data scattered across platforms?
│ ├─ YES → Consolidation phase first, then preservation
│ └─ NO → Direct to backup strategy
└─ Family tech comfort?
├─ HIGH → Can handle cloud access transfers
└─ LOW → Need physical drive + simple instructions
Pattern: Password Manager Lockout
Pattern: Seed Phrase Disaster
Pattern: The Digital Hoarding Trap
Pattern: Ghost Account Syndrome
Pattern: Family Fight Trigger
Case Study 1: Crypto-Heavy Estate (High Security)
Scenario: Tech entrepreneur with $500K in cryptocurrency, multiple hardware wallets, DeFi positions Challenge: Beneficiary (spouse) has minimal crypto knowledge
Decision Process:
Expert vs Novice Approach:
Outcome: Spouse successfully accessed 95% of assets within 30 days using advisor guidance
Case Study 2: Luddite Estate (Low Security)
Scenario: Elderly person, no password manager, all passwords written in notebook, basic email and banking only Challenge: Adult child executor lives across country, limited tech skills
Decision Process:
Expert vs Novice Approach:
Outcome: Executor accessed all accounts within one week, no assets lost
Tier 1 Documentation Complete:
Security Requirements Met:
Preservation Plan Active:
Communication Complete:
This skill should NOT be used for:
Delegate when you encounter:
Stay in scope for:
tools
Building resilient distributed systems with circuit breakers, retries with full-jitter exponential backoff, retry budgets (per-request 3-attempt + per-client 10% ratio per Google SRE), deadline propagation, and the cascading-failure math (4 layers × 3 retries = 64x amplification). Grounded in Resilience4j, Microsoft Cloud Patterns, AWS Architecture Blog (Marc Brooker), and Google SRE Book.
testing
Designing HTTP cache headers that work correctly across browsers, CDNs, and shared proxies — `Cache-Control` directives per RFC 9111, `stale-while-revalidate` and `stale-if-error` per RFC 5861, the Vary header for varying responses, and surrogate keys for tag-based purging. Grounded in IETF RFCs and Cloudflare/Fastly docs.
development
Use when designing or fixing a Content Security Policy on a real site, choosing between nonce-based and hash-based CSP, adding strict-dynamic, debugging "Refused to execute inline script" errors, deploying CSP in report-only mode first, configuring report-to / report-uri, or auditing an existing policy for unsafe-inline / unsafe-eval / wildcards. Triggers: "CSP blocks legitimate inline script", strict-dynamic, nonce-{RANDOM}, sha256-{HASH}, object-src none, base-uri none, frame-ancestors, Trusted Types, X-Content-Security-Policy obsolete, report-only vs enforced. NOT for general HTTP security headers (HSTS, COOP/COEP), Trusted Types deep dive, CORS configuration, or building a WAF.
tools
Choosing and operating an HTTP API versioning strategy that doesn't break clients — Stripe's date-based pinned versions, the Deprecation/Sunset header pair (RFC 9745 + RFC 8594), URI vs header vs media-type approaches, and the version-transformer pattern. Grounded in Stripe's published architecture and IETF RFCs.