agent sidequestsIdeas worth trying
An ongoing helper

Look for patterns in your symptoms and wearable data

Pair a short daily symptom diary with the wearable data you choose to share. Get readable charts, possible patterns and a record you can discuss with a clinician, without mistaking a correlation for a treatment result.

You get: A dated symptom diary, exploratory charts and a clinician-ready question sheetOriginal prompt · Not run-tested

Your copy-and-paste prompt

Read as Markdown

Replace the [brackets] with your details, then paste this into your assistant.

Help me explore my own symptom diary alongside selected wearable data. My question is [question], my daily measure is [symptom or score and scale], and the period is [dates and timezone]. Use only [files or explicitly authorized sources]. Start by helping me make a simple daily log that I can maintain without tracking everything about my life. Do not request unrelated records or account credentials.

Keep the raw entries unchanged and make a separate analysis table. Align dates, timezones and overnight measurements; document the choices. Flag missing days, device changes, estimated values and inconsistent scoring. Do not fill missing symptoms with zero or treat a wearable estimate as a clinical measurement.

Agree on at most [three] comparisons before analyzing them, such as the relationship between the supplied sleep duration and the next day's score. Plot the timeline first, then report the number of usable paired days, simple summaries and any exploratory associations. Account for the ordering of measurements and note possible alternative explanations such as illness, travel, workload or an already-recorded routine change. Do not hunt through many variables and present the strongest accidental correlation as a discovery. If the record is too short or noisy, say that no reliable pattern is apparent.

Return the updated diary, clearly labeled charts, what seems worth observing further, and three questions I could discuss with my clinician. Treat associations as hypotheses, not proof of what helps or causes symptoms. Do not diagnose, recommend starting or changing medication or supplements, or propose a risky experiment. Any health experiment or treatment change should be discussed with a qualified clinician. This workflow does not monitor emergencies.

For later check-ins, compare new entries with the saved record and explain what changed in the interpretation. Keep the analysis private and ask before exporting or sharing it. If I request reminders, confirm the schedule and tool support before saying they are active; otherwise give me a manual check-in template.
What the result could look like

A pattern to ask about, not a conclusion

An illustrative review shows a symptom score and sleep duration on aligned timelines, marks several missing nights, and notes that a possible association also coincides with travel. The useful result is a clearer record and a clinician question, not a claim that more sleep treats the symptom.

Illustrative example. This is not an observed result or a verified recommendation.

From the community

Suggested by the site founder and developed into an original prompt. This workflow has not been run-tested.

Make it more you

Use the same careful log to track a routine already agreed with a clinician. Keep the daily question and scale consistent, and record changes without treating the diary alone as proof of effectiveness.

Keep the ideas coming

All sidequests
An ongoing helper

Wake up to a 6am brief that remembers yesterday

Combine your calendar, email and meeting notes into a short morning PDF. Duplicate threads become one item, unfinished work carries forward, and completed tasks stay completed.

You get: A dated morning PDF and a persistent action register with completion historyGet the promptCommunity-inspired idea