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:
data-ai
license: Apache-2.0 NOT for unrelated tasks outside this domain.
development
Use when designing caching strategies (cache-aside, write-through, write-behind), implementing distributed locks, building rate limiters, leaderboards, real-time streams (XADD/consumer groups), pub/sub, or tuning eviction policies. Triggers: thundering-herd on cache miss, dogpile on key expiry, Redlock vs SET-NX-PX choice, sliding-window rate limiter, hot-key on a single cluster slot, big-key blowup, MULTI/EXEC across slots, KEYS in production. NOT for Redis Cluster operations/admin (different domain), embedded KV (SQLite, leveldb), in-process LRU caches, or Memcached.
tools
Drawing the `'use client'` boundary correctly in React Server Components apps (Next.js App Router, RSC frameworks) — leaf-pushing, slot composition, serialization rules, and environment poisoning prevention. Grounded in react.dev and Next.js 16 docs.
development
Use when designing rate limiting for an API, choosing between token bucket / sliding window / leaky bucket / fixed window, implementing it in Redis, deciding edge (Cloudflare/Upstash) vs origin enforcement, sizing per-user vs per-IP vs per-endpoint quotas, returning the right 429 response with Retry-After, or fixing the boundary-burst bug in fixed-window limiters. Triggers: 429 too many requests, INCR + EXPIRE, ZADD + ZREMRANGEBYSCORE + ZCARD, X-RateLimit-Remaining header, Cloudflare WAF rate limiting rules, Upstash @upstash/ratelimit, leaky bucket shaping vs policing, distributed rate limiter consistency. NOT for DDoS mitigation specifically (different scale), CAPTCHA / bot management, full WAF design, or per-user quota billing.