Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsBlogPro
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges
  • Chrome Extension
  • Skill Manager

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Daily Briefing

ASecurity

Build a morning briefing ritual with Muse: overnight priorities, today's calendar, weather-aware planning, and top 3 focus items as a concise chat summary.

2 stars
0 votes
0 copies
0 views
Added 9/29/2026
ai-agentsgoreact

Works with

cli

Security Analysis

A100/100

Scanned 9/29/2026

$npx -y skills add aicodedecode/awesome-muse-skills --skill daily-briefing --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Daily Briefing?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Daily Briefing
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/aicodedecode-daily-briefing/badge)](https://www.skillsdirectory.com/skills/aicodedecode-daily-briefing)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
Files
SKILL.md
---
name: daily-briefing
description: Build a morning briefing ritual with Muse: overnight priorities, today's calendar, weather-aware planning, and top 3 focus items as a concise chat summary.
category: everyday-assistant
---

# Daily Briefing

## Overview

A daily briefing is a short morning conversation with Muse that sets the tone for the day. Instead of discovering your schedule one surprise at a time, you get a single concise summary: what happened overnight, what's on your calendar, what the weather means for your plans, and — most importantly — the top three things that actually matter today. The whole ritual takes five minutes and replaces the anxious first hour of reactive checking. It's a conversation, not an app: you talk, Muse assembles and prioritizes, you adjust.

## When to use

- Every morning, as the start-of-day ritual (5 minutes, same time each day works best)
- When your calendar is packed and you need help deciding what deserves your energy
- Before travel days, to check weather, meetings, and timing in one pass
- When you wake up to unread messages and need help separating urgent from noise
- When you want to start the day intentionally instead of reactively

## Core concepts

- **One conversation, not five tabs.**
  The value is consolidation: priorities, calendar, weather, and messages in a single chat summary instead of scattered across apps.
- **Top 3 focus items.**
  Everything else is context; three items are commitments. Three is small enough to remember and big enough to matter. Muse proposes them; you approve or swap.
- **Weather-aware planning.**
  Weather changes clothing, commute timing, and whether outdoor plans are sensible. A briefing that ignores weather is just a calendar readout.
- **Overnight triage.**
  Some messages that arrived overnight are time-sensitive; most aren't. The briefing filters so you only act on the genuinely urgent before noon.
- **Calendar is truth, not suggestion.**
  The briefing reads your calendar as it is. If something's wrong there, fix the calendar first — briefing quality depends on calendar quality.
- **Evenings feed mornings.**
  A thirty-second evening note ("tomorrow's big thing is the client call") makes the next morning's briefing sharper. The briefing is a loop, not a broadcast.
- **Prep items get named, not implied.**
  If something needs preparation, the briefing should say what and by when — "prep 20 min for the 2pm review" — not just list the event.

## Practical workflow

1. **Say good morning with context.**
   Open with something like: "Good morning — give me my briefing for today." If it's your first time, add the basics: your timezone, your rough hours, and what "a good day" looks like for you this week.
2. **Share what Muse can see.**
   Tell Muse where to look: "Check my calendar for today and any messages from overnight." Name the sources you care about — calendar, email, chat — so it doesn't guess.
3. **Ask for weather that affects plans.**
   Prompt: "How's the weather today, and does it affect anything on my calendar?" Muse connects conditions to your actual plans — commute, outdoor meetings, errands.
4. **Get the top 3 proposed.**
   Ask: "What's my top 3 focus for today?" Muse weighs deadlines, calendar density, and what you told it matters this week, then proposes three. Push back: "Swap item 2 — that can wait; instead..." The negotiation is the point.
5. **Flag the landmines.**
   Ask: "Anything tonight or tomorrow that changes what I do today?" Prep work, early meetings, and deadlines have a way of hiding. Surface them now.
6. **Confirm and close.**
   End with: "Summarize my day in three lines so I can glance back later." You get a compact reference you can re-open any time. Then close the laptop for a minute and breathe — the briefing's job is done.

## Common pitfalls

- **Letting the briefing become a to-do dump.**
  Fifteen items is not a briefing, it's anxiety. Insist on the top 3; everything else is just listed, not committed to.
- **Skipping the weather question.**
  It's the easiest thing to forget and the most common cause of a ruined plan. Make it a fixed part of the ritual.
- **Briefing without an accurate calendar.**
  If your calendar is missing half your commitments, the briefing optimizes the wrong day. Keep the calendar honest and the briefing stays useful.
- **Treating the top 3 as rigid.**
  Life happens. The top 3 is a compass, not a contract — rearrange when reality changes, and tell Muse so it learns your actual priorities.
- **Doing the briefing too late.**
  A briefing at 10:30 after you've already reacted to everything is a debrief. Same time each morning, before the noise starts.
- **Never customizing the format.**
  The default summary works for week one. By week two, tell Muse what to keep and cut: "Skip the news section; always include my workout." The ritual should fit you.
- **Skipping weekends and travel days.**
  The days you need a briefing most — travel, Mondays after a holiday — are the easiest to skip. Those are the days that pay for the habit.
- **Trigger phrases for Muse.**
  Phrases like "start my day," "morning briefing," or "what's my day look like?" should always trigger this ritual once you've set it up. Tell Muse that explicitly so it doesn't need re-explaining.
- **Briefing a partner or team.**
  Once your own ritual works, extend it: "Give me a two-line summary I can share with my partner about today's logistics." Shared mornings run smoother.
- **Briefing on the go.**
  Mornings happen in cars and on trains too. The briefing is just a chat — voice or text both work. The format survives either medium.
- **Turning the briefing into planning.**
  Briefing is orientation; planning is separate work. If the summary keeps growing into a planning session, split them — five minutes to orient, then plan separately if needed.
- **Ignoring energy, not just time.**
  A packed calendar of low-energy admin after a late night is a different day than the same calendar when rested. Tell Muse your energy; let it sequence accordingly.

Attribution

aicodedecodeaicodedecode
View sourceSee grades on GitHubMore from aicodedecode →
SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Related Skills

Caveman

Terse caveman voice: answer first, fluff gone, every technical fact kept. Use for /caveman, "caveman mode", "talk like caveman", "be brief", "less tokens". Stays on until "stop caveman" or "normal mode".

1100021 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

698621 votes

Writing Skills

Create and manage Claude Code skills in HASH repository following Anthropic best practices. Use when creating new skills, modifying skill-rules.json, understanding trigger patterns, working with hooks, debugging skill activation, or implementing progressive disclosure. Covers skill structure, YAML frontmatter, trigger types (keywords, intent patterns), UserPromptSubmit hook, and the 500-line rule. Includes validation and debugging with SKILL_DEBUG. Examples include rust-error-stack, cargo-dep...

3931 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3421 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Amp, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Grok Build, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

741 votes
View all in ai-agents →