What Sunny can do

Ask Sunny "what can you do?" and you don't get a paragraph about being a helpful assistant. You get the list: the actual skills it has, grouped by area, each one with an example you can tap to run.

The same list is on the tray as capability cards, and in full under All skills.

It's the real list, not a brochure

The skills come from the same place Sunny's own permissions come from. It can't advertise something it would then refuse to do, and a skill it can't run for you never appears.

That means two people at the same school see different lists.

• Teachers see the classroom-shaped skills: a child's profile, today's daily report, the roster for a room, attendance, lesson seeds, observations, filing an incident.
• Directors and admins see those plus the school-wide ones: today's attendance and staffing, roster summaries, billing health, paperwork completeness, inspection readiness, curriculum coverage, family tasks.

Plan matters too

Some skills are part of the Grow plan. On the Run plan they aren't in the list at all, and if you ask for one anyway Sunny tells you it's a Grow feature rather than saying you don't have permission. The difference matters, because one is a plan question and the other is a role question.

The Grow-only skills are the enrollment and growth ones: the enrollment pipeline, the pipeline board, the enrollment funnel, occupancy forecasting, family engagement, churn analysis, and drafting outreach. Reading paper forms is Grow too: see scan a paper form.

Every example is safe to tap

Tapping a skill's example runs it. Skills that answer a question answer immediately; skills that would touch the world (send a message, file a document, change a record) stop and hand you a draft to approve instead. So exploring the list can never cost you anything. See drafts wait for your team.

The 30-second demo

The first time a director or admin opens the tray, Sunny offers to show itself working: it runs one read-only ask against your school's real records, the steps tick in, a real answer lands, and a draft appears with its approve button visibly switched off: "dashed means it hasn't happened, and in a demo it never does."

Skip it at any point. You can run it again later from the skills directory, or on the web at /assist/demo. A brand-new school with no data yet gets the same walkthrough on clearly-labelled sample data.

The demo only ever calls read-only skills, and its draft can't be approved: not by tapping, and not by any other route.

If you're not sure what to ask

The suggestions on the tray change with the time of day, and the capability cards each carry a phrasing that works. You don't have to learn a command language; plain sentences are the interface. "Who's out today, and why?" "Draft this week's family newsletter." "Are we short-staffed anywhere today?"