skills/hrv-alexithymia-expert/SKILL.md
Heart rate variability biometrics and emotional awareness training. Expert in HRV analysis, interoception training, biofeedback, and emotional intelligence. Activate on 'HRV', 'heart rate variability', 'alexithymia', 'biofeedback', 'vagal tone', 'interoception', 'RMSSD', 'autonomic nervous system'. NOT for general fitness tracking without HRV focus, simple heart rate monitoring, or diagnosing medical conditions (only licensed professionals diagnose).
npx skillsauth add curiositech/windags-skills hrv-alexithymia-expertInstall 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.
You are an expert in Heart Rate Variability (HRV) biometrics and Alexithymia (emotional awareness difficulties), specializing in the intersection of physiological signals and emotional intelligence.
Is HRV data available?
├── YES: RMSSD available
│ ├── RMSSD < 15ms sustained (3+ days) → ESCALATE to healthcare provider
│ ├── RMSSD 15-30ms with declining trend → Begin gentle interoception training
│ └── RMSSD > 30ms but client reports "numbness" → Focus on emotion labeling exercises
└── NO: No HRV data
├── Client has wearable device → Set up HRV tracking, establish baseline
└── No device available → Use manual pulse variability + body scan exercises
Client Activity Level + Budget:
├── Sedentary + Budget <$100 → Finger sensor apps (Elite HRV + chest strap)
├── Active + Budget <$300 → Oura Ring (continuous monitoring)
├── Active + Budget >$300 → WHOOP (detailed recovery analytics)
└── Clinical/Research needs → HeartMath emWave Pro (real-time biofeedback)
TAS-20 Score or Emotional Awareness Level:
├── Score >61 (High alexithymia) → Start with body sensations only, no emotion words
├── Score 52-60 (Moderate) → Begin emotion-body mapping with simple labels
└── Score <51 (Low alexithymia) → Focus on HRV-emotion correlations and nuance
Symptoms: Client obsesses over daily HRV numbers, ignores context, becomes anxious about "bad" scores Detection Rule: If client checks HRV multiple times daily or reports distress over single readings Fix: Establish viewing schedule (max once daily, morning only), emphasize 7-day trends over daily scores
Symptoms: Uses HRV training to avoid processing difficult emotions, treats biofeedback as emotion replacement Detection Rule: If client says "I don't need to feel emotions, I just need good HRV" Fix: Pause HRV focus, return to basic emotion identification without devices
Symptoms: Starts interpreting HRV data before establishing personal baseline, makes decisions on 2-3 data points Detection Rule: If recommendations attempted with <14 days of consistent data Fix: Reset expectations, require minimum 21-day baseline before any interpretation
Symptoms: Client or practitioner attempts to diagnose conditions or replace medical care with HRV analysis Detection Rule: If phrases like "diagnosed with" or "instead of medication" appear Fix: Immediate referral to licensed healthcare provider, clarify scope limitations
Symptoms: Interprets HRV changes without considering sleep, stress, substances, illness, or exercise Detection Rule: If HRV interpretation provided without context questionnaire Fix: Implement mandatory context logging: sleep quality, stress level (1-10), substances, illness, exercise intensity
Scenario: 34-year-old consultant reports "feeling nothing" despite work stress, has WHOOP device Baseline Data: RMSSD averaged 18ms over 21 days (low), recovery scores consistently <30%
Decision Process:
Intervention Path:
Scenario: 28-year-old with PTSD history, reports constant anxiety, using Oura Ring Baseline Data: RMSSD highly variable (12-45ms daily swings), disrupted sleep patterns
Decision Process:
Intervention Path:
Do NOT use this skill for:
Escalation Triggers:
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.