daily-brief
Skill56 starsChanged 48 days agoMITView on GitHub
Builds the daily news brief: today's stories, weather and markets on one phone-first page. Use it when the user asks for their brief, or a routine opens one.
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 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
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
Other versions30 projects use a version of this.
Word for word · 1
- cgoinglove/thursday★ 56100% same
Edited · 0
None found.
Wrote their own version · 29
- huytieu/COG-second-brain★ 1.3ksame name
- mariagorskikh/open-instinct★ 428same name
- leiting-eric/DailyBrief★ 384same name
- HybridAIOne/hybridclaw★ 159same name
- systemind-team/AICOO-Skills★ 35same name
- seedprod/claude-code-telegram★ 20same name
- Unabyss/unabyss-skills★ 15same name
- rittmananalytics/wire-plugin★ 14same name
- geekfujiwara/copilot-cowork-skills★ 13same name
- Distilla-AI/distilla-skills★ 9same name
19 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 repository12 other files it gives its agents.
- AGENTS.mdAGENTS.md
- agent-browserSkill
- ai-sdkSkill
- marketingSkill
- shadcnSkill
- artifactSkill
- browserSkill
- computerSkill
- data-reportSkill
- find-skillsSkill
- media-digestSkill
- skill-creatorSkill
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 22 edited versions we read keep these.
0
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
- Very specific: line 44
A brief is remade, not added to: Run the whole thing again the same day and today's own page does not count as already told, so the same …
“Common” is measured: kept by at least 6 in 10 of the 22 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
Four scripts do everything but choosing and writing. They sit in this skill's scripts/ folder and
node runs them; nothing to install, no key. <scratch> is this job's own folder under scratch/:
write it out in full, and set S= again in every bash call — each call is a new shell.
S=<this skill's folder>/scripts
# Gather, one call: every topic as "<label>=<query>", in the edition the user reads, with the
# glance beside it when they want one
node $S/news.mjs "AI=AI OR OpenAI OR Anthropic" "Startups=startup funding" \
--lang en --country US --hours 30 --out <scratch>/cand.json [--avoid a.com] [--prefer b.com]
node $S/glance.mjs --weather "<their city>" \
--markets "S&P 500:SP500,EUR/USD,Bitcoin:CBBTCUSD" --out <scratch>/glance.json
# Read, one call: the stories you chose, from their publishers, photos saved
node $S/story.mjs <scratch>/cand.json a1 a4 b2 c1 c3 --out <scratch>/stories
# Their words, one call a file: story.mjs prints the `cat` line for each
cat <scratch>/stories/text-1.md
# Lay out, one call: after you have written <scratch>/brief.json yourself
node $S/page.mjs <scratch>/brief.json --look <scratch>/look
# A PDF beside it, only when they ask for one: a brief sent to their phone goes with its PDF
node $THURSDAY_SKILLS/artifact/scripts/document.mjs pdf <the page's path>- The ids are all you pass between steps.
news.mjsprints an id per story (a1,b3);story.mjstakes those ids;brief.jsonnames the same ids. A url, a photo path or a number is never typed: the page takes them from the scripts' files. - What the scripts print is what you read — except the stories' own words.
cand.jsonandstories.jsonare for the next script; opening one costs tens of thousands of tokens and says nothing the printout does not. The articles' text is the one thing too long to print:story.mjswrites it intotext-<n>.mdfiles that each fit one read, and prints thecatline for each. Those files are the only source for a summary. Choose by reading the list yourself — never with a script that scores it. - A story
news.mjsdid not print is not in the brief. The very article a brief of the last four days carried is left out before you see it; the same news in another article is yours to judge, against the headlines those briefs told, printed under the list. A storystory.mjsprints asNO TEXTwas refused by its publisher: drop it for one of your spares; withNO PICTURE, keep it or swap it. - A brief is remade, not added to. Run the whole thing again the same day and today's own page
does not count as already told, so the same stories come up again and
page.mjswrites over it. - The browser opens itself where a step needs it. A Google News link does not hold the
publisher's address, so
story.mjsfollows the chosen stories' links in this job's browser;--lookrenders the page in a headless one of its own. Nothing else here needs one.
references/brief.md is the format: what brief.json holds, how to choose, how to write a
summary and the spoken version. references/preferences.md is what to keep about the user and
the one question a first brief asks.
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.

