agentleFS
Sign inStart free
Works-HQWorks-HQ/ai-brain-starter-pack/skills/morning-sweep/SKILL.md

morning-sweep

Skill3 starsChanged 3 months agoMITView on GitHub

Build today's brief from current context, tasks, waiting-for items, and any connected calendar or inbox. Use first thing each morning. Triggers on "morning sweep", "what's important today", and "build my day".

The file

We split this skill into the rules it gives an agent

8 rules. About 0 are common, 5 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read what matters and return a one-screen plan for today.

    line 8
  2. Very specific:

    Company mode: use this when operating-system/ exists with operating-system/GLOBAL_TASKS.md.

    line 16
  3. Very specific:

    Personal mode: use this when root-level TASKS.md exists with a personal root or area CLAUDE.md.

    line 17
  4. Distinctive:

    Both detected: ask which mode to use. Write nothing until the user chooses.

    line 18
  5. Very specific:

    Read root TASKS.md and the current-state blocks in relevant CLAUDE.md files.

    line 25
  6. Distinctive:

    Read these top-level files when present:

    line 29
  7. Distinctive:

    If a calendar or inbox is connected and the user has allowed access, include today's meetings and replies.

    line 36
  8. Distinctive:

    Keep it to one screen. Never send a message, email, or post.

    line 51

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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

Morning Sweep

Read what matters and return a one-screen plan for today. The default is read-and-summarise with zero file writes.

Done when: the user has a one-screen brief covering today's shape, top 3, calendar, replies needed, overdue items, and parked work.

Detect the structure first

Inspect the current folder before reading or planning.

  1. Company mode: use this when operating-system/ exists with operating-system/GLOBAL_TASKS.md.
  2. Personal mode: use this when root-level TASKS.md exists with a personal root or area CLAUDE.md.
  3. Both detected: ask which mode to use. Write nothing until the user chooses.
  4. Neither detected: say that this folder does not contain a recognised personal or company structure. Point the user to START-HERE. Write nothing.

Read the available signals

Personal mode

Read root TASKS.md and the current-state blocks in relevant CLAUDE.md files. Use debrief-history.log only when recent history is needed to understand an open item.

Company mode

Read these top-level files when present:

  • operating-system/GLOBAL_TASKS.md
  • operating-system/WAITING_FOR.md
  • operating-system/current-context.md
  • operating-system/DECISIONS.md when a pending decision affects today

If a calendar or inbox is connected and the user has allowed access, include today's meetings and replies. If either source is unavailable, say so. Never claim to have read a source you could not access.

Build the brief

Choose the top three priorities based on due dates, work blocking other people, and work that moves the most important outcome. Respect anything the user explicitly parked.

Return:

  • Today's shape
  • Top 3
  • Calendar with preparation flags
  • Needs a reply today
  • Overdue to chase
  • Parked

Keep it to one screen. Never send a message, email, or post.

Write behavior

The default morning sweep writes nothing. Do not update tasks, context, or waiting-for files while summarising.

Only offer a persistent file if the user explicitly asks to save the sweep. In personal mode the target is root DAILY_SWEEP.md. In company mode the target is operating-system/DAILY_SWEEP.md. Show that one-file plan and wait for approval before writing. Overwrite only the previous daily sweep, never another file.

Scaling to per-project folders

Company mode deliberately reads the top-level operating system. If the volume later demands project folders, the sweep can read their task and waiting-for files too, but the final plan should still be one cross-company view.

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.

Check your setup, free