Generate and edit Draw.io, Mermaid, and Excalidraw diagrams from natural language using a structured JSON spec.
Coding
gift-occasion-planner
Try itUse when birthdays, anniversaries, and holidays keep sneaking up on you every single year — maintains a registry of people and their gift occasions (birthday, anniversary, Mother's/Father's Day, etc.) with per-person gift profile (interests, sizes, favorites, taboo list, past gifts), generates a rolling 60-day lookahead of upcoming occasions, recommends what to give based on profile + past-gift history (never repeat, always evolve), budgets per person/occasion with running yearly totals, produces an actionable buying plan per occasion (what, budget, where, wrap, card), and exports ICS reminders at 21/7/1 days out so the era of gas-station flowers on the drive home ends.
What it does
Gift failure is a memory failure. Every year: the birthday that arrives the day after you remembered it, the anniversary dinner booked nowhere, Mother's Day creeping up between playoff games. The result is the gas-station-flower bailout — expensive, obviously last-minute, and quietly corrosive to r…
The skill document
Gift Occasion Planner
Overview
Gift failure is a memory failure. Every year: the birthday that arrives the day after you remembered it, the anniversary dinner booked nowhere, Mother's Day creeping up between playoff games. The result is the gas-station-flower bailout — expensive, obviously last-minute, and quietly corrosive to relationships.
This skill runs a gift intelligence system:
- Registry — people × occasions with dates. Per-person profile: interests, sizes, favorite colors/teams/authors, taboo list ("no clothes", "no sweets"), budget.
- 60-day radar — rolling lookahead; every occasion appears 60, 21, 7, 1 days ahead (ICS export puts these in your real calendar).
- Recommendation engine — suggests gifts from profile ∩ history: never repeats, escalates or rotates category by year (year 1 book → year 2 experience → year 3 something from the wish list), respects taboos and budget.
- History — every given gift logged; the engine and the annual "what did I give last year?" panic both read it.
- Budget view — per-person and yearly totals, so December's damage is visible in March.
When to Use
- Chronic last-minute gifters — the core audience; the 60-day radar IS the product.
- Large families / blended families — 15+ occasions/year is un-manageable by memory alone.
- Anniversaries matter to your partner — the highest-stakes recurring date there is.
- Budget control — see the whole year's gift spend upfront and cap it.
- After any gift lands well — log it; profiles compound (year 3 recommendations beat year 1's).
- Don't use for: holiday shopping lists for yourself (different problem), corporate gifting programs (different scale/tax rules).
How It Works
- Add people —
add-person "Mom" --birthday 1958-03-14 --interests "gardening,opera" --taboo "no gadgets". - Add occasions — birthdays auto-created; anniversaries, Mother's/Father's Day, graduations added explicitly. Recurring occasions compute next date automatically.
- Radar —
radarshows the next 60 days: who, what occasion, days left, budget, recommendation, and status (IDEA / BOUGHT / WRAPPED / GIVEN). - Recommendations —
recommendproposes 3-5 options from profile ∩ past-gift history with rationale; you confirm into the plan. - Plan & execute —
planprints the actionable card: gift, budget, where to buy, wrap idea, card note suggestion, deadline chain (buy-by, wrap-by, mail-by dates). - Log —
given --gift "..."records history and moves on.
Commands
# People
python3 scripts/gift_planner.py add-person "Mom" --birthday 1958-03-14 \
--interests "gardening,opera,birdwatching" --taboo "no gadgets,no sweets" --budget 75
python3 scripts/gift_planner.py add-person "Dad" --birthday 1955-11-02 \
--interests "woodworking,jazz vinyl" --budget 60
# Occasions (birthdays auto; others explicit)
python3 scripts/gift_planner.py add-occasion "Mom" --kind anniversary --month-day 04-22 --label "Wedding anniversary"
python3 scripts/gift_planner.py add-occasion "Dad" --kind fathers-day
# The radar: next 60 days
python3 scripts/gift_planner.py radar
# What to give?
python3 scripts/gift_planner.py recommend "Mom"
# Lock in a plan
python3 scripts/gift_planner.py plan mom-birthday-2026 --idea "Pruning set + garden kneeler"
# Status machine: IDEA → BOUGHT → WRAPPED → GIVEN
python3 scripts/gift_planner.py status mom-birthday-2026 --set bought
# Log what was given (feeds history so recommendations never repeat)
python3 scripts/gift_planner.py given mom-birthday-2026 --gift "Felco pruning set" --cost 68
# Budget overview
python3 scripts/gift_planner.py budget
# Calendar export: 60/21/7/1-day reminders per occasion
python3 scripts/gift_planner.py ics gifts.ics
Example Session
$ python3 scripts/gift_planner.py radar
GIFT RADAR — next 60 days (as of 2026-09-20)
DUE IN 21 DAYS ────────────────────────────────
Mom — BIRTHDAY (Oct 11)
Budget: $75 Status: IDEA (nothing planned yet!)
Interests: gardening, opera, birdwatching
Recent gifts: bird feeder (2025), opera DVDs (2024)
Recommendation: rotate category → tool/equipment this year:
· Felco #2 pruners + holster (garden tool upgrade) ~$65
· Garden kneeler-stool ~$45
· Botanical garden season pass ~$70
DUE IN 47 DAYS ────────────────────────────────
Dad — FATHER'S DAY... no, wait: ANNIVERSARY (Nov 2 is birthday)
...
$ python3 scripts/gift_planner.py plan mom-birthday-2026 --idea "Felco pruners + holster"
PLAN: Mom's birthday 2026-10-11 (21 days out)
Gift: Felco #2 pruners + holster Budget: $75 (est. $65)
Where: local garden store or online 2-day ship
Buy by: 2026-10-04 (buffer for shipping)
Wrap by: 2026-10-10
Card angle: "for the rose bed that beat the neighbors again"
Status: IDEA → run `status --set bought` when purchased
Recommendation Logic
- Never repeat — exact and near-dupe matches against history (token overlap ≥ 60%).
- Category rotation — interests cycle: if last year was gardening-gear, this year suggest opera or birdwatching; same-category twice in a row only if the profile is single-interest.
- Taboo filter — hard exclusion.
- Budget fit — suggestions land within ±20% of per-person budget.
- Wish-list escalation — items marked "mentioned wanting" in notes rank first.
The engine proposes; the human decides. Suggestions carry rationale strings so choices never look arbitrary in the plan card.
Workflow for an Agent
- Onboard: ask for 3-5 important people + dates;
add-personeach. Birthdays auto-create occasions. - Set budgets — even rough ones; the yearly budget view depends on them.
- Export ICS immediately — 60/21/7-day reminders in the user's real calendar make the system work even when they forget the system exists.
- At T-21:
radar→recommend→ present 3 options with rationale; user picks;planit. - At T-7: check status; if still IDEA, escalate the reminder and suggest fastest shippable options.
- After:
given— history keeps future recommendations fresh and non-repeating.
Common Pitfalls
- Populating occasions once and never again — one-time events (graduation) need annual review; recurring ones don't.
radarshows "no occasions in window" — that's the cue to check next year's one-offs. - Ignoring taboo lists — a suggestion the person explicitly banned is worse than a generic gift; the engine filters, but manual plans bypass it.
- Setting budgets too tight to be useful — ±20% flex is built in; a $30 budget producing zero viable suggestions means the budget, not the engine, is wrong.
- Logging gifts from memory years back — pre-history is fine to seed, but mark years clearly; the never-repeat logic treats memory-seeded entries as gospel.
- Reminder-only usage — reminders without profiles produce panic purchases anyway; the profile IS what converts lead time into good gifts.
- Mother's/Father's Day dates — they move (2nd Sunday in May / 3rd Sunday in June US, different elsewhere); the library computes them, don't hardcode.
Verification Checklist
- All important people + occasions registered (birthdays at minimum)
- Profiles carry interests + taboos + budget per person
- ICS exported with 60/21/7/1-day reminders and imported into real calendar
- Radar reviewed at least monthly; nothing within 21 days still in IDEA
- Every given gift logged (
given) so history compounds - Yearly budget total reviewed and accepted
Related skills
Find why your productivity system keeps failing, then apply the smallest fix — capacity math, bottleneck routing, durable local notes.
Stores durable facts in a categorized, plain-markdown vault on disk, alongside your agent's built-in memory.
Join a video meeting as an AI bot with voice, avatar, and screenshare across four operating modes.
Fetch raw ad creative, app, ranking, and revenue data from AdMapix as structured JSON.
Run Git operations — commits, branches, merges, rebases, conflict resolution, and recovery — with safety rules enforced.
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.