agentleFS
DScardini91DScardini91/agentic-os/.claude/skills/morning-brief/SKILL.md

morning-brief

Skill2 starsChanged 5 months agoMITView on GitHub

Start the day — reads the brain, pulls calendar and email digest, and delivers a single prioritized briefing with a development nudge tied to today's actual agenda.

26 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use meeting-prep.

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.
  • OpenAISkill

    meeting-prep

    Use when creating Public Equity Investing meeting prep briefs. Do not use for private diligence, IB, FP&A, legal, or scheduling-only tasks.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 21 edited versions we read keep these.

  • 1

    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:

    If external connectors are unavailable, deliver the briefing from local memory only and note what is missing.

    line 55

“Common” is measured: kept by at least 6 in 10 of the 21 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

Skill: morning-brief

Purpose

One crisp briefing that replaces the "where do I even start?" moment at the top of the day.

Steps

  1. Read the brain silently
    • control-plane/memory/self/ — who the principal is, working style, protected time
    • control-plane/memory/tasks/backlog.md — task list and priorities
    • Last 2 control-plane/memory/daily/ logs — open threads, carried items
    • Active control-plane/memory/projects/ files referenced in recent logs
    • control-plane/memory/development/objectives.md — active development objectives
  2. Delegate in parallel
    • briefing-analyst — pull today's calendar + important email/inbox items. Pass brain context (active projects, key stakeholders). Note if external connectors are not authenticated and continue without.
    • work-advisor — ranked prioritization for today. Pass brain context + whatever briefing-analyst returns.
  3. Open today's daily log
    • Delegate to work-logger to create control-plane/memory/daily/YYYY-MM-DD.md from _template.md if it doesn't exist. Pull "Carried to tomorrow" from yesterday's log.
  4. Synthesize ONE briefing (structure below)

Output structure

Today's shape — key meetings, hard deadlines, energy map for the day

Top 3 priorities — each with a one-line "why this first"

Watch-outs — anything slipping, anyone waiting on the principal, sensitivities to manage

Development nudge — ONE concrete moment today that is a practice rep for an active development objective. Tie it to a real calendar event or task, never generic. If no objective exists, skip.

First move — the single thing to start with right now


Rules

  • The entire output is one response. No back-and-forth before delivering it.
  • Development nudge must be specific and observable. "Be more strategic" is not a nudge. "The 14:30 kickoff is your rep for 'drive the room' — open with your POV before opening the floor" is.
  • If external connectors are unavailable, deliver the briefing from local memory only and note what is missing.
  • Log the plan in today's daily log before closing.

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.