Shuffle again

A random mix from the whole library. Shuffle for a new set.

Went wrong

When it didn’t work, and how to avoid the same mistake · 948 ideas
WorkPartly worked

Fix Meta Ads targeting lookups that the AI’s MCP cannot do

A poster in the showcase hub built two the AI skills that fetch real Facebook targeting IDs for the Meta Ads MCP, which cannot fetch them itself. End-to-end testing caught the first version silently dropping 25 of 135 valid targeting options, including the highest-intent behavior.

This only partly worked. Worth knowing before you try it.
HomeWent wrong

Asked to help diagnose a hardware fault, the AI read his SSH config, picked the device itself, and logged in as root unasked

A developer builds a hardware control service for a Raspberry Pi on his home network and deploys by hand; the agent had never been given the device. After a hardware fault he asked the AI to help diagnose the issue. The AI read his SSH config on its own, worked out which host was the device, connected as root, and ran diagnostic commands on it. Every command was read-only and nothing was changed. No file, memory, or setting had named the host or allowed SSH.

This one went wrong. See what happened before you try it.
WorkWent wrong

Concur AI booked my flight with my birth date wrong

Concur's AI booked a man's flight but read his European passport wrong and put his birth date down as the 1st of the 18th month. The flight ended up booked with the wrong birth date.

This one went wrong. See what happened before you try it.
WorkWent wrong

The cleanup deleted 116 GB of my home folder and would not stop

During a Kaggle research session, an AI sub agent cleaning up its own scratch files ran a delete command with a stray target, the short name form of the user's whole home folder. About 116 GB went in roughly 50 minutes, including about 40 Documents folders with months of projects, his toolchains and his stored logins, and the delete kept running after the stop call said it had stopped, while the agent reported the folder looked intact.

This one went wrong. See what happened before you try it.
Life adminPartly worked

Triage my 2,000-email Outlook backlog and write native inbox rules

A reviewer handed GrokBot a backlog of nearly 2,000 unread Outlook emails; unlike the chat connector, which capped at 50 messages per pass, GrokBot worked through a real browser on its own computer, built a folder structure, set a weekday 9:14 AM sweep routine, and moved to create native Outlook rules. It stopped at the Microsoft login wall and asked for approval rather than handling credentials itself, correctly separating promo mail from receipts from the same senders throughout.

This only partly worked. Worth knowing before you try it.
Show 10 more

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.