Set up Sprout for school

Gets Sprout reading what your kids' school sends: your inbox (through your own agent), your calendar, the school portals (found in your email) and the parent chat groups through Sprout Edge, then a weekday check of each and a daily check of your calendar against what was found. Run it in your own chat with Sprout.

Adopt
Set up Sprout for school

Walks a parent through getting Sprout reading what their kids' school sends: which of their agents reads their email, their calendar, the school portals, the parent chat groups. Ends by saving a weekday gather routine for each source and a daily check of the calendar against what was found for schedule conflicts, in the parent's own chat. Run it in the parent's private chat with Sprout on their first day, or any time to finish setup: it reads what is already connected first and never asks twice. Its inputs can carry a school pack (portal addresses, chat group names, inbox senders) so a parent who arrives with one is asked less.

How it works

  1. 1Your inbox and calendarAsks which of your agents reads your email and gives that agent's connect steps from Sprout's help. Connects your calendar in Sprout, or uses the one your agent reads.
  2. 2School portalsSearches your email for the school's portals and their sign-in addresses, then gives you a one-time sign-in link for each you confirm. Sprout never asks for a password.
  3. 3Parent chat groupsOffers the school groups Sprout Edge already lists on your Mac, or gives you the Sprout Edge download and steps, and asks you once to approve the reader.
  4. 4The routinesSaves a weekday check for each source and a daily check of your calendar against what was found, all in this chat. Nothing posts on its own unless something needs you.

Instructions

  1. Set the parent up so Sprout reads what their kids' school sends. You are in their own chat. One question per message, short plain words. Never ask for a password or a code. Their own agents only ever "listed" or "read" something as of their last check-in; only accounts Sprout itself holds are "connected". Keep a family memory note titled "School setup" (memory_write) with what is done, what is open, and the next step; at the start read it and continue from the first open step.
  2. This procedure is only in front of you on the turn it was invoked, so the note must carry it forward: start the note with exactly "SETUP IN PROGRESS: before every reply, call skill_get on the skill Set up Sprout for school (find it with skill_list), follow it from the next step named here, and update this note." and end it with "Next step: <number and name>". Save the note with the annotation intent "preference" so it is in front of you on every turn. End every reply while setup is in progress with one short line: "School setup: step <n> of 7, <name>." When setup is finished, replace the note's first line with "Setup finished." and stop adding that line.
  3. ​
  4. Pack values (empty = ask): school={{input.school}}; portals={{input.portals}}; groups={{input.chat_groups}}; senders={{input.inbox_senders}}
  5. ​
  6. 0. Check first: the note, care_fleet_status, integration_list, routine_list. Then one message: what you will set up (inbox, calendar, portals, chat groups, routines), about ten minutes, stop any time.
  7. 1. School: ask only if unknown. Never ask for the kids' names.
  8. 2. Inbox: name the agents the fleet shows reading email and ask which inbox the school writes to. If none, ask only which agent they use (Claude Code, ChatGPT, or none yet); ask for the inbox address and senders in later messages, one at a time. If they say none yet or later, do not ask for the address or senders: note step 2 as open and go straight to step 3. To connect one, call help_lookup and open agents/claude-code, agents/chatgpt, agents/claude-ai or agents/codex-computer, and give its steps and link exactly as written. Ask which sender domains the school uses.
  9. 3. Calendar: if Google Calendar is not connected in Sprout, recommend it ("simplest: Sprout reads it directly") and call integration_connect for google_calendar. If they prefer a calendar one of their agents reads, use that; the daily check reads either.
  10. 4. Portals: use the pack, or the addresses the parent gives. If they have none, start the email search right away and say you started it: care_file_request on the inbox, for the agent that reads it, asking "Search this inbox for the school's portal invitations and sign-in emails. For each portal give its name and its exact sign-in web address." When it comes back, the result card does not show the addresses: read them with memory_list and memory_read under /user/school/portals, then list each portal with its exact web address and ask "these?". For each one the parent confirms: care_add_portal with that exact web address, never a name alone (on a refusal say why and ask again, never guess); care_portal_sign_in_link (give the plain URL: one use, 30 minutes); after they sign in, portal_open and portal_read one page and say one line of what you saw. If the search is still running, go on and come back to it.
  11. 5. Chat groups need Sprout Edge on a Mac. If the fleet shows Edge groups (addresses starting "chat:"), offer the ones matching the school or class first. Otherwise, whenever the parent mentions WhatsApp or iMessage groups, at any step, your reply must include the Sprout Edge download link and steps: call help_lookup, open agents/sprout-edge, and give them exactly as written. If they have no Mac, keep the group names in the note as open. If the reader is waiting for approval, ask once, then care_approve_worker.
  12. 6. Routines. If nothing is connected yet (no agent reads the inbox, no portal, no linked group, no calendar), save nothing: say which one to connect first and that you will set the routines up then. Otherwise, only after they agree (default weekdays 7:00, conflicts daily 7:30, their timezone). routine_save in this chat; requests report back "Forms, payments, deadlines, events, schedule changes, anything a parent must do.":
  13. - "School inbox check": request, cron "0 7 * * 1-5", ask "Read the school's emails since the last check from <senders>: forms, payments, deadlines, events, schedule changes, new portal invitations, anything a parent must do.", requestKind check_school_email, requiresCapability gmail, address = the inbox.
  14. - "<portal> check", one per portal: request, cron "0 7 * * 1-5", ask "Read what is new on this portal since the last check.", requestKind check_school_portal, sourceKey = the portal's key.
  15. - "<group> check", one per linked group: request, cron "0 7 * * 1-5", ask "Read the newest messages in this group.", requestKind check_parent_chat, requiresCapability chat-reader, address "chat:<group>". Say it reads the newest messages for now.
  16. - If an agent reads the calendar: "Calendar gather": request, cron "0 7 * * *", ask "List every event for the next 7 days: title, day, time, place.", requestKind gather_calendar, requiresCapability calendar, address = the calendar account, assignTo that agent.
  17. - "Schedule conflicts", only when a calendar is connected (in Sprout or through an agent) or at least one routine above was saved; otherwise leave it in the note as open: prompt, cron "30 7 * * *", prompt "Read the calendar for the next 7 days (the calendar tools, and events the Calendar gather reported) and what this chat's routines found this week. Report only new overlaps or tight gaps, and anything due that is not on the calendar, one line each with day, time and source. If nothing is new, reply exactly 'Nothing new'. Never read the school's sources live."
  18. Act on each answer: schedule_taken, move a few minutes; a question about which agent has an account, ask the parent and save again with their answer (assignTo, confirmed); a note, say it as given and never claim it works.
  19. 7. Update the note, then finish in at most three lines: what is set up, what is still open, and that they only hear from you when something needs them.
  20. If they ask something else mid-way, answer it and offer to continue. If they say stop, update the note and stop.

Inputs

  • SchoolschoolThe school's name, when known. Leave empty to ask.
  • School portalsportalsComma-separated exact portal addresses (e.g. seesaw.me, unis.schoolpass.app). Leave empty to ask.
  • Parent chat groupschat_groupsComma-separated group names that carry school news (e.g. Grade 3 parents, UNIS PTA). Names only. Leave empty to ask.
  • Inbox sendersinbox_sendersComma-separated sender domains or addresses the school uses (e.g. @unis.edu). Leave empty to ask.

Capabilities

Nothing to flag. This one doesn’t use the camera, the microphone, or the internet.

Set up Sprout for school — Sprout