When should you use it?
- Assignments are scattered across portals
- Your child misses due dates
- You check the school site every evening
Not for: Schools that forbid automated logins; Data you would not want held by the agent provider
What do you need, and what do you get?
You need
- School portal login stored in a vault
- Child's calendar
- List of other sites teachers use
You get
- Calendar entries per assignment
- Alert ahead of each deadline
How does it work, step by step?
- Write the procedureList the sites, what counts as homework and how events should look.
- Store the login safelyUse the agent's credential vault, not the prompt.
- Run dailySchedule the check for the same time each day.
- Avoid duplicatesHave it update existing events when a due date changes.
- Review weeklyCompare the calendar with the portal once a week at first.
The prompt
Our own prompt, inspired by fnordpiglet on Hacker News and written to work in Custom agent, Grok Bot, ChatGPT agent and others. Values in lime are placeholders.
Fill in the blanks (optional; the copied prompt uses your values)
Every day at {time}, sign in to {school_portal} with the stored credential. Collect assignments with subject, title and due date. Add or update an event in {child_calendar} on the deadline, set an alert for the prior evening, and link the source page. End with a one-line summary of items found; if login fails, tell me instead of reporting zero.
Inspired by fnordpiglet on Hacker News: Hacker News comment on a first Muse workflow for school homework. The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.
What can go wrong?
- Portals change layout; a silent failure looks like a week with no homework.
- Share only what you are comfortable with the provider holding.
Our take
The habit of writing the procedure down before automating it is the transferable part. A clear spec says which sites to check, what counts as an assignment and how events should be named. fnordpiglet's setup is a good example of writing the procedure down before automating it: which sites to check, what counts as an assignment, how events should be named, and an alert the night before. Store the logins in the agent's credential vault rather than the prompt. Have it update existing events when a due date changes instead of adding duplicates. The risk is a silent failure; if the portal changes its layout, a week with no homework looks exactly like a broken run, so compare the calendar with the portal weekly at first. Check that the school allows automated logins, and only share what you are comfortable having the provider hold about your child. Keep your own eye on big deadlines.
Where the time goes back: Your child sees assignments where they already look, and you stop checking the portal each night.
FAQ
What is the point of writing the procedure first?
Is it reliable yet?
Source and credit
Inspired by fnordpiglet 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 a first Muse workflow for school homework
- Creator
- fnordpiglet on Hacker News
- Published on
- Hacker News
- Original date
- Sep 22, 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.