The solo maintainer of the karasu modeling language runs dependency updates through an AI skill that investigates each Dependabot PR before anyone merges: release notes, the diff between tags, publisher or ownership changes, install-time scripts, lockfile edges and known advisories, written up as merge, hold or reject recommendations in a design doc. In the week of Oct 10–17 three triage rounds fed 88 merged PRs (16 from Dependabot) and 12 architecture decision records, and the process caught a rebuilt lockfile silently moving a package off the reviewed version.
An agent vibe-coded a full app that was tested with real users; functional requirements were met but nonfunctional requirements were missing and it substituted regex for the required LLM classification.
This only partly worked. Worth knowing before you try it.
In the same week, Alec Ellin had the AI mine his own Instagram and LinkedIn connections and turn them into a leads list — prospecting built from the network he already had rather than a purchased list.
He is a consultant, and the free apps he and his team used to track time for the official timesheet all annoyed him. So he made his own time tracker, ConClock, with AI, and it is already at version 0.7.2.
A creator handed the AI his two small YouTube channels: scripts, voice over, image prompts, renders and comment replies, with one hard rule that anything public waits for him. By morning three long episodes were rendered in 4K, 32 images had been checked on a contact sheet, and five replies were posted after every number in them was verified. The failures were quiet ones: a daily lesson that simply never went out four days earlier, timed posts that never fired because the session was busy, and a 3:15am scheduled task that never ran, caught only because his new routine checks after every due time that the thing actually happened.
This only partly worked. Worth knowing before you try it.
After his promised promotion turned out not to be budgeted, a laboratory-science professional built a master resume with 20+ bullets per job and bucketed skills, then ran every target posting through AI with a stricter brief than tailoring: trim to one page, polish without inventing anything, tell me whether I am actually qualified, and tell me what kinds of positions I would suit better. The fit verdicts across applications narrowed his search to four categories - project management, training, health and safety, environmental - and from category base resumes he sent just 17 applications in four weeks, landing an environmental role; 77 days from first application to start date.
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.
Threw plain the AI at a git repo move with no skills or tools and finished in 20 minutes while multitasking, while a senior spent 6 to 8 weeks building the AI skills for the same job and moved only 5 repos.