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.
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.