daily-brief
Skill5 starsChanged 12 days agoMITView on GitHub
Start-of-day ranked brief - open issues, recent commits, work in progress, and anything waiting on a human decision. Use when asked for a 'daily brief', 'morning brief', 'what should I work on today', 'start my day', 'catch me up'.
31 other projects use a version of this.
Adopted by
Most recently taken up by
- Nowistay/claudetheir own version, first seen Nov 16, 2026
- bas1l/claude-skillstheir own version, first seen Nov 11, 2026
- hurleywgly/skillstheir own version, first seen Nov 8, 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 weekly-review, onboarding 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.
QuixiAISkillweekly-review
Review the past week across goals, tasks, calendar, journal, and commitments, then propose the next week
Also in 5 projects that use this
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
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 versions31 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 31
- huytieu/COG-second-brain★ 1.3ksame name
- mariagorskikh/open-instinct★ 428same name
- leiting-eric/DailyBrief★ 384same name
- HybridAIOne/hybridclaw★ 162same 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
21 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 repository48 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- .cursor/rules/project.mdcCursor rule
- bug-reportSkill
- build-verification-skillSkill
- daily-briefSkill
- grill-designSkill
- launch-checkSkill
- learnSkill
- pin-guardrailSkill
- prd-to-issuesSkill
- review-dependency-updatesSkill
- security-auditSkill
- setupSkill
- tddSkill
- trellis-surveySkill
- trellis-syncSkill
- worktreeSkill
- write-a-prdSkill
- build-verification-skillSkill
- grill-designSkill
- launch-checkSkill
- learnSkill
- pin-guardrailSkill
- prd-to-issuesSkill
- review-dependency-updatesSkill
- security-auditSkill
- setupSkill
- trellis-surveySkill
- trellis-syncSkill
- write-a-prdSkill
- bug-reportSkill
- build-verification-skillSkill
- daily-briefSkill
- grill-designSkill
- launch-checkSkill
- learnSkill
- pin-guardrailSkill
- prd-to-issuesSkill
- review-dependency-updatesSkill
- security-auditSkill
- setupSkill
- tddSkill
- trellis-surveySkill
- trellis-syncSkill
- worktreeSkill
- write-a-prdSkill
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 24 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 18
Optional signals: - IF other MCP servers are connected (email, analytics, error tracking), pull their top items.
- Distinctive: line 34
Keep the whole brief under ~30 lines:
- Distinctive: line 57
If the project has no tracker and no recent commits, say so and suggest the single most useful next step instead of inventing a board.
“Common” is measured: kept by at least 6 in 10 of the 24 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
You are producing the day's brief: a ranked answer to "what should I work on today?" grounded in the project's actual state, not vibes.
Gather (use what exists, skip what doesn't - never fail on a missing source)
- Git state - commits since yesterday (
git log --since=yesterday --oneline --all), current branch, uncommitted changes, unpushed commits, open PRs (gh pr list). - Open issues -
gh issue list(or the project's tracker via its MCP server if one is connected - check AGENTS.md for which tracker this project uses). - Project docs - the 5 newest entries in
docs/decision-log.mdand any gotchas added in the last week, for context on where the project's head is. - Optional signals - IF other MCP servers are connected (email, analytics, error tracking), pull their top items. Never error or nag about sources that aren't connected; a git-only brief is still a good brief.
Rank
Score candidate work by, in order:
- Unblocks something - work that other work (or a person) is waiting on
- Deadline proximity - anything dated
- Momentum - in-progress work close to done beats starting something new
- Quick wins - under-30-minute items worth batching
Flag separately anything that needs a HUMAN decision before an agent can act on it.
Output format
Keep the whole brief under ~30 lines:
# Daily Brief - {date}
## Recommended focus (top 3)
1. {item} - {one-line why it's ranked here}
2. ...
3. ...
## Needs your decision
- {item} - {what's blocked on the human} (omit section if empty)
## Also on the board
- {compressed list of remaining open items}
## Since yesterday
- {commits/PRs merged, one line each}Notes
- Be opinionated in the ranking - a brief that lists everything equally decides nothing.
- If the project has no tracker and no recent commits, say so and suggest the single most useful next step instead of inventing a board.
- This skill can be scheduled (e.g. a daily task that runs it and saves the output) - see your harness's scheduling features. Start by running it manually; schedule it once you trust it.
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.

