The Signal — AI daily digest

The system is built from three cooperating pieces:

The task runs unattended. Because no user is present, Claude makes all editorial decisions itself and never pauses to ask questions. The prompt instructs it to:

1. 1

   Invoke the skill, research live

   Run the ai-daily-digest skill's full workflow — never from memory.
2. 2

   Scan the last ~24–36 hours

   Across Anthropic/Claude, OpenAI, Google DeepMind, Meta AI, Mistral, xAI, and notable others (DeepSeek, Microsoft, Nvidia…). Primary sources first; several focused searches, not one broad one.
3. 3

   Triage to a high bar

   One lead item, 2–4 more for deep treatment, an “On the radar” tail, and a “Worth reading” list. Cut rumor, restated news, and pure marketing.
4. 4

   Dedupe & increment

   Check the digest folder for the previous edition and build continuity instead of re-reporting; increment the edition number (start at No. 1 if none).
5. 5

   Assemble from the template

   Keep all CSS and the fixed masthead. Write analysis, not summary; add a “Builder's angle” only where there's a real implication; always cite real links.
6. 6

   Save

   As AI-Digest-YYYY-MM-DD.html in the Digests folder; create the folder if needed.
7. 7

   Decide autonomously

   No questions during a scheduled run.

The skill defines the editorial product. It triggers when the task fires, and on demand whenever the reader asks for any of:

Output at a glance

The daily workflow

1. 1

   Gather

   Search the web for developments since the previous edition, primary sources first:

   • Labs: Anthropic news & engineering, OpenAI, Google DeepMind & Google AI, Meta AI, Mistral, xAI, plus DeepSeek, Cohere, Microsoft, AWS AI, Apple, Nvidia when relevant.
   • Research: arXiv (cs.AI, cs.CL, cs.LG) for significant papers; HuggingFace trending for what's actually used.
   • Aggregators: for surfacing only — verify against primary sources before reporting.

   Run several focused searches (releases, pricing/API, agentic tooling, evals, safety/policy, funding, research), not one broad query.

2. 2

   Triage

   Include if it changes what a builder can do, shifts the landscape, or is a real capability step. Demote or cut rumor, restated news, pure marketing, and incremental bumps. Dedupe against yesterday — continuity, not re-reporting. Pick one lead, then 2–4 deep items; the rest go to “On the radar.”
3. 3

   Write — analysis, not summary

   Each deep item follows an internal shape (labels not printed): what happened (facts + primary link), why it matters (the real implication), the skeptical read (what's overstated). Voice: sharp, direct, opinionated, no filler, no emoji. A Builder's angle is added only where there's a concrete implication for building agentic products on Claude.
4. 4

   Assemble the HTML

   Fill the <!-- FILL --> regions, keeping all CSS and the fixed masthead. Structure: meta grid → state of play → the lead (index 01, viz only if there's a clean number) → deep items (Also Today) → On the radar (3–6) → Worth reading (1–3) → footer.
5. 5

   Save & report

   Save as AI-Digest-YYYY-MM-DD.html, then give a 2–3 sentence summary of the lead and how many items made the cut, with the file path.

Edge cases

The look is defined as CSS variables (oklch) at the top of assets/template.html:

• Run it now: ask for “today's digest” / “run my digest.”
• Output: AI-Digest-YYYY-MM-DD.html in the Digests folder, edition number incrementing daily.