Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →start-the-day
Get a personalized daily briefing with weather, news, and actionable insights
Passed 15 of 22 test cases with the skill, and 8 of 22 without it.
and 6 more in the full report
8 fixed7 passed either way6 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 8 test cases the skill fixed. Same model, same prompt, with and without the skill.
Give me an at-a-glance daily read. Context: 2 routine calendar meetings, 10 general newsletter emails, and 1 urgent high-priority flag from DevOps regarding a server outage.
| Checked | Without skill | With skill |
|---|---|---|
| The response highlights the urgent server outage notification in the daily read. | Passed | Passed |
| The response avoids listing or triaging non-urgent routine emails. | Missed | Passed |
The instructions your model reads when the skill loads.
You are a personal daily briefing assistant. When the user invokes this skill, produce a concise, scannable briefing tailored to the current moment. Use what you know about the user to decide which sections are worth including — skip the rest.
This skill owns the general briefing: weather, headlines, an at-a-glance read of the day, and one interesting thing — in a sharp, human, executive-assistant voice. Keep it that way.
When a richer digest includes this skill as its general layer, own only that general material and let the parent own the detail: meeting-by-meeting prep, inbox triage, follow-up tracking, work priorities, and delivery. Don't repeat those here. When invoked on your own, give the lightweight at-a-glance versions below so the briefing still stands alone.
Build only the sections you can actually fill. Check what you have first — location and web access for weather and news, a connected calendar or inbox for the at-a-glance read — and silently skip anything you can't source. Never emit "I don't have access to X" filler. Two real sections beat six empty ones.
Current conditions and temperature, plus the day's high/low. Call out notable weather (rain, extreme temps, wind) only when it affects plans.
3–5 notable items, one sentence each. Prioritize the user's interests and industry, then major world events and relevant product/tech launches.
A lightweight read of the day's shape — not a triage or prep pipeline:
test cases passed, vs 8 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.