morning-briefing
Skill0 starsChanged 3 months agoMITView on GitHub
Morning status report — active projects, yesterday's work, server health, what to do today. Use when the user says "briefing", "morning", "what's the status", "what should I do today".
18 other projects use a version of this.
Adopted by
Most recently taken up by
- krishagel/geoffreytheir own version, first seen Nov 15, 2026
- anotherben/claude-harnesstheir own version, first seen Nov 8, 2026
- Rneayan/airship-skillstheir own version, first seen Nov 4, 2026
- jjs04/dailypulsetheir own version, first seen Oct 15, 2026
- Johnwang688/jarvistheir own version, first seen Oct 13, 2026
- fivebarn/studiotheir own version, first seen Oct 11, 2026
Other versions18 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 18
- sonichi/sutando★ 396same name
- Hassaan146/claude-skills★ 18same name
- pbc-os/smb-starter-kit★ 10same name
- krishagel/geoffrey★ 9same name
- anotherben/claude-harness★ 7same name
- broomva/skills★ 4same name
- atomicpapa/claude-obsidian-setup★ 2same name
- Peter-Swain-Inc/psi-skills★ 2same name
- fabio-baumgartner/unternehmer-skills★ 1same name
- GopalGB/claude-code-toolkit★ 1same name
8 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository6 other files it gives its agents.
- templates/CLAUDE.mdCLAUDE.md
- deploySkill
- new-projectSkill
- server-checkSkill
- session-memorySkill
- telegram-sendSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 3 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 16 edited versions we read keep these.
3
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
- Distinctive: line 12
Run these in parallel:
- Distinctive: line 42
Call out slacking honestly — an empty yesterday gets named, not politely skipped
- Distinctive: line 43
Keep the whole briefing under 15 lines
“Common” is measured: kept by at least 6 in 10 of the 16 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.
Files
Morning Briefing
The Iron Man moment: you sit down, JARVIS tells you where everything stands.
Gather
Run these in parallel:
- Yesterday's work — for each active project in
~/.jarvis/projects.md:git -C ~/project log --oneline --since="yesterday 00:00" --author="$(git config user.email)" - Memory — read each project's
## Nextfrom~/.jarvis/memory/<project>.md(seesession-memoryskill) - Servers — quick pass of the
server-checkskill on production hosts (skip if no servers configured) - Staleness — projects with no commits and no session saves for 7+ days
Report Format
☀️ Briefing — <date>
Yesterday: <N commits across M projects — one line each, or "nothing. we don't talk about yesterday.">
Servers: 🟢 all up | 🔴 <problem first>
Today:
1. <most important Next across all projects — pick ONE>
2. <second>
Stale: <project> — <N> days untouched. Kill it or schedule it.Rules
- Problems first, always — a dead container outranks everything else
- Pick today's #1 for the user; don't hand them a menu of ten options
- Call out slacking honestly — an empty yesterday gets named, not politely skipped
- Keep the whole briefing under 15 lines
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
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.

