root-cause-tracing
Five-whys + cause-and-effect diagram + analysis report. Drives /shannon:why.
What this skill does
# root-cause-tracing Backs `/shannon:why`. Five-whys cascade plus Ishikawa categorization. ## Behavior contract 1. Read symptom description. 2. Apply five-whys: each "why" probes one level deeper. Stop when an actionable root cause is reached (not "it's complicated"). 3. Build cause-and-effect diagram categorizing across: - **Code** — logic error, race condition, type mismatch, edge case - **Data** — bad input, schema drift, missing record, stale cache - **Config** — wrong env var, misconfigured route, missing secret - **Environment** — OS/runtime version, network, hardware constraint - **Dependency** — library bug, version mismatch, broken upstream - **Human** — incorrect assumption, missed step, undocumented constraint 4. Identify primary category + minimal fix. 5. Write `reports/root-cause-<slug>.md`. ## Per the `instrument-before-theorize.md` rule If you can't determine root cause in 10 minutes of reading code, **add instrumentation**: - Print statements at boundary points - Trace logs at each candidate root cause site - Live reproduction with the actual data - THEN re-apply five-whys with empirical evidence ## When to use - `/shannon:why` invocation - Phase 2 of `/shannon:fix` (debug step) - Post-incident analysis ## When NOT to use - Obvious bugs (null pointer, typo) — fix and move on - Configuration errors with clear error messages — read and fix ## Iron rules - Empirical > theoretical. Instrument > reason. - Five-whys reaches actionable cause, not vague label. - Cited evidence per "why" answer (log path, file:line).
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.