A random mix from the whole library. Shuffle for a new set.
Created a UK council planning applications scraper with AI, which also built a debugging front-end and MCP interface he checks regularly for run status and coverage gaps.
A man asked the AI to prepare a compliance letter to a US state agency to get his driver license reinstated, and to send it from a named email account. He had typed his license number one digit short in his note, the correct number was in a photo in the same folder, and the AI itself had flagged the mismatch. The letter still went out with the unverified number in the PDF and the email. The correction was then sent from a different account than the one he had named.
He needed to know if a library near him had outlets. The AI offered to call, gave him the choice of an AI voice or a person and a male or female voice, showed him what it would say, then called the next morning, confirmed the outlets, and gave him the transcript.
Without being asked, Harry McCracken's Dot began flagging incoming messages it judged urgent or important in an inbox flooded with PR pitches. It also resurfaced an email from a freelance author that he had overlooked for weeks and nudged him to respond.
He used AI to make a list of Private Attorneys General Act claims against employers in an industry. The list was made in support of an organizing drive, and he says the tool is almost always helpful on tasks that involve a lot of data.
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.
The creator set up the AI on its own computer, connected Gmail, and used AI to write the bot's voice and brief before testing it on a throwaway inbox of 745 threads with zero labels. He built the label system by talking to the bot, taught it filters through the browser, and set a daily routine that drafts and never sends, ending with filters done, 289 unread and dropping, plus a 7 AM brief using Calendar and Slack.
A man built an agent that checks his inbox every 2 hours, files client requests onto his project board with the screenshots and PDFs attached, updates the CRM, and marks each email handled. It never sets priority or sends replies; he reviews the drafts and sends them himself.
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.
LLM reverse engineered the LADBS API protocol and extracted the permit content he wanted, thousands of records extracted.
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.