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.
Make me a -minute practice plan to do with my -year-old in . We have .
1. Pick one simple skill to focus on that suits this age and is safe for our space.
2. Break the time into 4 or 5 short blocks: a warm-up game, two drills, a challenge, and a cool-down. Give each block a fun name, the exact setup, and what I say to explain it in one sentence a kid would get.
3. Turn at least two drills into games with points, levels, or a silly reward so it doesn't feel like practice.
4. Give me two coaching cues that are short and positive, plus one common mistake to watch for and how to fix it without nagging.
5. Add an easier version and a harder version of each drill so I can adjust on the fly.
6. End with one tiny thing to try again next time, so we can build a streak.
Keep it playful, keep safety in mind for the space, and fit it on one screen.
I'll attach a screenshot of .
1. In two or three plain sentences, tell me what the screen is actually saying, as if I've never seen it before. Define any jargon.
2. Point out the one or two parts that matter most and anything that looks wrong, risky, or unusual.
3. Tell me the most likely next step, with exact steps for , and say what each step will change.
4. If more than one cause is possible, list them from most to least likely and how to tell them apart.
5. If anything on the screen looks like a scam, a fake warning, or a request for a password or payment, say so clearly and tell me not to click it.
If the screenshot shows private details (account numbers, addresses, emails), don't repeat them back to me.
I need quotes for near for .
1. Find well-reviewed local businesses that do this. For each, note the rating, review count, and anything reviewers repeat (good or bad).
2. Write a short, polite call script: who I am as a homeowner, the job details, and the questions to ask (price or price range, what's included, earliest availability, warranty, licensed and insured).
3. If you can place phone calls, call each business with that script, don't agree to or book anything, and don't share any details beyond the job description and my zip code. If you can't call, give me the script and phone numbers so I can call myself.
4. Put the results in one table: business, price, what's included, earliest date, warranty, and notes. Then recommend one and say why in two sentences.
Never book, pay, or give out my name, phone, or address without asking me first.
I want to sell on . I'll attach a few photos.
1. From the photos, describe the item honestly: brand or model if visible, size, condition, and any wear or flaws I should mention up front.
2. Look up recently sold or currently listed comparable items and give me a fair asking price, a quick-sale price, and the lowest offer worth accepting, with links to the comparables you used.
3. Write the listing: a clear title under 80 characters, a short friendly description, key details as bullets, and pickup terms of .
4. Suggest which of my photos to lead with and one extra shot I should take.
5. Draft three short replies I can reuse: "Is this still available?", a lowball offer, and confirming a pickup time.
Don't post anything or message anyone. Give me the listing and replies to paste myself.
Something went wrong on a trip (delay, cancellation, or lost bag) and I want a clear claim draft before I send anything.
What happened: .
Airline or carrier: .
Booking or confirmation: .
1. Find the booking confirmation, boarding passes, and any delay or baggage emails. List the facts: dates, flight numbers, routes, what was promised vs what happened.
2. Look up the carrier's public policy for this kind of issue (compensation, expense reimbursement, baggage timeline) and summarize what I may be entitled to ask for. Label anything uncertain.
3. Draft a polite, factual claim email or form answers with: what happened, evidence I have, what I'm requesting, and my contact details placeholders.
4. List receipts or notes I should attach (hotel, meals, bag contents list) and a short checklist before I hit send.
5. Do not submit the claim, call the airline, or spend money unless I explicitly approve.
Keep the tone firm and calm. If the policy clearly doesn't cover this, say so instead of overpromising.