agentleFS
Sign inStart free
VeeiyVeeiy/vantage-os/skills/morning-brief/SKILL.md

morning-brief

Skill0 starsChanged 5 months agoMITView on GitHub

the operator's morning brief. Use when the operator says "morning brief", "good morning", "start my day", "what's on my plate", "daily briefing", or when a session starts before 11am. Pulls rental-fleet status from Tessie MCP, surfaces overnight events, lists today's top 3 priorities, and flags decisions waiting on him. Output is a tight dashboard, not a wall of text.

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:

    Surface conflicts: If yesterday's top 3 included an item that's not in any venture, call it out as orphan work.

    line 57
  2. Distinctive:

    If top-3 is stale (>24h), force a refresh: before showing the brief. Ask "yesterday's top 3 weren't checked off.

    line 58
  3. Distinctive:

    Tier check: If permissions are Tier 2 or 3, list any auto-actions that happened overnight at the top of the brief.

    line 59
  4. Very specific:

    If top-3.md has not been updated for today, generate a proposed top 3 based on:

    line 65

“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

Produce the operator's morning brief. Tight, scannable, actionable. He has ADHD and gets off a demanding full-time job at 8:30am Tue-Sat. Respect that.

Read first

  1. ~/Vault/Vantage-OS/ventures.md - venture statuses
  2. ~/Vault/Vantage-OS/decisions.md - pending decisions
  3. ~/Vault/Vantage-OS/top-3.md - yesterday's top 3 and whether they shipped
  4. ~/Vault/Vantage-OS/experiments.md - active experiments
  5. ~/Vault/Vantage-OS/hair-product-state.md - hair venture state
  6. Tessie MCP fleet-overview if available - rental-fleet status

Output structure

Render in this exact order. Keep each section under 6 lines unless content requires more.

# Morning Brief - [DATE]

## Fleet (rental-fleet)
- [Vehicle 1]: [status, location, battery, current renter if any]
- [Vehicle 2]: ...
- [Flag any issues: low battery, overdue return, mileage overage]

## Yesterday
- [What shipped]
- [What slipped]

## Today's Top 3
1. [Priority 1 - venture - estimated time]
2. [Priority 2 - venture - estimated time]
3. [Priority 3 - venture - estimated time]

## Decisions waiting on you (with deadlines)
- [Decision 1] - due [date] - [days remaining]
- [Decision 2] - due [date] - [days remaining]

## Hair product status
- Phase: [validation / sourcing / branding / launch / scale]
- Next action: [single concrete step]
- the partner's last input: [date, summary]

## Watch items
- [Trading levels, earnings tomorrow, anything market-related the operator needs to track]
- [a partner's milestones if relevant]

Rules

  1. No fluff. No "good morning the operator, hope you slept well." Get to the data.
  2. Surface conflicts. If yesterday's top 3 included an item that's not in any venture, call it out as orphan work.
  3. If top-3 is stale (>24h), force a refresh before showing the brief. Ask "yesterday's top 3 weren't checked off. Update before I render?"
  4. Tier check. If permissions are Tier 2 or 3, list any auto-actions that happened overnight at the top of the brief.
  5. If today is Sunday, surface protected personal time as the top item and ask if the operator really wants a work brief.
  6. If Tessie data is unavailable, say so explicitly. Do not invent fleet status.

Generate today's top 3 if not set

If top-3.md has not been updated for today, generate a proposed top 3 based on:

  • Decisions with imminent deadlines (highest priority)
  • Hair product next action
  • Stalled ventures from ventures.md (>5 days no movement)
  • Active experiments needing measurement

Propose them, ask the operator to confirm or edit, then write to top-3.md with today's date.

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