Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Daily briefing: gathers today's calendar, active todos, and local weather from available workspace tools, then composes a concise summary.
Daily briefing: gathers today's calendar, active todos, and local weather from available workspace tools, then composes a concise summary.
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Then review README.md for any prerequisites, environment setup, or post-install checks. Tell me what you changed and call out any manual steps you could not complete.
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. Then review README.md for any prerequisites, environment setup, or post-install checks. Summarize what changed and any follow-up checks I should run.
Compose a daily briefing using companion skills. Each source is optional β skip it if the skill is not available.
Three companion skills. Skip any that are not in the available skills list: Calendar β gcalcli-calendar Todos β todo-management Weather β openmeteo-sh-weather-simple (requires a default city/country in session context) If none of the three are available β tell the user you have nothing to build a briefing from and stop. Do not fabricate a briefing.
Decide whether the user's day is effectively over based on current time and today's remaining calendar events. Day still active -> briefing covers today. Day winding down -> briefing covers tomorrow. Todos are not date-bound β always show active items.
For each available source, read its SKILL.md before calling any commands.
Read gcalcli-calendar SKILL.md. Fetch the briefing day's agenda. If no events β note it.
Read todo-management SKILL.md. List active/pending items. If none β note it.
Get the briefing day's conditions and forecast. Use the user's default city/country from session context. Commands (always use --llm): Today: openmeteo weather --current --forecast-days=1 --city="{city}" --llm Tomorrow: openmeteo weather --current --forecast-days=2 --forecast-since=2 --city="{city}" --llm
If a command fails, skip that section and mention the failure briefly. Do not retry more than once. Never fabricate data.
Build a single message. Include only sections whose skill was available. If a skill returned no data, still include the section with a one-line note.
Title line β compact: date, day-of-week, time. E.g. ΠΡΠΈΡΠΈΠ½Π³ 14.02 (ΠΏΡ, 8:12). If briefing day is tomorrow, say so. Weather β 1β2 lines: temperature, sky, anything notable. Calendar β briefing day's events, chronologically. Format: HH:MM β Title. All-day events first. If empty: one line noting no events. Upcoming β next 2-3 days' notable events (if any), one line per day. Omit if nothing notable. Todos β active items, briefly. Higher priority first if supported. If empty: one line noting no todos.
Follow this format exactly in the user's language: Briefing 14.02 (Sat, 8:12) **π€ Weather (London, UK)** +2Β°C, cloudy, wind 11 km/h. Daytime to -3Β°C, light rain. **π Calendar** 09:00 β Standup 14:00 β Sprint review 18:30 β Driving school **π Upcoming** β’ 15.02: Free day. β’ 16.02: Daily standup 12:00, Driving school 18:30. **β Todos** β’ [work] Debug feature X. β’ [personal] Book a doctor's appointment. Note: bold header β content immediately on next line (zero blank lines); one blank line between sections; no trailing question or CTA.
These rules are critical for readability on mobile. Follow them exactly. Between sections: exactly one empty line. Between a section header and its content: zero empty lines. Content starts on the very next line. Right: **Calendar** 09:00 β Standup 14:00 β Review Wrong: **Calendar** 09:00 β Standup 14:00 β Review When briefing day is tomorrow, calendar and weather headers should reflect that. Do not shorten the user's city name. Match the language of the user's request. Simple formatting β optimize for mobile chat. Bold section headers, short lines. Concise, skimmable, no filler.
No preamble β dive straight in. No call to action or question at the end. The briefing ends after the last section. No "What's next?", "What's first?", or similar. Never invent events, todos, or weather data. Only report what tools returned.
Workflow acceleration for inboxes, docs, calendars, planning, and execution loops.
Largest current source with strong distribution and engagement signals.