Turn a running symptom log into a clear read: pattern, likely triggers, and whether to see a doctor.
Scanned 9/13/2026
Install to Claude Code
npx -y skills add fru-dev3/fd-apps-prevail-cli --skill symptom-log-triage --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Symptom Log Triage?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/fru-dev3-symptom-log-triage)More formats (shields.io, HTML) on the badges page.
---
id: symptom-log-triage
runner: llm
trigger: on-demand
description: Turn a running symptom log into a clear read: pattern, likely triggers, and whether to see a doctor.
source: seed
---
# Symptom log triage
Run when a symptom has recurred enough to take seriously, not at the first twinge.
1. **The pattern.** From data/symptom-log.csv, lay the episodes in date order with severity and duration. Is it getting more frequent, more intense, or settling on its own?
2. **Triggers and correlates.** Cross-reference data/vitals.csv (sleep, resting HR) and any food, stress, or activity notes to surface what tends to precede an episode.
3. **Reassure vs escalate.** Apply a simple rule: clear red-flag features or a worsening trend means book a visit now; otherwise set a concrete watch-window with the threshold that would change the answer.
4. **Prepare the handoff.** If escalating, draft the timeline and triggers into the format the doctor-visit-prep skill expects, so nothing is lost in the retelling.
Output: the episode timeline, the likely triggers, and a clear see-a-doctor-or-watch decision with its threshold.
Note: this is an organizing aid for your own records, not medical advice; anything acute or alarming warrants prompt professional care.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Ultra-compressed communication mode. Cuts token usage ~75% by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman. Also auto-triggers when token efficiency is requested.
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...
Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.
Recovers prior coding-agent session context by running `catchup <agent> --since-compact`, which extracts a clean summary of a previous Codex, Claude Code, Antigravity, OpenCode, or Pi Agent session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", or asks to recover/summarize a previous session before continuing. Do NOT use for the current conversation, git history, or any non-agent log.
A comprehensive mathematical reasoning skill for AI assistants — handles arithmetic to research-level problems with rigorous step-by-step reasoning, systematic verification, and transparent uncertainty handling