2.6k
GitHub Stars
2
Bundled Files
2 months ago
Catalog Refreshed
4 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill openclaw/skills --skill wilma-triage- _meta.json456 B
- SKILL.md7.2 KB
Overview
This skill performs a daily triage of Wilma school notifications for Finnish parents. It fetches exams, messages, news, schedules, and homework, filters noise, surfaces actionable items, and syncs exams/events to Google Calendar. The skill requires the wilma skill and gog (gog CLI or gog skill) for calendar access.
How this skill works
On each run it reads student details and preferences from TOOLS.md and MEMORY.md, then calls wilma CLI commands to collect summaries, exams, schedules, homework, messages, and news. It applies triage rules to classify items as actionable, worth mentioning, or skippable, syncs new or changed exam events to the configured Google Calendar via gog, and reports findings in a concise chat summary. Calendar additions check for duplicates and removed events are deleted from the calendar.
When to use it
- Daily morning checks (recommended cron at 07:00) to capture schedule changes and exam updates
- Before school starts for the day to surface required materials or early dismissals
- When a weekly letter (viikkoviesti) or teacher message arrives and may contain buried actions
- After receiving parent/office announcements that could include deadlines or forms
- Whenever you want school exams synced to your Google Calendar automatically
Best practices
- Store student IDs and the target calendar ID in TOOLS.md and keep naming conventions consistent
- Record kid-specific rules and notification preferences in MEMORY.md so triage learns over time
- Always read full content of class teacher weekly letters (viikkoviesti) regardless of subject line
- Before adding events, search the calendar for matching date+child+subject keywords to avoid duplicates
- Keep the cron job isolated and staggered from other jobs to reduce API rate conflicts
Example use cases
- Detect a new math exam and add it to the family Google Calendar with the child and subject in the title
- Find a permission form request in a teacher message and report it immediately for parent action
- Remove a school disco event from the calendar when a cancellation message arrives
- Quietly skip city-wide informational notices but surface any school office monthly newsletter dates
- Daily short report showing one-line actionable items per child, or remain silent if nothing actionable
FAQ
Run wilma kids list to discover students, choose a calendar via gog calendar calendars, store the calendar ID and naming rules in TOOLS.md, and save any child-specific preferences in MEMORY.md.
How does the skill avoid duplicate calendar events?
It always checks the calendar for events in the same date range and with matching child and subject keywords; it only adds events when no suitable match exists.