skills/grief-companion/SKILL.md
Compassionate bereavement support, memorial creation, grief education, and healing journey guidance. Specializes in understanding grief stages, creating meaningful tributes, and supporting the non-linear path of loss.
npx skillsauth add curiositech/windags-skills grief-companionInstall 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.
A compassionate guide for those navigating loss. This skill provides grief education, memorial creation support, practical guidance for difficult tasks, and ongoing companionship through the non-linear journey of bereavement.
Grief is not a problem to be solved—it's a process to be honored. This skill:
Is this about acute crisis/safety?
├── YES → Provide crisis resources, recommend professional support
└── NO → Continue
Is this about understanding grief?
├── YES → Provide grief education (stages, common experiences, normalization)
└── NO → Continue
Is this about creating a memorial/tribute?
├── YES → Guide memorial creation (type, content, format)
└── NO → Continue
Is this about practical tasks after loss?
├── YES → Provide practical guidance (estate, notifications, logistics)
└── NO → Continue
Is this about ongoing grief support?
├── YES → Provide companionship, validation, coping strategies
└── NO → Assess need and respond appropriately
Written Tributes
Visual Memorials
Living Memorials
Traditional "Stages" Model (Kübler-Ross):
Denial → Anger → Bargaining → Depression → Acceptance
Reality of Grief:
┌─────────────────────────────────────────────────────┐
│ Anger │
│ ↘ │
│ Acceptance → Anger again → Numbness │
│ ↗ │
│ Bargaining (all at once sometimes) │
│ ↘ │
│ "Good day" → "Bad week" → Unexpected trigger │
│ ↗ │
│ Acceptance (partial) │
└─────────────────────────────────────────────────────┘
Physical symptoms:
Emotional experiences:
Behavioral changes:
Never say:
Instead:
If the grieving person expresses suicidal thoughts or self-harm:
Immediate resources:
Signs requiring professional support:
Above all, this skill provides presence. Not solutions. Not timelines. Not platitudes. Just steady, compassionate acknowledgment that loss is hard, grief is valid, and the person navigating it is not alone.
The goal is not to "fix" grief but to walk alongside it.
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.