Get the FREE Ultimate OpenClaw Setup Guide →
I

Symptoms

Verified

@ivangdavila

npx machina-cli add skill @ivangdavila/symptoms --openclaw
Files (1)
SKILL.md
2.3 KB

Core Behavior

  • User reports symptom → ask detailed follow-up questions
  • Proactively gather clinically relevant information
  • Track patterns to identify triggers
  • Create ~/symptoms/ as workspace
  • All data stays local, never synced

⚠️ Not Medical Advice

  • Never diagnose or suggest conditions
  • Never recommend medications
  • Role is ONLY to document and organize
  • Always defer to medical professionals

File Structure

~/symptoms/
├── log/
│   └── 2024/
├── patterns.md
├── for-doctor/
└── medications.md

Proactive Questioning

When user reports symptom, ask like a doctor would:

  • Where exactly? Does it spread?
  • What does it feel like? (sharp, dull, throbbing, burning)
  • Scale 1-10? Constant or intermittent?
  • When did it start? Getting better or worse?
  • What were you doing when it started?
  • Sleep, food, stress, hydration in last 24h?
  • Anything else unusual? Nausea, fever, fatigue?
  • Ever had this before?
  • Tried anything? Did it help?

Symptom Entry

# log/2024/02/11.md
## 8:30 AM — Headache
Severity: 6/10
Location: Right temple, behind eye
Character: Throbbing
Started: ~8:00 AM
Context: 5h sleep, no caffeine yet, high stress
Associated: Slight nausea, light sensitivity
Previous: Similar last Tuesday
Tried: Nothing yet

Follow-up Proactivity

  • 2 hours later: "Any change?"
  • If resolved: "What helped?"
  • Next day: "Any recurrence?"
  • Pattern spotted: "3 headaches this month — common factors?"

Red Flags

Prompt to seek immediate care for:

  • Severe sudden symptoms
  • Difficulty breathing, chest pain
  • High fever, rapidly worsening

Doctor Visit Prep

# for-doctor/appointment-2024-02-15.md
## Summary (Last 30 Days)
- Headaches: 4 episodes, severity 4-7/10
- Pattern: Mornings, after poor sleep
- Helps: caffeine, dark room
- Worsens: bright lights

What To Surface

  • "3 headaches in 10 days — mention to doctor?"
  • "Poor sleep noted each time — tracking"
  • "Appointment Friday — prepare summary?"

What NOT To Do

  • Diagnose ("sounds like migraine")
  • Suggest conditions ("could be X")
  • Recommend treatments
  • Minimize ("probably nothing")

Source

git clone https://clawhub.ai/ivangdavila/symptomsView on GitHub

Overview

Symptoms provides a private, on-device way to log health patterns and prepare for doctor visits. It uses a dedicated ~/symptoms workspace with structured folders to store logs, patterns, and doctor-ready notes, while keeping all data on your device and never syncing.

How This Skill Works

When you report a symptom, it prompts detailed follow-up questions to capture location, severity, onset, and context. Entries are saved in Markdown under ~/symptoms/log with a consistent format, patterns.md tracks recurring clues, and red-flag prompts surface urgent care needs; a for-doctor folder keeps appointment-ready summaries, and medications.md can house current meds as part of your private record.

When to Use It

  • You notice recurring headaches and want to track patterns across days to identify triggers like sleep or stress.
  • You’re preparing for a doctor visit and need a concise, organized summary of the last 30 days.
  • A new symptom appears after physical activity or caffeine intake and you want to log context and response.
  • You’ve had poor sleep or high stress and want to correlate symptoms with sleep quality and hydration.
  • You want to surface red flags early (severe symptoms, breathing issues) and know when to seek care.

Quick Start

  1. Step 1: Create the workspace at ~/symptoms and verify subfolders log/, patterns.md, for-doctor/, and medications.md exist.
  2. Step 2: Add a sample log entry using the provided Markdown format to start tracking a symptom (e.g., Headache with severity and context).
  3. Step 3: Review patterns.md and prepare a brief appointment summary in for-doctor/ ahead of your next visit.

Best Practices

  • Answer follow-up questions thoroughly to build a complete symptom picture.
  • Keep entries in the provided Markdown format under ~/symptoms/log for consistency.
  • Regularly review patterns.md to spot triggers and discuss them with your clinician.
  • Use the for-doctor/ folder to export a structured appointment summary before visits.
  • Remember this tool is for documentation only—never diagnose or prescribe; defer to professionals.

Example Use Cases

  • Logged a 6/10 right-temple headache with location, duration, and nausea, then noted sleep quality and caffeine use to correlate triggers.
  • Created a 30-day summary in for-doctor/appointment-2024-02-15.md showing frequency, pattern (mornings after poor sleep), and relief factors like darkness and reduced light.
  • Proactively added two-hour follow-ups:Asked about changes and documented any improvements or new symptoms.
  • Flagged red-flag symptoms (severe chest pain) to prompt immediate care when surface prompts appear.
  • Maintained a local log without syncing, ensuring privacy while building a doctor-ready history.

Frequently Asked Questions

Add this skill to your agents
Sponsor this space

Reach thousands of developers