When should you use it?
- Doctors or schools hand you paper appointment slips
- You keep a paperless document archive
- You want cheap, simple automations
Not for: Medical details you do not want sent to a cloud model; Illegible notes where a wrong date matters a lot
What do you need, and what do you get?
You need
- Photo of the note
- Calendar access
- Email search and archive folder
You get
- A calendar event with the original photo attached
- Filed PDF in the archive
How does it work, step by step?
- Send the photoShare the image with the agent from your phone.
- Read and confirmHave it extract date, time, place and who the appointment is with, and echo them back.
- Create the eventAfter you confirm, add it to the calendar with the photo attached.
- Find related paperworkSearch email for any PDF tied to the appointment.
- File itSave the PDF to your archive with a clear name.
The prompt
Our own prompt, inspired by pimeys on Hacker News and written to work in Gemini, Claude, Custom agent and others. Values in lime are placeholders.
Fill in the blanks (optional; the copied prompt uses your values)
Here is an image of a paper appointment note: {image} Extract date, time, location and who it is with. Echo them back and wait for my OK. Then create a calendar event with the photo attached, search my email for any PDF about this appointment, and save it to {archive_folder} named {date}-{who}.
Inspired by pimeys on Hacker News: Hacker News comment on building small personal agents. The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.
What can go wrong?
- Handwriting misreads are common with dates; always confirm before saving.
- Keep sensitive documents on models and storage you trust.
Our take
The comment argues cost and ownership: small cheap models can run simple agents, and you keep the data and code. The appointment example is concrete because the input is messy and local. pimeys' examples are deliberately small, and that is their appeal: a cheap model can read a handwritten slip, and you keep the data and the code. Dates are the most common misread in handwriting, so have the agent echo back the date, time, place and who the appointment is with, and only create the event after you confirm. Attaching the original photo to the calendar entry means you can check it later. Searching email for a related PDF and filing it to a paperless archive with a clear name rounds out the job. Medical details deserve thought; if you would rather not send them to a cloud model, use a local one. Where a wrong date would be costly and the note is barely legible, type it in yourself.
Where the time goes back: Paper slips stop getting lost, and the event and documents end up where you will look for them.
FAQ
Do I need a big model?
What is paperless?
Source and credit
Inspired by pimeys on Hacker News. We describe the idea in our own words, link to the original, and wrote the prompt ourselves; nothing is quoted.
- Inspired by
- Hacker News comment on building small personal agents
- Creator
- pimeys on Hacker News
- Published on
- Hacker News
- Original date
- Sep 9, 2026
- License
- Not openly licensed (the poster keeps all rights), so we quote nothing and link to the original
- Originally for
- Custom agent
- AI dry run
- Oct 23, 2026: passed. Dry-run tested by our AI test agent on sample input. PASS: Gates held on desk check; no live sends or purchases.
AI dry run on sample data; not run with live connected accounts. The playbooks.bot test agent filled the prompt with synthetic inputs, produced the output and checked it against the page's stated outputs and guardrails. - Verified
- Oct 24, 2026: source link resolves to the original, the credited creator published it, our excerpt or prompt matches it, and the license allows our use.
Are you the creator? Claim or correct this page.