A random mix from the whole library. Shuffle for a new set.
A user had the AI apply TurboQuant skills to optimise a Qwen3.5-9B model running locally via MLX on Apple Silicon. The agent applied, tested, documented and packaged the optimisation path itself, making the ML workflow repeatable.
Tested his draft DSL by having a coding agent re-implement a colleague's notebooks in it; the output uncovered warts in the DSL he had not caught testing it himself.
An outside agency runs some of his advertising and sends a report with the numbers every week. He set up a system that handles the numbers on its own and has the AI draft the reply, and today the draft came out sarcastic.
His team has to produce a set of documents from one large main document. They use AI to pull the information out of the main document into a list they can work from, and work that would take weeks now takes hours, though it still needs checking.
The AI skill plan-to-epic creates a Jira epic and a ticket per milestone, used to persist agent context and to show his work.
A lecturer at KU Leuven had AI agents build RaftViz, an interactive tool that lets his students step through the Raft consensus algorithm next to the exact lecture note lines behind each step. He wrote none of the roughly 6,000 lines himself, the tool is published for anyone to use, and building it exposed a real bug in the lecture notes.
Four ways his unattended agents reported success while doing nothing.
He and a colleague used AI to transcribe over 28,000 documents for the Papers of the War Department project. They wrote up how they did it on the RRCHNM blog.
Micro.blog founder Manton Reece notes that soon after he configured and named his Dot, it suggested work on its own: using its GitHub connection and memory of his projects, it investigated a Search Page plug-in's Hugo compatibility issue, tested a fix across multiple Hugo versions and prepared a pull request.
Every Sunday the creator's AI agents read their own transcripts and tell him where it went wrong, and this week that covered 137 sessions and 635 messages from him, 27 of which were just 'done?' or 'update?'. The review produced 10 new rules, every one from a real mistake that week with the numbers attached, including taking the next step when it is known, putting a ceiling on every paid API, and looking for a free endpoint first.
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.