{ "schemaVersion": "1.0", "item": { "slug": "wilma-triage", "name": "Wilma Triage", "source": "tencent", "type": "skill", "category": "通讯协作", "sourceUrl": "https://clawhub.ai/aikarjal/wilma-triage", "canonicalUrl": "https://clawhub.ai/aikarjal/wilma-triage", "targetPlatform": "OpenClaw" }, "install": { "downloadMode": "redirect", "downloadUrl": "/downloads/wilma-triage", "sourceDownloadUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=wilma-triage", "sourcePlatform": "tencent", "targetPlatform": "OpenClaw", "installMethod": "Manual import", "extraction": "Extract archive", "prerequisites": [ "OpenClaw" ], "packageFormat": "ZIP package", "includedAssets": [ "SKILL.md" ], "primaryDoc": "SKILL.md", "quickSetup": [ "Download the package from Yavira.", "Extract the archive and review SKILL.md first.", "Import or place the package into your OpenClaw setup." ], "agentAssist": { "summary": "Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.", "steps": [ "Download the package from Yavira.", "Extract it into a folder your agent can access.", "Paste one of the prompts below and point your agent at the extracted folder." ], "prompts": [ { "label": "New install", "body": "I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete." }, { "label": "Upgrade existing", "body": "I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run." } ] }, "sourceHealth": { "source": "tencent", "slug": "wilma-triage", "status": "healthy", "reason": "direct_download_ok", "recommendedAction": "download", "checkedAt": "2026-05-01T20:38:03.787Z", "expiresAt": "2026-05-08T20:38:03.787Z", "httpStatus": 200, "finalUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=wilma-triage", "contentType": "application/zip", "probeMethod": "head", "details": { "probeUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=wilma-triage", "contentDisposition": "attachment; filename=\"wilma-triage-1.0.1.zip\"", "redirectLocation": null, "bodySnippet": null, "slug": "wilma-triage" }, "scope": "item", "summary": "Item download looks usable.", "detail": "Yavira can redirect you to the upstream package for this item.", "primaryActionLabel": "Download for OpenClaw", "primaryActionHref": "/downloads/wilma-triage" }, "validation": { "installChecklist": [ "Use the Yavira download entry.", "Review SKILL.md after the package is downloaded.", "Confirm the extracted package contains the expected setup assets." ], "postInstallChecks": [ "Confirm the extracted package includes the expected docs or setup files.", "Validate the skill or prompts are available in your target agent workspace.", "Capture any manual follow-up steps the agent could not complete." ] }, "downloadPageUrl": "https://openagent3.xyz/downloads/wilma-triage", "agentPageUrl": "https://openagent3.xyz/skills/wilma-triage/agent", "manifestUrl": "https://openagent3.xyz/skills/wilma-triage/agent.json", "briefUrl": "https://openagent3.xyz/skills/wilma-triage/agent.md" }, "agentAssist": { "summary": "Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.", "steps": [ "Download the package from Yavira.", "Extract it into a folder your agent can access.", "Paste one of the prompts below and point your agent at the extracted folder." ], "prompts": [ { "label": "New install", "body": "I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete." }, { "label": "Upgrade existing", "body": "I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run." } ] }, "documentation": { "source": "clawhub", "primaryDoc": "SKILL.md", "sections": [ { "title": "Wilma Triage", "body": "Automated daily triage of Wilma school data for parents. Filters noise, surfaces actionable items, and syncs exams/events to Google Calendar." }, { "title": "Dependencies", "body": "wilma skill — install from ClawHub (clawhub install wilma) for Wilma CLI commands and setup\ngog skill — install from ClawHub (clawhub install gog) for Google Calendar sync" }, { "title": "First Run Setup", "body": "On first use, collect and store configuration:\n\nDiscover kids: Run wilma kids list --json to get student names, numbers, and schools\nCalendar ID: Run gog calendar calendars to list available calendars. Ask the user which calendar to use for school events. Store the calendar ID in TOOLS.md under a ## Wilma Triage section along with naming conventions for events.\nPreferences: Ask about any kid-specific rules (e.g., subject overrides like ET instead of religion). Store in MEMORY.md as part of the Wilma triage context.\n\nOver time, the user will give feedback on what to report and what to skip — store these preferences in MEMORY.md. The triage gets smarter with use." }, { "title": "Workflow", "body": "Fetch data — check TOOLS.md for student details, then start with summary:\n# Best starting point — returns schedule, exams, homework, news, messages\nwilma summary --all-students --json\n\n# Drill into specifics as needed\nwilma exams list --all-students --json\nwilma schedule list --when today --all-students --json\nwilma schedule list --when tomorrow --all-students --json\nwilma homework list --all-students --limit 10 --json\nwilma grades list --all-students --limit 5 --json\nwilma messages list --all-students --limit 10 --json\nwilma news list --all-students --limit 10 --json\n\n# Read full content when subject line looks actionable\nwilma messages read --student --json\nwilma news read --student --json\n\n\n\nFilter — apply triage rules below plus any kid-specific rules from MEMORY.md\n\n\nCalendar sync — add missing exams and actionable events using gog CLI commands from TOOLS.md\n\nALWAYS check for existing events before adding to avoid duplicates\nUse naming conventions stored in TOOLS.md\nRemove cancelled events from calendar\n\n\n\nReport — if actionable items found, send details. If nothing actionable, stay silent or send a brief confirmation. Check MEMORY.md for the user's notification preference." }, { "title": "Calendar Sync", "body": "Refer to TOOLS.md for the calendar ID, naming conventions, and exact gog CLI commands.\n\nNO DUPLICATES rule:\n\nBefore adding any event, check calendar for that date range\nIf a matching event exists (same date + child + subject keywords), skip it\nOnly add if not already there" }, { "title": "Understanding Wilma Messages", "body": "Wilma messages come from different sources and have very different signal-to-noise ratios. Knowing the difference is critical for good triage:\n\nViikkoviesti / weekly letter (from class teacher) — HIGH VALUE. These are the class teacher's weekly updates. They look like casual newsletters but frequently contain buried actionable items: upcoming exams, materials to bring, schedule changes, field trips, deadlines. Always read the full content. Never skip based on subject line.\nTeacher messages (from subject teachers) — Usually about specific exams, homework, or class events. High signal.\nSchool office / rehtori messages — Administrative: schedule changes, events, policy updates. Medium signal — skim for actions.\nKuukausitiedote / monthly newsletter (from school office) — Read these. They typically contain important dates: holidays, school year start/end, event schedules, enrollment deadlines. Don't skip based on the generic subject line.\nCity-wide notices (from Helsinki/municipality) — Health campaigns, transport info, surveys. Usually noise for daily triage. Skim subject, skip unless clearly actionable.\nParent union / vanhempainyhdistys — Low signal by default (fundraising, volunteer calls). However, check MEMORY.md — if the parent is actively involved in the union, these become high priority.\n\nRule of thumb: If a message is from a teacher (class teacher or subject teacher), always read it. If it's from the school office or city, skim the subject and skip unless it's clearly actionable." }, { "title": "Always Report (Actionable)", "body": "Forms, permission slips, replies needed\nDeadlines (sign-ups, payments, materials to bring)\nSchedule changes (early dismissal, cancelled classes, substitute arrangements)\nSpecial gear/materials needed (e.g., \"bring ski gear\", \"outdoor clothing\")\nAfter-school events kids might want to attend (discos, movie nights)\nExam schedule updates or new exams\nCancelled events that are on the calendar → remove them" }, { "title": "Report Briefly (Worth Mentioning)", "body": "Field trips, themed days with date info\nSchool closures, holiday schedule changes\nHealth notices (lice alerts, illness outbreaks)\nNew grades (brief mention with grade)" }, { "title": "Important: Always Read Weekly Letters (viikkoviesti)", "body": "Weekly letters from class teachers often contain actionable items buried in the text: exams, materials to bring, schedule changes, field trips. Always read the full content of viikkoviesti messages — do not skip based on subject line alone." }, { "title": "Skip Silently", "body": "Concerts, cultural performances (FYI only)\nGeneric \"welcome back\" or seasonal greetings\nCity-wide informational notices (health campaigns, transport info, surveys)\nParent union messages (unless user is actively involved — check MEMORY.md)\n\nCheck MEMORY.md for additional skip/report rules the user has provided over time (e.g., subject overrides, school-specific filtering)." }, { "title": "Suggested Cron Setup", "body": "Run daily at 07:00 local time as an isolated agentTurn job:\n\nSchedule: 07:00 daily\nTimeout: 180s\nTask: \"Read the wilma-triage skill, then run the full triage workflow. Report actionable findings.\"\n\nStagger with other morning jobs (e.g., email check at 07:05) to avoid API rate limits." }, { "title": "Output Format Example", "body": "📚 Wilma Update\n\nChild A (8th grade)\n• Math exam tomorrow — yhtälöt, kpl 1-8\n• Friday short day (9:20-12:35) — kulttuuripäivä, bring laptop + outdoor clothes\n\nChild B (6th grade)\n• No actionable items\n\n📅 Calendar: Added Child A math exam (Feb 10), removed cancelled disco (Feb 11)\n\nKeep it brief. One line per item. Silence is better than noise." } ], "body": "Wilma Triage\n\nAutomated daily triage of Wilma school data for parents. Filters noise, surfaces actionable items, and syncs exams/events to Google Calendar.\n\nDependencies\nwilma skill — install from ClawHub (clawhub install wilma) for Wilma CLI commands and setup\ngog skill — install from ClawHub (clawhub install gog) for Google Calendar sync\nFirst Run Setup\n\nOn first use, collect and store configuration:\n\nDiscover kids: Run wilma kids list --json to get student names, numbers, and schools\nCalendar ID: Run gog calendar calendars to list available calendars. Ask the user which calendar to use for school events. Store the calendar ID in TOOLS.md under a ## Wilma Triage section along with naming conventions for events.\nPreferences: Ask about any kid-specific rules (e.g., subject overrides like ET instead of religion). Store in MEMORY.md as part of the Wilma triage context.\n\nOver time, the user will give feedback on what to report and what to skip — store these preferences in MEMORY.md. The triage gets smarter with use.\n\nWorkflow\n\nFetch data — check TOOLS.md for student details, then start with summary:\n\n# Best starting point — returns schedule, exams, homework, news, messages\nwilma summary --all-students --json\n\n# Drill into specifics as needed\nwilma exams list --all-students --json\nwilma schedule list --when today --all-students --json\nwilma schedule list --when tomorrow --all-students --json\nwilma homework list --all-students --limit 10 --json\nwilma grades list --all-students --limit 5 --json\nwilma messages list --all-students --limit 10 --json\nwilma news list --all-students --limit 10 --json\n\n# Read full content when subject line looks actionable\nwilma messages read --student --json\nwilma news read --student --json\n\n\nFilter — apply triage rules below plus any kid-specific rules from MEMORY.md\n\nCalendar sync — add missing exams and actionable events using gog CLI commands from TOOLS.md\n\nALWAYS check for existing events before adding to avoid duplicates\nUse naming conventions stored in TOOLS.md\nRemove cancelled events from calendar\n\nReport — if actionable items found, send details. If nothing actionable, stay silent or send a brief confirmation. Check MEMORY.md for the user's notification preference.\n\nCalendar Sync\n\nRefer to TOOLS.md for the calendar ID, naming conventions, and exact gog CLI commands.\n\nNO DUPLICATES rule:\n\nBefore adding any event, check calendar for that date range\nIf a matching event exists (same date + child + subject keywords), skip it\nOnly add if not already there\nUnderstanding Wilma Messages\n\nWilma messages come from different sources and have very different signal-to-noise ratios. Knowing the difference is critical for good triage:\n\nViikkoviesti / weekly letter (from class teacher) — HIGH VALUE. These are the class teacher's weekly updates. They look like casual newsletters but frequently contain buried actionable items: upcoming exams, materials to bring, schedule changes, field trips, deadlines. Always read the full content. Never skip based on subject line.\nTeacher messages (from subject teachers) — Usually about specific exams, homework, or class events. High signal.\nSchool office / rehtori messages — Administrative: schedule changes, events, policy updates. Medium signal — skim for actions.\nKuukausitiedote / monthly newsletter (from school office) — Read these. They typically contain important dates: holidays, school year start/end, event schedules, enrollment deadlines. Don't skip based on the generic subject line.\nCity-wide notices (from Helsinki/municipality) — Health campaigns, transport info, surveys. Usually noise for daily triage. Skim subject, skip unless clearly actionable.\nParent union / vanhempainyhdistys — Low signal by default (fundraising, volunteer calls). However, check MEMORY.md — if the parent is actively involved in the union, these become high priority.\n\nRule of thumb: If a message is from a teacher (class teacher or subject teacher), always read it. If it's from the school office or city, skim the subject and skip unless it's clearly actionable.\n\nTriage Rules\nAlways Report (Actionable)\nForms, permission slips, replies needed\nDeadlines (sign-ups, payments, materials to bring)\nSchedule changes (early dismissal, cancelled classes, substitute arrangements)\nSpecial gear/materials needed (e.g., \"bring ski gear\", \"outdoor clothing\")\nAfter-school events kids might want to attend (discos, movie nights)\nExam schedule updates or new exams\nCancelled events that are on the calendar → remove them\nReport Briefly (Worth Mentioning)\nField trips, themed days with date info\nSchool closures, holiday schedule changes\nHealth notices (lice alerts, illness outbreaks)\nNew grades (brief mention with grade)\nImportant: Always Read Weekly Letters (viikkoviesti)\n\nWeekly letters from class teachers often contain actionable items buried in the text: exams, materials to bring, schedule changes, field trips. Always read the full content of viikkoviesti messages — do not skip based on subject line alone.\n\nSkip Silently\nConcerts, cultural performances (FYI only)\nGeneric \"welcome back\" or seasonal greetings\nCity-wide informational notices (health campaigns, transport info, surveys)\nParent union messages (unless user is actively involved — check MEMORY.md)\n\nCheck MEMORY.md for additional skip/report rules the user has provided over time (e.g., subject overrides, school-specific filtering).\n\nSuggested Cron Setup\n\nRun daily at 07:00 local time as an isolated agentTurn job:\n\nSchedule: 07:00 daily\nTimeout: 180s\nTask: \"Read the wilma-triage skill, then run the full triage workflow. Report actionable findings.\"\n\n\nStagger with other morning jobs (e.g., email check at 07:05) to avoid API rate limits.\n\nOutput Format Example\n📚 Wilma Update\n\nChild A (8th grade)\n• Math exam tomorrow — yhtälöt, kpl 1-8\n• Friday short day (9:20-12:35) — kulttuuripäivä, bring laptop + outdoor clothes\n\nChild B (6th grade)\n• No actionable items\n\n📅 Calendar: Added Child A math exam (Feb 10), removed cancelled disco (Feb 11)\n\n\nKeep it brief. One line per item. Silence is better than noise." }, "trust": { "sourceLabel": "tencent", "provenanceUrl": "https://clawhub.ai/aikarjal/wilma-triage", "publisherUrl": "https://clawhub.ai/aikarjal/wilma-triage", "owner": "aikarjal", "version": "1.0.1", "license": null, "verificationStatus": "Indexed source record" }, "links": { "detailUrl": "https://openagent3.xyz/skills/wilma-triage", "downloadUrl": "https://openagent3.xyz/downloads/wilma-triage", "agentUrl": "https://openagent3.xyz/skills/wilma-triage/agent", "manifestUrl": "https://openagent3.xyz/skills/wilma-triage/agent.json", "briefUrl": "https://openagent3.xyz/skills/wilma-triage/agent.md" } }