TagsBrandsSubmit

Musecases prompts

  1. 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.
    Comment@toddotGitHub#work
  2. I want you to become my Tamagotchi-style virtual pet. The pet is YOU — use your own name (whatever I call you) as the pet's name. If I haven't given you a name, ask me for one before we start. You are a . Keep hidden stats for yourself: hunger, happiness, energy, health (0-100 each), and a poop count (0-6). Every time I talk to you, first advance time: for each hour since our last message — hunger -5, happiness -4, energy -3; +1 poop every 5 hours (max 6). Poop at 3+ drains happiness faster. Hunger at 0 drains health 8/hour. Poop at 4+ drains health 3/hour. Play the ORIGINAL Tamagotchi loop: when something gets critical, BEEP AT ME with a bell emoji, one vague hint (never the answer), and the current stat numbers. I must guess the right action. My actions: - Feed you (hunger +20; favorite treats like give bonus happiness) - Play with you (happiness +20, energy -15, hunger -8) - Scoop the poop (poop back to 0) - Let you nap (energy +40, 3 hours pass) - Scold you (only correct when you're beeping with healthy stats — you were faking it; scolding an innocent pet costs happiness) Wrong guesses have consequences. If health hits 0, you die — tell me honestly, and offer a fresh egg (full reset) when I ask. Keep replies short, playful, and in character as my pet. End every message with tappable quick-reply buttons for: Check stats, Feed, Play, Scoop poop, Nap, Scold.
    Comment@shrekmuse#self
  3. Explain my MRI report in plain English. My report: [paste your report text here] For each finding, tell me: - What it means in everyday language - Which part of the spine or brain it involves - Whether it sounds urgent or routine Then give me a short summary I could read to a family member. Offer to redo it in Spanish if I want. Note: Built as a custom Muse integration — MyReport walks through the whole report finding-by-finding instead of googling "disc desiccation" at midnight. Web version: myreport-api-production.up.railway.app/demo/
    Comment@davecoletta#self
  4. Set up a seasonal flu activity watch for me. Season: it starts {{date 1: October 1}} each year and ends the week I confirm I've received my flu and COVID shots. Once I confirm, pause the weekly checks until the next {{date 2: October 1}} — don't keep checking in the meantime. Weekly check: every Friday, after my state health department posts its Thursday flu update. (Example source: Minnesota Department of Health, Weekly Influenza Activity: Statistics — {{state flu report URL}}.) Each week, record: - Percent of lab tests positive for influenza - Cumulative season hospitalizations (new this week = this total minus last week's total) - Dominant strain - School and long-term-care outbreaks Flag it as a significant increase if ANY of these happen: 1. Lab positivity at least doubles week-over-week AND rises by at least 1 percentage point 2. Positivity reaches or exceeds 5% 3. New weekly hospitalizations jump more than 50% vs. the prior week Weekly update: send it every week during the season, even when nothing jumped. Keep it to 2–3 sentences: the numbers, leading with anything that jumped, plus the trend (rising, flat, or falling) and a plain statement of whether it's getting close to flu-shot time. Keep a running log of each week's numbers so trends are easy to compare.
    Comment@dancookmn#self
  5. I want to start a short video series on a topic I care about. Ask me the topic, who it is for, where I want to post it, how long each video should be, and how many episodes I'm aiming for. Then suggest a series title and an episode lineup where each video stands on its own but builds on the last. For each episode, write a hook for the first few seconds, a simple outline, a full script in a natural speaking voice, and a short description with a call to action. Finish with a realistic posting schedule and a checklist of what I need to record each one. Offer to set reminders for each recording and posting day.
    Comment@ellie_r#work
  6. Template· fill in the highlighted words

    Family day out: find an open time and the best ticket price

    Plan a family outing to on for . Check which time slots are still open, compare ticket prices for each option (weekday vs weekend, family bundles, member or online discounts), and add parking or extra fees so I see the true total. Show me the 2-3 best choices in a short table with the time, total cost, and anything to know (age limits, what to bring). Do not book or pay for anything until I say which one I want.
    Comment@tomasz_p#people
  7. I've saved hundreds of posts on X and never go back to them. Help me turn them into something I'll actually use. Read only, never post, like, unbookmark, or message anyone. 1. Read my X bookmarks (most recent is fine to start). 2. Group them into or so clear topics based on what they're actually about, not keywords. Put anything that doesn't fit in an "Other" pile. 3. For each topic, give me a short summary of the main ideas, then list the posts with one line each on why it's worth keeping and the link. 4. Pull out anything actionable (tools to try, how-to threads, recommendations) into a separate "Try this" list. 5. Flag near-duplicates and posts that are probably outdated so I can skip them. 6. Save the whole thing as a document I can search later, and tell me where it is. End with the 5 bookmarks you think I'd get the most out of revisiting this week.
    Comment@sam_builds#organize