agentleFS
mgonzalezbailemgonzalezbaile/personal-assistant/.claude/skills/daily-briefing/SKILL.md

daily-briefing

Skill8 starsChanged 6 months agoMITView on GitHub

Use when the user asks about their plan, agenda, to-do list, schedule, what's on their plate, what they should work on, morning briefing, or any synonym. Builds the complete daily picture — calendar events, pull requests awaiting review or assigned, and every task from TASKS.md.

36 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use crm-lookup, spotify and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • QuixiAISkill

    crm-lookup

    Search, view, update, and merge contacts in the local CRM

    Also in 3 projects that use this

  • QuixiAISkill

    spotify

    Search Spotify, inspect current playback and devices, and control playback with explicit approval

    Also in 3 projects that use this

  • MicrosoftSkill

    inbox-triage

    Use this skill whenever the user asks to clean up, triage, declutter, or archive low-value Outlook inbox mail - "clean up my inbox", "triage my mail", "declutter my inbox", "sort out newsletters", "archive old resolved threads", "/inbox-triage" - to group only newsletters, auto-notifications, past-event meeting logistics, resolved threads, and redundant duplicates into reviewable move-proposals presented for per-bucket approval before any message moves. Do not use for reading mail, drafting or sending replies, deleting mail, executing moves without explicit per-bucket approval, or acting on messages from the user's manager, direct reports, active threads, flagged mail, or labelled/HR/Legal/Finance/Security senders.

    Also in 4 projects that use this

  • MicrosoftSkill

    image-gen

    Also in 3 projects that use this

  • AnthropicSkill

    weather

    The optional standing status report ("the weather"): compile open incidents, build health, merge-queue stats, and deploy lag into one always-current report page, and post to the channel only when a defined event fires. Use when the weather routine fires, or when someone asks to run/update the weather report.

    Also in 3 projects that use this

  • SentrySkill

    notion

    Search, fetch, create, update, and move Notion pages and data sources. Use when users ask to look up docs, specs, notes, meeting notes, project context, roadmaps, trackers, or internal references stored in Notion, or when they explicitly ask to create or edit Notion content.

    Also in 3 projects that use this

  • +2 more from QuixiAI

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 33 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Do NOT trigger for narrow lookups ("what's my next meeting?", "any PRs from Karan?").

    line 20
  2. Distinctive:

    Use this plan format:

    line 47
  3. Distinctive:

    Only show sections that have tasks, except "Do now" which always appears

    line 85
  4. Distinctive:

    After the plan, offer a short next step ("want me to tackle #1?" / "should I draft a plan around the workshop?").

    line 96

“Common” is measured: kept by at least 6 in 10 of the 33 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Daily Briefing

Produces {{NAME}}'s complete daily picture by gathering three data sources in parallel and presenting them in the plan format defined in CLAUDE.md.

When to trigger

Whenever {{NAME}} asks anything that means "give me the big picture of my day":

  • "What's my plan for today?" / "What's my agenda?"
  • "What's on my to-do?" / "What's in my to-do list?"
  • "What should I work on today?" / "What's on my plate?"
  • "Morning briefing" / "What's my schedule?"
  • Any close synonym.

Do NOT trigger for narrow lookups ("what's my next meeting?", "any PRs from Karan?"). Those don't need the full briefing.

Step 1 — Gather data IN PARALLEL

Issue all three tool calls in a single message. Never sequential.

1a. Calendar — today's events via gws (see the google-workspace-cli skill for CLI details):

gws calendar events list --params '{"calendarId": "primary", "timeMin": "YYYY-MM-DDT00:00:00Z", "timeMax": "YYYY-MM-DDT23:59:59Z", "singleEvents": true, "orderBy": "startTime"}'

Pipe through a short python snippet to get HH:MM - HH:MM Title [type] per line.

1b. Pull requests — two gh queries:

gh search prs --review-requested={{GH_HANDLE}} --state=open
gh search prs --assignee={{GH_HANDLE}} --state=open

Empty output = none.

1c. Tasks — Read TASKS.md. Capture every item in Active and Someday.

Step 2 — Present the picture

Use this plan format:

Good morning, {{NAME}}. [Day] [Month] [Date].

📅 [Meeting 1] [time]
📅 [Meeting 2] [time]
(or: 📅 No meetings today — full day for deep work.)

**Do now** (urgent + important)

1. [Task] `[tag]`

2. [Task] `[tag]`

**Schedule** (important, not urgent)

3. [Task] `[tag]`

4. [Task] `[tag]`

**Delegate** (urgent, not important)

5. [Task] `[tag]`

(or: _(nothing today)_ if empty)

**Backlog** (not urgent, not important)

6. [Task] `[tag]`

(or: _(nothing today)_ if empty)

Format rules:

  • One line per task, no long explanations
  • Inline tag after each task: 2-4 words max (e.g., due tomorrow, unblocks team, quick win)
  • Blank line between every numbered item for readability
  • Only show sections that have tasks, except "Do now" which always appears
  • Empty sections show (nothing today)
  • Greeting adapts to time of day (Good morning / afternoon / evening)

Additional constraints:

  • PRs awaiting review always land in "Do now" — they are high-urgency blockers.
  • Propose the Eisenhower classification for tasks; {{NAME}} reviews.
  • Never skip one of the three data sources — missing one is a failure of this skill.
  • Show all tasks — every item from TASKS.md must appear, no silent filtering.

After the plan, offer a short next step ("want me to tackle #1?" / "should I draft a plan around the workshop?").

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.