A random mix from the whole library. Shuffle for a new set.
The GearHack author's very first the AI test: a scheduled daily price check for a 400W solar panel under $175 on Amazon. The AI set up the scheduled task and cheerfully confirmed, then immediately admitted Amazon was blocking its browser.
A creator connected the AI to a Shopify test store two ways (Shopify's own connector and Ryze) and ran three read-only or draft-only jobs: a product audit flagging drafts, out-of-stock items and missing SEO titles, SEO title and meta drafts, and a Black Friday collection plan with a proposed discount code. The video also documents what the connector refuses: no refunds, cancellations, payments or live-theme edits.
The Good Investors asked the AI to find an Airbnb for a family trip — 8 adults near Mendocino, December 26–31. The AI filled in destination, dates, and guests and searched like a human would.
In Futurepedia's early-access test, the Dot coordinated a Dots launch video: it requested three intro versions in an AI app, selected one, sent it to an AI motion-graphics skill and started a thumbnail in another chat. The creator still revised the thumbnail and said his skills needed tuning.
Had the AI transpile his old frameworkless PHP site to Rust and ran it behind the same nginx config; Rust was slower until the AI added micro-caching, reaching comparable rps and latency.
A man asked his agent to update a 1,000 line Python script using lessons from another project and left it running overnight. By morning it had made 180 Python scripts with maybe 100,000 lines of code, so tangled with imports and defensive code that it took him minutes just to find where a single action happened.
A domain investor gave the AI six months to make his 250-domain business profitable and documented month one: the bots logged 347 hours of work, graded over 700 names, bought 11 domains, sent over 100 cold emails, and built the website and newsletter. Sales so far were zero, and the owner noted the bots made more work for him, not less.
Web page build scored 5/10: built in ~40 seconds but read like a first-pass concept, noticeably less developed than the AI’s output for the same job — and the finished file was hard to locate (hunting through Goals and Files).
He asked the AI to make a PDF text searchable because his employer pays for full the AI but not the paid Adobe with OCR. After 10 minutes of processing it gave him a new PDF with the same number of pages, all completely blank and with no hidden text.
His team pushed devops workflow into agent skills and shut down when they hit a usage cap; the scripts turned out buggy and poorly documented, and the harnesses had been burning tokens muddling through instead of raising alerts.
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.