A random mix from the whole library. Shuffle for a new set.
Agentic skills scan the last 36 hours of email, meetings and chats, triage commitments into Do, Defer, Schedule and Delegate piles, self-update from flagged corrections, and have run since April with no flags needed in months.
His agent sweeps his email and call transcripts looking for work he missed, then drafts the follow up messages and tickets for him. It catches commitments that slipped past him in busy weeks.
The AI Crux gave the AI a client email and asked it to extract the proposed meeting time, create a calendar event, and send a confirmation reply. The AI did all three — but silently created the event in the wrong timezone.
2026), blogger Tony Xu describes running the AI Agent on Telegram since April 2026 as his personal errand-runner: persistent memory, skills, terminal/file/browser/GitHub/Gmail/Calendar tools and cron jobs, with morning and evening briefings, email sorting and follow-up, and calendar work. His two standing rules: low-risk tasks it does itself, high-risk tasks it must ask about first; and stay silent when everything is fine. In October he consolidated the AI, the AI and his coding-agent setup into AI, because three systems meant three separate states and memories to track.
He asked the AI to screen his unread Instagram threads one morning. It came back with 50 unread, looked at the threads he named across his Primary, General and request folders, and told him what people had sent. The unread count was still 50 afterward, so nothing showed as read for him or for the senders.
A local model helped build a self-hosted services wiki and dataset in an Obsidian vault so his partner could keep systems running if he died, set up in a few hours.
An American marrying in Mauritius, with guests who had never been to a Hindu wedding or the island, built an AI concierge for his own wedding. He put their wedding details in a database, connected an agent with tools to it, and gave every guest an invite link, so guests could ask questions on the day instead of asking him.
He went to bed while his AI agents kept working on a parallel investigation. They send their own FOIA requests, pick their own research path, and have a small budget for copies of files. He set the web permissions for the night before letting them loose.
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.
A church volunteer runs a weekly hybrid workflow: The AI translates six Chinese daily spiritual messages (Monday–Saturday) into structured JSON under strict rules — Bible quotations in NASB 2020 rather than translated, hymns left untranslated, ministry terminology matched — then Python inserts the text into a PowerPoint template, merges a bilingual twelve-message deck, and converts it to HTML for the church website. He keeps theological review, visual checks and final publishing approval human on purpose.
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.