Daily Briefing

Creates a morning briefing with priorities, calendar, and key updates

Security Scan

The skill's instructions, requirements, and behaviour are coherent with a morning briefing tool — it is instruction-only, requests no credentials or installs, and simply tells the agent how to assemble a briefing from available sources.

Purpose & Capability

The name/description (daily morning briefing) matches the runtime instructions: compile calendar, email highlights, tasks, news, weather and produce a concise briefing. No unrelated binaries, env vars, or install steps are requested.

Instruction Scope

Instructions are broadly written to 'pull from whatever's available' (calendar, email, CRM, tasks, web search). That openness is expected for a briefing skill, but it leaves discretion to the agent about which connectors to use and what data to read; users should verify which integrations the agent has access to before enabling automatic runs.

Install Mechanism

No install spec or code is included (instruction-only), so nothing will be downloaded or written to disk by the skill itself.

Credentials

The skill declares no required environment variables, credentials, or config paths. It may rely on existing platform connectors (calendar, email, CRM) but does not request extra secrets beyond what those connectors expose.

Persistence & Privilege

always is false and the skill is user-invocable; it does not request permanent/always-on inclusion or to modify other skills. It mentions optional cron/heartbeat use but does not itself install scheduling or change agent settings.

Assessment

This skill appears coherent, but before installing: confirm which calendar/email/CRM connectors the agent will use and what permissions they have (read-only vs modify); be cautious about enabling automatic scheduled runs (cron/heartbeat) if you don't want regular access to your inbox/calendar; consider restricting the agent's access to only the accounts/folders you want summarized; review any third-party 'context packs' links before using them; if you need strict privacy, only enable the skill for on-demand (manual) use rather than autonomous scheduling.

You create a concise morning briefing so the user starts their day knowing exactly what matters.

When Triggered

User says: "Brief me", "Morning briefing", "What's on today?", "Start my day" Or: run automatically via heartbeat/cron if configured.

Briefing Template

☀️ DAILY BRIEFING — [Day, Month Date, Year]
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

📅 TODAY'S SCHEDULE
• [Time] — [Event] ([Location/Link])
• [Time] — [Event] ([Location/Link])
• [No meetings today — deep work day!]

🎯 TOP 3 PRIORITIES
1. [Most important thing]
2. [Second priority]
3. [Third priority]

📧 INBOX HIGHLIGHTS
• [Urgent/important emails worth noting]
• [X unread emails, Y flagged]

📰 RELEVANT NEWS
• [Industry news or updates that matter]

⚡ FOLLOW-UPS DUE
• [Person] — [Action] (was due [date])
• [Person] — [Action] (due today)

💡 HEADS UP
• [Upcoming deadlines this week]
• [Meetings to prep for tomorrow]
• [Anything else worth knowing]

Priority Framework

Rank tasks using this matrix:

	Urgent	Not Urgent
Important	DO FIRST — Calendar conflicts, client emergencies, deadlines today	SCHEDULE — Strategic work, planning, relationship building
Not Important	DELEGATE/QUICK — Admin tasks, routine replies	SKIP — Time-wasters, low-value meetings

Data Sources

Pull from whatever's available:

• Calendar — Today's events and tomorrow's early events
• Email — Unread count, flagged/urgent messages, key senders
• CRM — Follow-ups due (if crm-manager skill is active)
• Tasks/Notes — Any tracked to-dos or project notes
• News — Industry-relevant headlines via web search
• Weather — Quick forecast if relevant

Rules

• Keep it scannable. The whole briefing should take 60 seconds to read.
• Prioritize ruthlessly. Don't list everything — list what matters.
• If calendar is empty, say so (that's useful info — it's a deep work day).
• If no email access, skip that section. Don't fake it.
• End with something useful — a heads-up about tomorrow or this week.
• Adjust tone to time of day. Morning = energetic. Evening recap = reflective.
• Include time zones if the user works across zones.

Evening Recap (Optional)

If asked at end of day: "How'd today go?" or "End of day recap"

🌙 END OF DAY — [Date]
━━━━━━━━━━━━━━━━━━━━

✅ COMPLETED
• [What got done]

🔄 CARRIED OVER
• [What didn't get done — moves to tomorrow]

📝 NOTES
• [Key decisions, insights, things to remember]

📅 TOMORROW PREVIEW
• [First meeting/deadline]