A random mix from the whole library. Shuffle for a new set.
Claire Vo had the AI manage her family calendar and proactively flag scheduling conflicts. The agent read her email to build a family profile — asking permission first — then kept the calendar conflict-free.
He pointed the AI Fable at a newspaper archive and asked for a timeline of wildfire events in and around the Adirondacks. The result is an interactive timeline built from 12,000 pages of newspapers.
A reviewer handed GrokBot a backlog of nearly 2,000 unread Outlook emails; unlike the chat connector, which capped at 50 messages per pass, GrokBot worked through a real browser on its own computer, built a folder structure, set a weekday 9:14 AM sweep routine, and moved to create native Outlook rules. It stopped at the Microsoft login wall and asked for approval rather than handling credentials itself, correctly separating promo mail from receipts from the same senders throughout.
He had the AI work out how the When2Meet scheduling site works and turn it into a skill. Now the AI can read his calendar and fill in the When2Meet availability grid by itself.
Gaby Hersham built a nightly automation in which the AI reads the roughly 20 school emails her family gets each week and adds the important dates to the family calendar, ending the manual trawl through newsletters and PDFs.
Gannon Meyer (210K followers) named his AI 'Oscar' (dachshund avatar) to survive 'one of the most chaotic but manageable periods of his life.' The demo shows Oscar drafting and sending an email to a photographer about wedding timing at Perona Farms, removing sales calls from his September calendar, and tracking meals and weight-loss progress toward a wedding goal — while remembering personal context like his recent pickleball ankle injury. Oscar proposes actions but executes only after a
Trained on past writings and responses; reviewer edits drafts and tells the AI the reasoning so it learns. Drafts only - never sends autonomously.
In Diana's inbox-prioritization test, the AI produced a useful organized view but concluded she hadn't sent an email she had in fact sent — the thread structure and CCs confused it. If she'd trusted the first answer, she'd have sent a duplicate email.
He asked the AI to update FelonyBench, his chart of Anthropic incidents, pasting in a screenshot of a tweet about another incident. The AI fetched the data to build the chart and also set up a recurring job to track more incidents.
Around Elmira and Corning, New York, event listings were scattered across library systems, a brewery site, a school app, chamber newsletters and Facebook, so people found out about things the day after. He had the AI build one page that checks 101 sources across three New York counties and part of northern Pennsylvania: 1,855 listings over the next 90 days, 1,767 events after duplicates are merged, about 250 in any week, at 159 venues. A cron job reruns it every six hours on cheap shared hosting, about 8,300 lines of PHP, and cancellations mostly handle themselves because an event disappears when its source stops listing it.
Every idea is a real post from someone who tried it, summarized in our words, with a link to the original. App names are swapped for plain words.