agentleFS
cgoinglovecgoinglove/thursday-agent/skills/daily-brief/SKILL.md

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

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.
  • QuixiAISkill

    weekly-review

    Review the past week across goals, tasks, calendar, journal, and commitments, then propose the next week

    Also in 5 projects that use this

  • AnthropicSkill

    onboarding

    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

  • VercelSkill

    setup

    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

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
  1. Very specific:

    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 …

    line 44

“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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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.mjs prints an id per story (a1, b3); story.mjs takes those ids; brief.json names 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.json and stories.json are 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.mjs writes it into text-<n>.md files that each fit one read, and prints the cat line 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.mjs did 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 story story.mjs prints as NO TEXT was refused by its publisher: drop it for one of your spares; with NO 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.mjs writes over it.
  • The browser opens itself where a step needs it. A Google News link does not hold the publisher's address, so story.mjs follows the chosen stories' links in this job's browser; --look renders 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.

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.