# Send Briefed to your agent Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually. ## Fast path - Download the package from Yavira. - Extract it into a folder your agent can access. - Paste one of the prompts below and point your agent at the extracted folder. ## Suggested prompts ### New install ```text 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. ``` ### Upgrade existing ```text 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. ``` ## Machine-readable fields ```json { "schemaVersion": "1.0", "item": { "slug": "briefed", "name": "Briefed", "source": "tencent", "type": "skill", "category": "效率提升", "sourceUrl": "https://clawhub.ai/jamesnation/briefed", "canonicalUrl": "https://clawhub.ai/jamesnation/briefed", "targetPlatform": "OpenClaw" }, "install": { "downloadUrl": "/downloads/briefed", "sourceDownloadUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=briefed", "sourcePlatform": "tencent", "targetPlatform": "OpenClaw", "packageFormat": "ZIP package", "primaryDoc": "SKILL.md", "includedAssets": [ "README.md", "SKILL.md", "assets/reader/server.js", "assets/reader/package-lock.json", "assets/reader/package.json", "assets/reader/scripts/requirements.txt" ], "downloadMode": "redirect", "sourceHealth": { "source": "tencent", "slug": "briefed", "status": "healthy", "reason": "direct_download_ok", "recommendedAction": "download", "checkedAt": "2026-04-29T05:58:16.978Z", "expiresAt": "2026-05-06T05:58:16.978Z", "httpStatus": 200, "finalUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=briefed", "contentType": "application/zip", "probeMethod": "head", "details": { "probeUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=briefed", "contentDisposition": "attachment; filename=\"briefed-1.1.2.zip\"", "redirectLocation": null, "bodySnippet": null, "slug": "briefed" }, "scope": "item", "summary": "Item download looks usable.", "detail": "Yavira can redirect you to the upstream package for this item.", "primaryActionLabel": "Download for OpenClaw", "primaryActionHref": "/downloads/briefed" }, "validation": { "installChecklist": [ "Use the Yavira download entry.", "Review SKILL.md after the package is downloaded.", "Confirm the extracted package contains the expected setup assets." ], "postInstallChecks": [ "Confirm the extracted package includes the expected docs or setup files.", "Validate the skill or prompts are available in your target agent workspace.", "Capture any manual follow-up steps the agent could not complete." ] } }, "links": { "detailUrl": "https://openagent3.xyz/skills/briefed", "downloadUrl": "https://openagent3.xyz/downloads/briefed", "agentUrl": "https://openagent3.xyz/skills/briefed/agent", "manifestUrl": "https://openagent3.xyz/skills/briefed/agent.json", "briefUrl": "https://openagent3.xyz/skills/briefed/agent.md" } } ``` ## Documentation ### Briefed A daily newsletter digest pipeline + local web reader. Gmail → Haiku summaries → web app → notification ping. ### Architecture [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. ### Security & Scope 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. ### Prerequisites 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.) ### 1. Install Python dependencies cd ~/.openclaw/workspace/briefed python3 -m pip install -r scripts/requirements.txt ### 2. Configure Gmail OAuth 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 ### 3. Deploy the reader app # Copy the reader to the workspace cp -r assets/reader/ ~/.openclaw/workspace/briefed/ cd ~/.openclaw/workspace/briefed npm install ### 4. Configure Gmail token paths (optional) 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 ### 5. Configure interests 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": {} } ### 6. Start the reader 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: Labelai.openclaw.briefed ProgramArguments /usr/local/bin/node /Users/YOUR_USER/.openclaw/workspace/briefed/server.js EnvironmentVariables BRIEFED_GMAIL_CLIENT_SECRET/Users/YOUR_USER/client_secret.json BRIEFED_GMAIL_TOKEN_FILE/Users/YOUR_USER/.openclaw/workspace/briefed-gmail-token.json RunAtLoad KeepAlive WorkingDirectory/Users/YOUR_USER/.openclaw/workspace/briefed StandardOutPath/tmp/briefed.log StandardErrorPath/tmp/briefed.log launchctl load ~/Library/LaunchAgents/ai.openclaw.briefed.plist ### 7. Create the daily cron job 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 — stories waiting.\\n→ http://YOUR_HOST:3001" ## Step 6 — Final reply 📬 *Briefed — [DD Mon YYYY]* · stories *. * — (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. ### Data Files 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 ### Reader API 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 ### Filtering Transactional Email 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. ### Branding The reader shows "Briefed" with a blue "B" logo by default. To customise, edit public/index.html and public/icon.svg. ## Trust - Source: tencent - Verification: Indexed source record - Publisher: jamesnation - Version: 1.1.2 ## Source health - Status: healthy - Item download looks usable. - Yavira can redirect you to the upstream package for this item. - Health scope: item - Reason: direct_download_ok - Checked at: 2026-04-29T05:58:16.978Z - Expires at: 2026-05-06T05:58:16.978Z - Recommended action: Download for OpenClaw ## Links - [Detail page](https://openagent3.xyz/skills/briefed) - [Send to Agent page](https://openagent3.xyz/skills/briefed/agent) - [JSON manifest](https://openagent3.xyz/skills/briefed/agent.json) - [Markdown brief](https://openagent3.xyz/skills/briefed/agent.md) - [Download page](https://openagent3.xyz/downloads/briefed)