agentleFS
Sign inStart free
Jason-hub-starJason-hub-star/model-orchestrator/skills/morning-brief/SKILL.md

morning-brief

Skill0 starsChanged 2 months agoMITView on GitHub

Open a work session by checking the previous handoff, recent commits, uncommitted work, failed checks, and the single best next action. Use for “morning”, “start the day”, “what did I leave yesterday?”, “아침”, or “시작하자”.

25 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

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

  • 0

    Common

    Most of the 20 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Start from evidence left by the previous session.

    line 8
  2. Distinctive:

    Read the nearest project instructions and one current status or handoff document.

    line 12
  3. Distinctive:

    Do not automatically archive, delete, reset, or commit anything.

    line 26
  4. Very specific:

    If the desired outcome still needs comparison with the code, use aim-before-build.

    line 30

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

Morning Brief

Start from evidence left by the previous session. This is read-only unless the user separately asks to clean or archive files.

Workflow

  1. Read the nearest project instructions and one current status or handoff document.
  2. Inspect recent commits and working-tree changes without modifying them.
  3. Find the most recent recorded verification result. Missing evidence means unknown, not pass.
  4. Identify one blocker or red signal that could invalidate today’s work.
  5. Recommend exactly one next action.

Output

  • Previous result: last known completed outcome
  • Red signal: failed, missing, or stale evidence
  • Uncommitted work: concise status
  • Blocker: one, or none
  • Next action: exactly one

Do not automatically archive, delete, reset, or commit anything.

Next

If the desired outcome still needs comparison with the code, use aim-before-build.

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