Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Set up and run a personal AI newsletter intelligence system called Briefed. Fetches Gmail newsletters daily, uses Claude Haiku to extract article summaries,...
Set up and run a personal AI newsletter intelligence system called Briefed. Fetches Gmail newsletters daily, uses Claude Haiku to extract article summaries,...
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Then review README.md for any prerequisites, environment setup, or post-install checks. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Then review README.md for any prerequisites, environment setup, or post-install checks. Summarize what changed and any follow-up checks I should run.
A daily newsletter digest pipeline + local web reader. Gmail โ Haiku summaries โ web app โ notification ping.
[Gmail] โ pre-fetch.py (fetches, filters, extracts compact metadata) [newsletter-inbox.json] โ Haiku cron agent (reads compact JSON, writes AI summaries) [newsletter-today.json] โ fetch-bodies.py (adds full HTML email bodies) [newsletter-today.json + bodies] โ Express web reader (default port 3001) [Notification ping โ user opens reader] Why split fetch/summarise? Raw Gmail API JSON overflows Haiku's context. Python handles data wrangling; Haiku handles cognition.
Gmail access is read-only (gmail.readonly). OAuth token is stored locally at ~/.openclaw/workspace/briefed-gmail-token.json (or BRIEFED_GMAIL_TOKEN_FILE). The workflow should only read/write the following workspace files: newsletter-inbox.json newsletter-today.json newsletter-interests.json newsletter-notes.json reading-list.md Do not send newsletter content to external endpoints other than the configured model provider and user-selected notification channel.
Python 3.9+ Python deps for Gmail API (google-api-python-client, google-auth, google-auth-oauthlib) A Google OAuth Desktop client JSON file (for Gmail read-only auth) Node.js โฅ18 (for the reader web app) claude-haiku-4-5 on the OpenClaw models allowlist A notification channel configured in OpenClaw (Telegram, Discord, etc.)
cd ~/.openclaw/workspace/briefed python3 -m pip install -r scripts/requirements.txt
Create a Google Cloud OAuth Desktop app and download the client JSON, then set: export BRIEFED_GMAIL_CLIENT_SECRET=~/client_secret.json On first script run, Briefed opens a browser OAuth flow and stores a reusable token at: ~/.openclaw/workspace/briefed-gmail-token.json
# Copy the reader to the workspace cp -r assets/reader/ ~/.openclaw/workspace/briefed/ cd ~/.openclaw/workspace/briefed npm install
Defaults (works for most users): Token file: ~/.openclaw/workspace/briefed-gmail-token.json Client secret: ~/client_secret.json Override via env vars if needed: export BRIEFED_GMAIL_CLIENT_SECRET=~/path/to/client_secret.json export BRIEFED_GMAIL_TOKEN_FILE=~/.openclaw/workspace/briefed-gmail-token.json
Create ~/.openclaw/workspace/newsletter-interests.json (or let it be auto-created on first run): { "version": 1, "topics": { "ai": 0.9, "startups": 0.8, "design": 0.75 }, "signals": [], "sources": {} }
Run manually if you prefer no persistence. LaunchAgent is optional convenience for auto-start. # Quick test node ~/.openclaw/workspace/briefed/server.js # Persistent โ create ~/Library/LaunchAgents/ai.openclaw.briefed.plist LaunchAgent plist template: <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> <plist version="1.0"><dict> <key>Label</key><string>ai.openclaw.briefed</string> <key>ProgramArguments</key><array> <string>/usr/local/bin/node</string> <string>/Users/YOUR_USER/.openclaw/workspace/briefed/server.js</string> </array> <key>EnvironmentVariables</key><dict> <key>BRIEFED_GMAIL_CLIENT_SECRET</key><string>/Users/YOUR_USER/client_secret.json</string> <key>BRIEFED_GMAIL_TOKEN_FILE</key><string>/Users/YOUR_USER/.openclaw/workspace/briefed-gmail-token.json</string> </dict> <key>RunAtLoad</key><true/> <key>KeepAlive</key><true/> <key>WorkingDirectory</key><string>/Users/YOUR_USER/.openclaw/workspace/briefed</string> <key>StandardOutPath</key><string>/tmp/briefed.log</string> <key>StandardErrorPath</key><string>/tmp/briefed.log</string> </dict></plist> launchctl load ~/Library/LaunchAgents/ai.openclaw.briefed.plist
Use the OpenClaw cron tool with this agent prompt (fill in the placeholders): Run my daily newsletter digest. Follow these steps exactly: ## Step 1 โ Pre-fetch emails Run: python3 ~/.openclaw/workspace/briefed/scripts/pre-fetch.py ## Step 2 โ Read the compact inbox Read: ~/.openclaw/workspace/newsletter-inbox.json ## Step 3 โ Write newsletter-today.json with AI summaries For each newsletter, write to **only** this file: ~/.openclaw/workspace/newsletter-today.json. Do not modify any other files in this step. Use the snippet field to write real summaries โ do NOT just repeat the subject line. Score by interest: (adjust topics and weights to match your interests) ai/ml=0.9, startups=0.85, design=0.8, finance=0.75, general=0.6 Schema per story: { "id", "rank", "source", "subject", "headline", "summary", "bullets": [], "threadId", "gmailUrl", "score", "body": "" } ## Step 4 โ Fetch HTML bodies Run: python3 ~/.openclaw/workspace/briefed/scripts/fetch-bodies.py ## Step 5 โ Send notification Send (via your configured channel): "๐ฌ Today's digest is ready โ <N> stories waiting.\nโ http://YOUR_HOST:3001" ## Step 6 โ Final reply ๐ฌ *Briefed โ [DD Mon YYYY]* ยท <N> stories *<rank>. <Source>* โ <Headline> <One sentence summary> (repeat for all stories) _Open the reader โ http://YOUR_HOST:3001_ Before enabling cron, run this once manually to complete OAuth in a browser: python3 ~/.openclaw/workspace/briefed/scripts/pre-fetch.py Cron schedule: 0 7 * * * (7am daily), model: anthropic/claude-haiku-4-5, delivery: announce.
All data files live in ~/.openclaw/workspace/: FilePurposenewsletter-inbox.jsonCompact pre-fetched email metadata (ephemeral)newsletter-today.jsonToday's stories with summaries + HTML bodiesnewsletter-interests.jsonTopic weights + vote/open signalsnewsletter-notes.jsonPer-story user notesreading-list.mdSaved/bookmarked stories
EndpointMethodPurpose/api/todayGETAll stories (bodies stripped)/api/story/:idGETSingle story with full HTML body/api/votePOST{ storyId, vote: "up"|"down"|"open" }/api/savePOST{ storyId } โ adds to reading-list.md/api/notePOST{ storyId, note }/api/notesGETAll notes
scripts/pre-fetch.py has two tunable lists near the top: SKIP_SUBJECT_PATTERNS โ subject substrings that flag an email as transactional SKIP_SENDERS โ sender names that are always transactional (e.g. banks, shops) Tune these when transactional emails slip through.
The reader shows "Briefed" with a blue "B" logo by default. To customise, edit public/index.html and public/icon.svg.
Workflow acceleration for inboxes, docs, calendars, planning, and execution loops.
Largest current source with strong distribution and engagement signals.