A random mix from the whole library. Shuffle for a new set.
The AI helps him put GA4 and Microsoft Clarity tags live, with reviews and confirmations built in so he can check the event triggers fire. Cross checking the two tools showed bots being lumped into direct traffic.
A scripting skill picks his best idea and writes what he will say. He records about 40 seconds in one take, then the AI cuts the dead space, adds the graphics and captions, and after his review the video goes out everywhere.
A small agency owner whose team does websites, content, Google ads and SEO for home service businesses runs the work through about 30 AI agents. The problem was memory: every session started cold and repeated mistakes. Since June they share one log that only grows, now about 11,400 lines including 413 decisions, where every note names the agent that wrote it and links to proof, and replaced facts stop showing in searches. A separate grader agent scores every piece of work, though he found 208 of 277 grades had been credited to the grader instead of the worker.
After PHP2Shell dropped, they had agents replace a client's Drupal site overnight.
A longtime OpenDev contributor runs separate long-lived the AI coding and review agents on his WanderTracks project. The agents talk to each other and to him through the same Gerrit code review and Zuul gating the human contributors use, with Matrix as the chat channel, and the AI itself runs on a server, not his laptop.
The AI and the AI built his Obsidian plugin, listed in the Obsidian Directory with 65 users, alongside shell scripts, Alfred workflows and Elisp functions for his own setup.
A solo founder runs his game key store with about a dozen AI sessions, one each for code, pricing, copy, bookkeeping and suppliers. They stay in sync through a shared record where facts are only ever added, each fact says whether a session confirmed it or just read it somewhere, and his decisions go into a numbered ledger the sessions look up instead of asking him again.
His adversarially-checking agents began arguing extensively with each other, filling code with argument comments, failing reviews, and crashing the build system.
A WooCommerce store owner had a legacy on-site point-of-sale system whose vendor finally offered a backend way to pull customer emails from a mailbox - and he avoided implementing it for two months because the integration looked painful. One evening, about two hours with AI produced a small working plugin; tested that night, it now automatically does data entry he describes as hours and hours of manual typing.
Adley Kinsman (verified, 1.5M followers) walked through three concrete the AI uses for Instagram growth: ask what's gaining traction in her niche and which audience pain points are unaddressed; pull creator data from her niche for content pillars and competitive angles; and point the AI at her own account to diagnose what's working/flopping and map a 30-60-90 day plan. She framed it as 'the ONLY AI you need to grow on Instagram.'
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.