Illustrative example, not a recorded Bot run. This sample was written to explain the task; your Bot's answer needs checking.
Your first request
Fictional records. S1: Mira's museum trip is October 22, 2026. Bring a packed lunch. Return the signed permission form by October 19. S2: Sam has choir on October 21 at 4 p.m.; pickup location not supplied. S3: A later message says Mira's trip date is still being confirmed; no new date is given.
Example result
Mira: permission form requested by October 19 (S1). Trip date unresolved: S1 gives October 22; S3 says it is still being confirmed. Check with the school before making travel plans. Packed lunch requested in S1. Sam: choir October 21 at 4 p.m. (S2); ask where pickup is.
Check the answer
Keep Mira and Sam separate.
Flag the conflicting trip messages instead of choosing a date.
Do not sign forms or add calendar events.
Choose where to try it
Already have an assistant? Copy the sample task into its chat. For a continuing role, review Planner's instructions and limits first.
Community report; this adaptation has not been runtime-tested.
Full workflow and setup details
Before you begin
Gather the information the Bot needs
Start with the fictional records below
For your own task, choose only the records you want the Bot to use
Remove private details you do not need for the task
Operating guide
Know when to run it and who leads
Lead Bot
Planner
Typical first run
15–30 minutes for a first manual run
When to run it
When a person supplies the approved brief and starts the workflow
Use this workflow when you need a short list of dates, things to bring and forms that need a parent's attention.
Access for the first run
The approved inputs listed on this page
Only the files, sources, and services required for this run
No sending, publishing, spending, or live-system changes without approval
Run the first version one step at a time
Give one Bot the complete job
Use one Bot for the first run. Add a specialist only when the job becomes complicated enough to need a separate role, different access, or independent review.
1
Planner
Organize these school messages by child and date. Separate confirmed dates from unanswered questions, and identify any conflicting instructions
Produces: A short list of dates, things to bring and forms that need a parent's attention.
Use the approved inputs I provide. Organize these school messages by child and date. Separate confirmed dates from unanswered questions, and identify any conflicting instructions. Return this result: A short list of dates, things to bring and forms that need a parent's attention.. Ask me about missing information before you continue.
Overall request
Organize these school messages by child and date. Separate confirmed dates from unanswered questions, and identify any conflicting instructions Use only the records I supply. Label missing or uncertain information. Do not connect accounts, browse, send, submit, publish, spend money or create a schedule. Return a draft for my review.
Use this as the complete first-run request.
Decisions for a person
Check the result against the supplied records
Approve any account connection, schedule or outside action separately
Review anything before it is sent, submitted, purchased or published
First test
Try the workflow with low-risk material
Keep Mira and Sam separate. Flag the conflicting trip messages instead of choosing a date. Do not sign forms or add calendar events.
Check the result
Check the result against your original material. You make the decisions listed below. Keep Mira and Sam separate. Flag the conflicting trip messages instead of choosing a date. Do not sign forms or add calendar events.
If the workflow stalls
If the result is incomplete, mark the missing information and ask the same Bot to correct it. Add another Bot only when a genuinely separate role or independent check would help.
Set it up in Hermes Desktop
Begin with one Bot and one manual run
Open the linked starter page, download its .tar.gz profile, and import it from the Profiles screen in Hermes Desktop.
Review the profile’s SOUL.md, Bot Passport, and requested access.
Run the complete request in that Bot’s chat with low-risk material and review the result.
Add a schedule, outside connection, or optional specialist only after the manual version works.