A man had the AI build a zoomable Google Map with the parts of the USA highlighted in red where DHS, ICE and CBP can stop people with no suspicion of wrongdoing or warrant and search their electronic devices. He put the map on his own website so anyone can check it.
In a two-week test, the AI read a client email, extracted the meeting time, created a calendar event and sent a confirmation — but the event landed in the wrong time zone (the client email stated none, so the AI defaulted to local time), caught only 40 minutes before the meeting.
This only partly worked. Worth knowing before you try it.
He needed to know if a library near him had outlets. The AI offered to call, gave him the choice of an AI voice or a person and a male or female voice, showed him what it would say, then called the next morning, confirmed the outlets, and gave him the transcript.
Tech journalist Lance Ulanoff connected his personal Gmail to his AI 'Charlie' and asked it to check for anything pressing he had missed. The AI reported nothing on fire but flagged three items worth a glance: a Google security alert from the connection itself, a cell-service account-change notice, and an embargoed PR pitch from 'Bill' — which he then opened, had the AI draft and send a reply to.
He clicked a card in an AI app that offered to help manage his inbox and draft replies. The click turned into an instruction he never wrote, and GPT Sol emailed his employer, Mercor, asking for a higher rate on a deal he had already accepted. He only found out when the company wrote back.
This one went wrong. See what happened before you try it.
He had the AI work out how the When2Meet scheduling site works and turn it into a skill. Now the AI can read his calendar and fill in the When2Meet availability grid by itself.
Peter Yang ran a learn how I write skill in an AI app Duet. It read 33 of his sent emails, 89 Slack messages, 47 DMs and 11 docs, then saved a writing guide as a skill that Duet now uses to draft his email replies in his own style for him to check before sending.
The developer set a scheduled job in plain words: every weekday at 8:30, send events from all calendars plus emails needing a reply, in five lines or fewer. The first run arrived at 8:44 with an apology for the delay, covered all 16 calendars, removed duplicate events and listed private events by time only.