daily-brief
Skill1 starsChanged 3 months agoMITView on GitHub
Give the user a short spoken-style morning rundown — today's calendar, unread email worth attention, open to-dos, and the one thing that matters most. Use when the user says "brief me", "good morning", "what's on today", "catch me up", or "start my day".
30 other projects use a version of this.
Adopted by
Most recently taken up by
- hurleywgly/skillstheir own version, first seen Nov 8, 2026
- craigcossairt/trellistheir own version, first seen Nov 6, 2026
- bas1l/claude-skillstheir own version, first seen Nov 3, 2026
- geekfujiwara/copilot-cowork-skillstheir own version, first seen Nov 1, 2026
- HybridAIOne/hybridclawtheir own version, first seen Nov 1, 2026
- ofershap/mashov-parent-brieftheir own version, first seen Nov 1, 2026
Used with
Projects with it also use onboarding, setup and 1 more.
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.
AnthropicSkillonboarding
Generate an onboarding checklist and first-week plan for a new hire. Use when someone has a start date coming up, building the pre-start task list (accounts, equipment, buddy), scheduling Day 1 and Week 1, or setting 30/60/90-day goals for a new team member.
Also in 3 projects that use this
VercelSkillsetup
Set up Vercel CLI and project configuration. Use when the user says "set up Vercel", "configure Vercel", "link to Vercel", or "vercel init".
Also in 3 projects that use this
SentrySkillskill-creator
Create new agent skills following the Agent Skills specification. Use when asked to "create a skill", "add a new skill", "write a skill", "make a skill", "build a skill", or scaffold a new skill with SKILL.md. Guides through requirements, writing, registration, and verification.
Also in 3 projects that use this
Other versions30 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 30
- huytieu/COG-second-brain★ 1.3ksame name
- mariagorskikh/open-instinct★ 428same name
- leiting-eric/DailyBrief★ 384same name
- HybridAIOne/hybridclaw★ 159same name
- cgoinglove/thursday★ 56same name
- cgoinglove/thursday-agent★ 56same name
- systemind-team/AICOO-Skills★ 35same name
- seedprod/claude-code-telegram★ 20same name
- Unabyss/unabyss-skills★ 15same name
- rittmananalytics/wire-plugin★ 14same name
20 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 repository8 other files it gives its agents.
- draft-replySkill
- inbox-triageSkill
- lead-campaignSkill
- meal-plannerSkill
- quick-researchSkill
- subscription-auditSkill
- trip-plannerSkill
- weekly-reviewSkill
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 23 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 23
Keep the whole thing under ~120 words.
- Distinctive: line 46
Never invent an event, email, or task.
- Distinctive: line 47
Don't send anything, don't mark anything read, don't change the calendar.
“Common” is measured: kept by at least 6 in 10 of the 23 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
Daily Brief
Produce a tight, human morning rundown. The goal is orientation in ten seconds, not a data dump.
Gather (read-only)
Pull only what's available; skip sources that aren't connected.
- Calendar — today's events with times. Note the first one and any gaps.
- Inbox — unread or flagged mail from a real person (skip newsletters, receipts, and no-reply senders). Who, and what they want, in a few words.
- Tasks / notes — anything due today or explicitly marked for today.
Deliver
Lead with a single sentence that sets the shape of the day, then short sections. Keep the whole thing under ~120 words.
Good morning. Three things on today, two emails worth a look.
CALENDAR
09:30 Standup (15m)
14:00 Dentist
16:00 Call with Sam — first free slot before it is 11:00
NEEDS YOU
Priya — wants the invoice, replied twice
Landlord — lease renewal, no rush
TODAY
Ship the newsletter
Book flights before prices moveEnd with one line: the single highest-leverage thing to do first.
Rules
- Never invent an event, email, or task. If a source is empty, say so briefly.
- Don't send anything, don't mark anything read, don't change the calendar.
- Times in the user's timezone. If unknown, say the timezone you assumed.
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.