Symptoms

Build a private symptom tracker for logging health patterns and preparing for doctor visits.

debugging-network-issues

Evidence-driven investigation for network, streaming, and protocol-layer bugs. Use when debugging connection resets (ECONNRESET, HTTP/2 RST_STREAM, INTERNAL_ERROR), SSE or long-polling stalls, fixed-time connection drops, CDN/proxy/CGNAT idle timeouts, or any incident where symptoms do not match the obvious cause. Applies falsification-first methodology — layered isolation experiments to pin down the responsible network layer, env-gated runtime instrumentation for non-invasive observation, and counter-review agent teams to challenge single-cause assumptions. Strongly trigger on "socket closed unexpectedly", "stream interrupted", "ECONNRESET", "HTTP/2 INTERNAL_ERROR", "fails after N seconds", "works sometimes but not always", "upstream silent for X seconds", or any scenario where the investigator might jump to conclusions before evidence. Generalizes to any multi-layer system investigation where assumption-first thinking is the failure mode.

ibs-that-symptoms

AutoSkill: Experience-Driven Lifelong Learning via Skill Self-Evolution

home-assistant-best-practices

Best practices for HA automations, helpers, scripts, device controls, and dashboards. TRIGGER THIS SKILL WHEN: - Creating/editing automations, scripts, scenes, or dashboards - Choosing between template sensors and built-in helpers - Writing or restructuring triggers, conditions, or automation modes - Setting up Zigbee button/remote automations (ZHA or Zigbee2MQTT) - Renaming entities or migrating device_id to entity_id - Configuring dashboard cards or picking helpers to feed them - Looking up card types or domain-specific documentation SYMPTOMS: - Agent uses Jinja2 templates where native conditions/triggers/helpers exist - Agent uses device_id instead of entity_id - Agent modifies entity IDs without checking consumers - Agent chooses wrong automation mode (e.g., single for motion lights) - Agent hard-codes values or picks raw sensor over derived helper - Agent edits `.storage/` files, writes raw YAML, or generates YAML snippets - Agent tells user to edit configuration.yaml for UI-confi

debugging

Systematic debugging framework ensuring root cause investigation before fixes. Includes four-phase debugging process, backward call stack tracing, multi-layer validation, and verification protocols. Use when encountering bugs, test failures, unexpected behavior, performance issues, or before claiming work complete. Prevents random fixes, masks over symptoms, and false completion claims.

home-assistant-best-practices

Best practices for Home Assistant automations, helpers, scripts, and device controls. TRIGGER THIS SKILL WHEN: - Creating or editing HA automations, scripts, or scenes - Choosing between template sensors and built-in helpers - Writing or restructuring triggers, conditions, or automation modes - Setting up Zigbee button/remote automations (ZHA or Zigbee2MQTT) - Renaming entities or migrating device_id references to entity_id SYMPTOMS THAT TRIGGER THIS SKILL: - Agent uses Jinja2 templates where native conditions, triggers, or helpers exist - Agent uses device_id instead of entity_id in triggers/actions - Agent modifies entity IDs or config objects without checking all consumers - Agent chooses wrong automation mode (e.g., single for motion lights)

troubleshoot-print-issues

Diagnose and fix common 3D printing failures through systematic symptom analysis. Covers adhesion, stringing, layer shifts, warping, and under/over-extrusion issues. Use when a print fails during the first layer or partway through, finished prints have quality defects (stringing, blobs, gaps), dimensional accuracy issues occur (warping, elephant foot), layer adhesion fails, or new material or hardware changes are causing inconsistent results.

troubleshoot-print-issues

Diagnose and fix common 3D printing failures through systematic symptom analysis. Covers adhesion, stringing, layer shifts, warping, and under/over-extrusion issues. Use when a print fails during the first layer or partway through, finished prints have quality defects (stringing, blobs, gaps), dimensional accuracy issues occur (warping, elephant foot), layer adhesion fails, or new material or hardware changes are causing inconsistent results.

troubleshoot-separation

Systematically diagnose and resolve chromatographic separation problems: document symptoms, identify root causes for peak shape and retention anomalies, evaluate matrix effects, and implement targeted fixes using a one-variable-at-a-time approach for GC and HPLC systems.

troubleshoot-separation

Systematically diagnose and resolve chromatographic separation problems: document symptoms, identify root causes for peak shape and retention anomalies, evaluate matrix effects, and implement targeted fixes using a one-variable-at-a-time approach for GC and HPLC systems.

troubleshoot-separation

Systematically diagnose and resolve chromatographic separation problems: document symptoms, identify root causes for peak shape and retention anomalies, evaluate matrix effects, and implement targeted fixes using a one-variable-at-a-time approach for GC and HPLC systems.