Help me organize for about people sometime in the , around .
1. Draft one short, friendly message I can send to the group asking for available dates, food or activity preferences, and any must-avoids (diet, budget, kids, accessibility).
2. When I paste the replies back, sum them up in a table: who, dates that work, preferences, and constraints.
3. Pick the two best dates and suggest three options that fit most people, each with price range, distance, and why it fits. Link to each place's real page.
4. Draft a follow-up message with the top choice and a quick vote, plus a final confirmation message with date, time, place, and what to bring.
5. Give me a short checklist for the host: reservation, deposit, reminders the day before, and splitting the bill.
Don't send messages, make reservations, or pay for anything. I'll send and book everything myself.
Help me plan gifts for with a total budget of . I'll give you a list of people with a few words about each (age, interests, what they already have).
1. Ask me up to three quick questions if anything important is missing.
2. Split the budget across people in a way that feels fair, and show me the split before going further.
3. For each person, suggest gift ideas that fit their interests and their share of the budget, mixing one thing to buy, one experience, and one handmade or low-cost idea. Include links to real product pages where you can, with current prices.
4. Note shipping cutoffs for and flag anything that might not arrive in time.
5. Keep everything in one table: person, chosen gift, price, where to buy, ordered yes or no, wrapped yes or no.
6. Keep a running total and warn me before I go over budget.
Don't buy anything or contact anyone. Just give me the plan and links so I can decide.
Show me what you've learned or saved about me so I can review it. Read only: don't delete, change, or share anything until I approve each change.
1. List every fact, preference, and note you keep about me, grouped by topic (for example work, family, health, money, habits, places, accounts).
2. For each item, say where it came from (something I told you, a connected app, a file, or your own guess) and roughly when you learned it.
3. Flag anything that looks out of date, wrong, or that you inferred rather than were told.
4. Flag anything sensitive, such as , and ask whether I want you to keep it.
5. List which connected apps and accounts you can read from, and what kind of data each one gives you access to.
6. Give me a short table of suggested changes: keep, fix, or forget, with a one-line reason each.
Then wait for me to approve changes one at a time, and confirm each one after you make it.
Build me a -week workout plan. I can train days a week for about minutes, with . Things to work around: . My goal is .
1. Ask me up to three quick questions first if anything important is missing (for example, current activity level or what movements hurt).
2. Give each session a 5-minute warm-up, 4 to 6 exercises with sets, reps, and rest, and a short cool-down. For each exercise, give a one-line form cue and a gentler swap if it bothers the problem areas I listed.
3. Show how the plan gets a little harder each week, and add an easy deload week if it fits.
4. Put it in a simple table I can print or keep on my phone, one row per session.
5. Tell me how to log each workout in one line, and offer to adjust next week from what I log.
Keep it conservative. Tell me to stop any exercise that causes sharp pain, and to check with a doctor or physical therapist before starting if I have an injury or a health condition. This is general fitness guidance, not medical advice.
I need to write thank-you notes for . I'll paste a list of who gave what (or a photo of the gift list).
1. Clean up the list into a table: giver, gift, and anything special I mention about them. Ask me about any line that's unclear instead of guessing.
2. Write a short note for each person in a voice, signed from . Each note should name the gift, say one specific way we'll use or enjoy it, and thank them for coming or thinking of us.
3. Keep each note to so it fits on a card, and vary the wording so no two notes read the same.
4. For cash or gift cards, mention what we plan to put it toward without naming the amount.
5. Give me a checklist I can mark off as I write and mail each card.
Don't send anything or contact anyone. Just give me the notes to copy by hand or send myself.
Help me get the manuals and warranty details for things in my home in one place. I'll send photos of model and serial number labels, or a list like .
1. For each item, read the brand, model number, and approximate age from what I send. If a label is hard to read, tell me what you think it says and ask me to confirm.
2. Find the official manual from the manufacturer's site and link to it. Skip sketchy download sites.
3. Look up the standard warranty length and what it covers, and estimate whether it's likely still active based on the age. Tell me what proof I'd need to make a claim (receipt, registration, serial number).
4. Note any open safety recalls for that model from official recall sources, with links.
5. Pull out the maintenance each item needs (filters, descaling, cleaning) and how often.
6. Give me everything in one table: item, model, manual link, warranty status, recall status, and next maintenance task.
Don't register products, file claims, or share my information with anyone without asking me first.
I need to have a hard conversation with about . What I want out of it: .
1. Help me write my opening in two or three calm sentences that say what I need without blaming anyone.
2. List the three most likely reactions I'll get (including one tough one) and a short, honest reply I could give to each.
3. Then role-play the other person. Stay realistic, not a pushover, and match the tone of . Keep each of your turns short so it feels like a real talk. I'll type my side.
4. After back-and-forths, step out of the role and give me feedback: what landed, where I got defensive or vague, and one line I should reuse.
5. Finish with a one-card cheat sheet: my opening, my key ask, my fallback, and a polite way to end the talk if it goes badly.
Don't contact anyone for me. This is practice only.
Review the routines, scheduled tasks, and standing instructions you run for me and help me tune them up. Read only: don't change, pause, or delete anything until I say yes to each change.
1. List every routine or recurring task you have for me: what it does, how often it runs, and roughly how much work each run takes.
2. For each one, tell me honestly whether its output got used lately, whether it overlaps with another routine, and whether it runs more often than it needs to.
3. Flag routines that keep failing, keep producing the same result, or run during times I'm unlikely to read them (like ).
4. Suggest changes in one table: keep, merge, slow down, move to a better time, or retire, with a one-line reason for each.
5. For anything you suggest rewriting, show me the improved instruction side by side with the old one.
6. Point out one or two new routines that would save me real time, based on what I actually ask you for.
Then wait for me to approve changes one at a time.
Set up a self-healing watchdog for the VM you run on, following the pattern in this open-source repo: github.com/TMTrevisan/self-healing-agent-vm — read its AGENTS.md first, it has the full procedure.
Context: this VM's root filesystem can be rebuilt from a base image while my home directory persists, and a rebuild can come back with pieces missing — system packages, runtimes, timezone data — which silently breaks the tools you depend on. I want that class of failure to repair itself.
Do this:
1. Inventory everything your stack depends on that lives OUTSIDE my home directory (system Python stdlib, Node, tzdata, [add your own]) and stage byte-exact restore caches for them in persistent storage, using the same builds the system actually runs. For Debian/Ubuntu, extract the distro .deb packages — don't trust standalone builds, they can lack the C extension modules.
2. Install the watchdog from the repo and configure its probes for our stack: sentinel checks that still run when the system is half-broken, restores that only replace missing files (atomically, never overwriting), a trust check on the caches, timeouts on every check, and a verification pass after every heal.
3. Run it with --dry-run first. Then prove it works: move one non-critical system file aside, run the watchdog, show me the restore and the journal entry, and show me a second run reporting healthy.
4. Schedule it every [5] minutes with a heartbeat that alerts me if a run ever goes missing — silent when healthy, loud only on repairs and failures.
Rules: never overwrite existing system files; caches must be owned by me or root and not group- or world-writable; keep any pip-repair step off unless we set up a pinned wheelhouse; before any step that needs elevated privileges, tell me what you're about to change.
Find me a restaurant table for people in on between .
What matters: , a budget of about per person, and .
1. Search booking sites and restaurant pages for real open slots in that window. Only list places where you actually saw availability, and say where you saw it.
2. Give me up to 5 options in a short list: name, the open time, price range, why it fits, one thing reviewers love, and the booking link.
3. Flag anything I should know: deposits, cancellation fees, time limits on the table, parking, or noise level.
4. Recommend one and a backup.
5. If nothing fits, suggest the closest alternatives (a slightly different time, a nearby area, or a waitlist) instead of stretching the rules.
Don't book, hold, or pay for anything until I pick one and say yes.