Claude Skill MartBrowse skillsQuick linesLearn by videoTerminal guideWhat is a Skill?
← Back to list

Daily Brief Operations Skill

An operational cheat sheet that lets Claude run, regenerate, and debug the DailyBrief daily digest pipeline.

AutomationIntermediate★ 361⑂ 204AI score 8/10Last updated: Sep 26, 2026

What it does

  • Gives Claude the operational knowledge of the DailyBrief pipeline: RSS/API fetchers → pluggable LLM enrichment → single-page HTML digest.
  • Provides a command table with expected time and LLM cost (npm run daily, dry-run, render, regen-trading, regen-enrich <cat:sub>, quota-report) so logic is never re-implemented ad hoc.
  • Includes a "where to change what" file map: sources in sources.config.json, tab labels and caps in lib/output/render.ts, prompts in lib/ai/enrich.ts, scheduler in scripts/install.mjs.
  • Defines an ordered diagnostic flow: scheduler state (Windows Task Scheduler / launchd / cron) → logs/daily-*.log → logs/llm-calls.jsonl with errorCategory triage.
  • Captures institutional knowledge on recurring failures: Cloudflare WAF on LinuxDo, blank community tab selector bug, empty trading watchlist retry, non-English tweets slipping through.

Who it's for

  • Anyone self-hosting the DailyBrief repo to get an automated morning digest.
  • Operators of local-scheduler + LLM summarization pipelines who want Claude to own the incident routine.
  • Builders looking for a solid reference pattern for an "ops manual" style skill.

Example uses

  1. "Today's report never appeared" → Claude checks the scheduled task's last result, then tails the last 40 lines of today's local-date log to pinpoint the failure.
  2. "The finance tab is missing summaries" → run npm run quota-report, then top up with npm run regen-enrich finance:news instead of a full rerun.
  3. "Add a new RSS source and disable a flaky one" → edit only sources.config.json using enabled: false plus a notes field, then verify with npm run sources.

· · · Install guide · · ·

Try it now, no install

Paste this into Claude to use the skill without installing anything.

Read the instructions in this file and follow them to help me:
https://raw.githubusercontent.com/leiting-eric/DailyBrief/HEAD/.claude/skills/daily-brief/SKILL.md

What I want: (describe your task here)

If Claude can't open the link, open it yourself and paste the contents instead.

↓ If it works for you, download the ZIP below and install it. Then it runs on its own — no pasting each time.

Install in the Claude app (no terminal)
  1. Download the ZIP with the button below.
  2. In Claude, open Settings → Capabilities and turn on 'Code execution and file creation'. (one time)
  3. Go to Customize → Skills → + → 'Upload a skill' and upload the ZIP.
↓ Download ZIP
Install in Claude Code

Let Claude do it — paste this into Claude Code

Install the skill I found on Claude Skill Mart.
Copy the .claude/skills/daily-brief folder from the GitHub repo leiting-eric/DailyBrief into my ~/.claude/skills/daily-brief/.
When it's done, tell me in one line what this skill can do.

Install with a command instead

git clone https://github.com/leiting-eric/DailyBrief.git && cd DailyBrief && npm install && node scripts/install.mjs --global

⚠ This is a third-party skill. Check the source repository before installing.

  1. Make sure Node.js (18+ recommended) and git are installed.
  2. Clone the repo: git clone https://github.com/leiting-eric/DailyBrief.git
  3. Enter the project and install dependencies: cd DailyBrief && npm install
  4. The skill already ships at .claude/skills/daily-brief/, so opening Claude Code inside the project root picks it up automatically.
  5. To use it from anywhere, copy it globally: cp -r .claude/skills/daily-brief ~/.claude/skills/ (PowerShell: Copy-Item -Recurse .claude\skills\daily-brief $HOME\.claude\skills\).
  6. Create .env.local and set REPORT_TZ and LLM_BACKEND if needed (unset means the claude CLI backend).
  7. Run npm run dry-run first to verify fetching without spending LLM calls.
  8. Register the daily trigger with node scripts/install.mjs --global --at 08:00; remove it later with node scripts/uninstall.mjs.