observability-report
Shannon-specific log reader. Powers /shannon:trace, /shannon:doctor, retrospective session analysis. Reads hooks.jsonl, hook-errors.jsonl, session JSONLs.
What this skill does
# observability-report The single skill for reading Shannon-produced logs + Claude Code session JSONLs. ## Behavior contract ### Mode: trace (for `/shannon:trace`) 1. Read `~/.claude/projects/<project>/<session-id>.jsonl`. 2. Stream-parse; filter to Shannon-relevant events (hook fires, skill triggers, tool calls, agent spawns). 3. Render chronological timeline. ### Mode: doctor (for `/shannon:doctor`) 1. Read `.claude-plugin/plugin.json` + `marketplace.json`. 2. Read `hooks/hooks.json` + verify scripts present. 3. Read `~/.claude/settings.json`. 4. Read `~/.claude/logs/shannon/hooks.jsonl` (last 100 lines) → confirm hooks have actually fired recently. 5. Emit per-check PASS/FAIL. ### Mode: session-log-audit (for `/shannon:retro` and `/shannon:audit --scope session`) 1. Walk `~/.claude/projects/<project>/` for sessions in date range. 2. Stream-parse each; extract user prompts, assistant turns, tool calls, commits. 3. Emit aggregate metrics + sample citations. ## Log paths Shannon writes to - `~/.claude/logs/shannon/hooks.jsonl` — one line per hook fire (ts, script, matchedTool, decision, exitCode, ms, sessionId) - `~/.claude/logs/shannon/hook-errors.jsonl` — one line per crash / slow-fire - `~/.claude/logs/shannon/open-tasks.txt` — TaskCreate/TaskUpdate listener output (for stop-task-semantics) ## Iron rules - Never invent log entries. If a log file is missing, report missing — don't fabricate. - Stream-parse large files (some sessions are >100MB). - Cite session-id + line number when surfacing claims.
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.