Find why your productivity system keeps failing, then apply the smallest fix — capacity math, bottleneck routing, durable local notes.
Coding
seasonal-allergy-radar
Try itUse when pollen ruins your springs (or you're moving/traveling and want to know what you're walking into) — correlates your daily symptom scores with regional pollen calendars (tree/grass/weed by month for your climate), computes your personal trigger lag and severity curve, forecasts the next 2 weeks of your symptoms from the calendar, and builds a pre-medication plan (antihistamine start before season, not after symptoms).
What it does
Hay fever suffers through the same 6-week misery every year, then repeats it — because nothing connects three facts they already have: **when their symptoms spike**, **what pollinates when in their region**, and **that antihistamines work best started 1–2 weeks BEFORE the season**.
The skill document
Seasonal Allergy Radar
Overview
Hay fever suffers through the same 6-week misery every year, then repeats it — because nothing connects three facts they already have: when their symptoms spike, what pollinates when in their region, and that antihistamines work best started 1–2 weeks BEFORE the season.
This skill connects them:
- Symptom log — 10-second daily entries: overall score 0–5 + affected systems (eyes/nose/lungs/skin). No app account, no cloud — a JSON file.
- Regional pollen calendar — month-by-month tree/grass/weed risk for your climate zone (temperate-Northern, Mediterranean, continental, subtropical, coastal-low-pollen). Curaated from aerobiology network patterns (see references).
- Correlation engine — aligns your log against the calendar, tests lags 0–7 days, and reports which pollen class(s) your symptoms track with correlation coefficient + your personal onset/peak.
- 14-day personal forecast — calendar × your fitted severity curve → expected symptom score per day, with "start/step-up medication" flags.
- Pre-medication planner — antihistamine start dates (season minus 10–14 days), nasal steroid ramp (they need days-weeks to peak effect), ophthalmologist-grade eye-drop timing, and an allergist-visit brief from your data.
When to Use
- "Every April I'm wrecked — is it tree or grass?" → correlation + calendar
- Planning a move or a trip during your allergy season
- "When should I start my antihistamine this year?" → pre-med plan
- Deciding if OTC management is enough or symptoms warrant an allergist
- Multi-year: "is it getting worse?" → season-over-season severity trend
Don't use for: asthma management, food allergy, anaphylaxis history, or substituting an allergist's testing (skin prick/IgE) — this is a pattern instrument, not a diagnostic one. Red-flag symptoms (wheezing, chest tightness) → doctor, not a log.
Quick Start
# 1. Print a month of blank log entries (paper or notes-app friendly)
python3 scripts/allergy.py log init --from 2027-03-01 --days 31 --out my_log.json
# 2. Record a day (takes 10 seconds)
python3 scripts/allergy.py log add --log my_log.json --date 2027-03-14 \
--score 4 --eyes --nose
# 3. What's in the air this month where I live?
python3 scripts/allergy.py calendar --zone temperate-northern
# 4. Correlate my log against the calendar (which pollen is me?)
python3 scripts/allergy.py correlate --log my_log.json --zone temperate-northern
# 5. My personal 14-day forecast + med flags
python3 scripts/allergy.py forecast --log my_log.json --zone temperate-northern \
--from 2027-04-01
# 6. Pre-medication plan for my main season
python3 scripts/allergy.py plan --zone temperate-northern --target tree \
--year 2027 --antihistamine cetirizine --nasal-steroid fluticasone
Symptom Log Format
One JSON file, one entry per day:
[
{"date": "2027-03-14", "score": 4, "systems": ["eyes", "nose"], "note": "driving with windows open"}
]
score0 (nothing) to 5 (incapacitating)systemsany ofeyes nose lungs skin- Best data: log EVERY day through the season, even good days — correlation needs the zeros as much as the spikes.
Pollen Calendar Zones
| Zone | Tree season | Grass season | Weed season |
|---|---|---|---|
| temperate-northern | Feb–May (birch/oak peak Apr) | May–Jul (peak Jun) | Jul–Sep (ragweed Aug–Sep) |
| mediterranean | Jan–May (cypress! olive Apr–Jun) | Apr–Jun | Jun–Sep |
| continental | Apr–Jun (birch May) | Jun–Jul | Jul–Sep (mugwort) |
| subtropical | near-year-round trees | Mar–Oct ( Bermuda ) | Jul–Nov |
| coastal-low | low overall; some grass May–Aug |
(Calendars are 3-week windows around these peaks; script holds the month-level table.)
How Correlation Works
For each pollen class (tree/grass/weed):
- Build the calendar's daily risk curve for your zone (0–3 scale).
- For lag L in 0–7 days: Pearson r between your score(t) and pollen(t−L).
- Best |r| wins; report r, lag, your days-worst percentile, inferred onset and peak dates from your own entries.
- If no class clears |r| ≥ 0.35, verdict = "no clear pollen driver — consider dust-mold-indoor factors or an allergist."
The lag matters clinically: symptoms can trail pollen by 1–3 days (priming effect), and antihistamines taken after onset fight a losing battle — receptor saturation works best pre-exposure.
Common Pitfalls
- Logging only bad days. Correlation needs baseline zeros; a log of only flare days correlates with everything.
- Starting meds when symptoms start. Second-generation antihistamines
reach steady effect in 1–3 days but work best on unstained mast cells;
nasal steroids need 1–2 weeks to plateau. The
plancommand back-dates starts from the season onset accordingly. - Wind vs insect pollinated. Showy flowers are rarely your problem; birch/grass/ragweed are wind-pollinated and produced in millions of grains per day. The calendar is built from wind-pollinators.
- Rain resets. Pollen drops during rain, spikes after (fragrance + burst grasses). A single rainy week can look like "cure" — it's weather, not tolerance.
- Cross-reactivity confusions. Birch-apple, mugwort-celery oral allergy syndrome: your "sudden fruit allergy" each April may be the tree pollen priming your mouth. Correlate before eliminating foods.
Verification Checklist
- Log has ≥ 21 days with honest zeros included
- Zone matches actual climate (not vacation spots in the log period)
- Correlation |r| ≥ 0.35 before trusting any trigger verdict
- Med start dates back-dated before calendar onset
- Red-flag symptoms (wheezing/chest) routed to a doctor, not the log
One-Shot Recipes
"What am I allergic to?" (one season of data):
python3 scripts/allergy.py log init --from 2027-03-01 --days 90 --out s.json
# ...log daily...
python3 scripts/allergy.py correlate --log s.json --zone temperate-northern
This year's pre-med calendar (birch-sensitive):
plan --zone temperate-northern --target tree --year 2027 \
--antihistamine cetirizine --nasal-steroid fluticasone
Trip planning — "April in Lyon vs Lisbon":
calendar --zone mediterranean
forecast --log my_log.json --zone mediterranean --from 2027-04-05
Related skills
Generate and edit Draw.io, Mermaid, and Excalidraw diagrams from natural language using a structured JSON spec.
Stores durable facts in a categorized, plain-markdown vault on disk, alongside your agent's built-in memory.
Fetch raw ad creative, app, ranking, and revenue data from AdMapix as structured JSON.
Join a video meeting as an AI bot with voice, avatar, and screenshare across four operating modes.
Write, debug, and tune Playwright specs with locator strategy, trace diagnosis, and CI-aware timeouts.
More from voronindenis5
Browse all skillsPryamoy Russkiy (Straight Russian) — AI assistant that tells it like it is. Direct answers, no fluff, occasional profanity. Specializes in honest analysis, t...
Prepare salary negotiations with a structured toolkit: market-rate anchoring math, walk-away floor calculation, total-compensation evaluation (equity, bonuses, benefits), negotiation scripts for offers, raises, and counter-offers, and BATNA analysis. Use when the user has a job offer, is preparing a raise conversation, wants to know if their pay is competitive, or needs scripts and a strategy for negotiating compensation.
Use when your calendar is eating your week and you want to know exactly where the time goes, when planning recurring meetings for a team, before proposing a new recurring meeting, when someone says 'we should sync weekly' and you want data, or when auditing which meetings to kill — imports ICS calendar files, measures meeting hours per week/person/meeting-series (including double-bookings and fragmentation), computes focus-time destruction from meeting placement, scores the true cost of each series (hours × attendees × frequency), flags specific meetings to kill/shorten/make-async using explicit rules, and simulates the recovered hours before anyone has to argue about it.
Use when you realize your photos/code/documents exist in exactly one place (or your 'backup' is a external drive in the same room as the computer) — audits your actual data-loss risk against the 3-2-1 rule (3 copies, 2 media, 1 offsite) asset by asset, scores blast radius (ransomware encrypts synced copies too), prices honest recovery (professional recovery lab $300-3000 vs $0), generates the minimum-cost redundancy plan for YOUR asset list, and produces a restore-test drill because an untested backup is a hope, not a backup.
Audit password vault exports (Bitwarden, 1Password, KeePass, Chrome, Firefox) for reuse, weakness, staleness, breach exposure, and 2FA gaps without ever storing or transmitting a plaintext password. Use when the user asks to audit passwords, check password strength/reuse, review vault health, or verify whether credentials appeared in breaches.
Use before any difficult phone call you're anxious about or that has stakes — calling customer service to dispute a fee, negotiating a bill, cold-calling a client, delivering bad news to a vendor, calling a landlord about repairs, insurance disputes, or handling collections calls — builds a branching call script from your situation (goal, leverage, fallback), generates objection→response trees for the specific counter-arguments you'll hear, produces a one-page printable cheat sheet, and includes a practice-drills mode that plays the other side and scores your responses.