{ "schemaVersion": "1.0", "item": { "slug": "daily-briefing-hub", "name": "Daily Briefing Hub", "source": "tencent", "type": "skill", "category": "效率提升", "sourceUrl": "https://clawhub.ai/ariktulcha/daily-briefing-hub", "canonicalUrl": "https://clawhub.ai/ariktulcha/daily-briefing-hub", "targetPlatform": "OpenClaw" }, "install": { "downloadMode": "redirect", "downloadUrl": "/downloads/daily-briefing-hub", "sourceDownloadUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=daily-briefing-hub", "sourcePlatform": "tencent", "targetPlatform": "OpenClaw", "installMethod": "Manual import", "extraction": "Extract archive", "prerequisites": [ "OpenClaw" ], "packageFormat": "ZIP package", "includedAssets": [ "SKILL.md" ], "primaryDoc": "SKILL.md", "quickSetup": [ "Download the package from Yavira.", "Extract the archive and review SKILL.md first.", "Import or place the package into your OpenClaw setup." ], "agentAssist": { "summary": "Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.", "steps": [ "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." ], "prompts": [ { "label": "New install", "body": "I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete." }, { "label": "Upgrade existing", "body": "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. Summarize what changed and any follow-up checks I should run." } ] }, "sourceHealth": { "source": "tencent", "status": "healthy", "reason": "direct_download_ok", "recommendedAction": "download", "checkedAt": "2026-04-23T16:43:11.935Z", "expiresAt": "2026-04-30T16:43:11.935Z", "httpStatus": 200, "finalUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=4claw-imageboard", "contentType": "application/zip", "probeMethod": "head", "details": { "probeUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=4claw-imageboard", "contentDisposition": "attachment; filename=\"4claw-imageboard-1.0.1.zip\"", "redirectLocation": null, "bodySnippet": null }, "scope": "source", "summary": "Source download looks usable.", "detail": "Yavira can redirect you to the upstream package for this source.", "primaryActionLabel": "Download for OpenClaw", "primaryActionHref": "/downloads/daily-briefing-hub" }, "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." ] }, "downloadPageUrl": "https://openagent3.xyz/downloads/daily-briefing-hub", "agentPageUrl": "https://openagent3.xyz/skills/daily-briefing-hub/agent", "manifestUrl": "https://openagent3.xyz/skills/daily-briefing-hub/agent.json", "briefUrl": "https://openagent3.xyz/skills/daily-briefing-hub/agent.md" }, "agentAssist": { "summary": "Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.", "steps": [ "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." ], "prompts": [ { "label": "New install", "body": "I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete." }, { "label": "Upgrade existing", "body": "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. Summarize what changed and any follow-up checks I should run." } ] }, "documentation": { "source": "clawhub", "primaryDoc": "SKILL.md", "sections": [ { "title": "Daily Briefing Hub", "body": "Your AI Chief of Staff. This skill pulls data from multiple sources and generates a single, prioritized daily briefing — delivered however the user wants it." }, { "title": "Why This Exists", "body": "Most OpenClaw users end up building their own morning briefing by manually calling 5-8 separate tools. This skill does it in one step: gather everything, prioritize it, format it beautifully, and deliver it." }, { "title": "How It Works", "body": "When triggered, gather data from whichever sources the user has available, then compose a structured briefing. Not every source needs to be configured — the skill gracefully skips unavailable sources and works with whatever is connected." }, { "title": "Data Sources", "body": "Attempt to pull from these sources in order. If a source is unavailable (tool not enabled, API not configured), skip it silently and move on. Never fail because one source is missing." }, { "title": "1. Calendar (High Priority)", "body": "Use the gog tool or Google Calendar CLI to fetch today's events.\n\nShow: event name, time, location, attendees (if available)\nFlag conflicts (overlapping events)\nNote gaps longer than 2 hours as \"focus time\" opportunities\nIf tomorrow's first event is early, mention it as a heads-up" }, { "title": "2. Email (High Priority)", "body": "Use Gmail via gog or the configured email tool to scan recent unread messages.\n\nSummarize the top 5-10 most important unread emails (skip newsletters, promotions)\nPrioritize: emails from known contacts > emails with urgent keywords > everything else\nFor each: sender, subject, one-line summary, suggested action (reply/read/archive)\nCount total unread and note if inbox is getting out of control (>50 unread = flag it)" }, { "title": "3. Weather (Medium Priority)", "body": "Use curl to fetch weather from a public API, or use an installed weather skill.\n\nIf user location is known (from memory or config), fetch automatically\nIf not, ask once and remember for future briefings\nShow: current temp, high/low, conditions, rain probability\nOnly mention weather if it's notable (rain, extreme temps, storms) — skip \"sunny and 72°F\"\nSuggest: \"bring an umbrella\" or \"dress warm\" when relevant" }, { "title": "4. GitHub / Dev Activity (Medium Priority — skip for non-developers)", "body": "Use the GitHub CLI (gh) or GitHub skill to check activity.\n\nOpen PRs awaiting your review (with age: \"PR #142 waiting 3 days\")\nPRs you authored that have new reviews or comments\nCI/CD failures on your repos in the last 24 hours\nNew issues assigned to you\nSkip this section entirely if the user doesn't have GitHub configured" }, { "title": "5. Tasks (Medium Priority)", "body": "Check configured task managers: Todoist, ClickUp, Linear, GitHub Issues, or local task files.\n\nShow tasks due today and overdue tasks\nGroup by project/label if available\nFlag overdue items prominently" }, { "title": "6. News & Feeds (Low Priority)", "body": "Use web_search or RSS feeds to pull relevant headlines.\n\nIf the user has specified interests (in memory or config), filter for those topics\nDefault: top 3-5 tech/business headlines from the last 24 hours\nKeep summaries to one sentence each\nHacker News top 3 stories (if user is a developer)" }, { "title": "Briefing Format", "body": "ALWAYS structure the briefing like this. Adapt sections based on available data:\n\n☀️ Good [morning/afternoon], [Name]! Here's your briefing for [Day, Date].\n\n📅 TODAY'S SCHEDULE\n[Calendar events in chronological order]\n[Flag any conflicts or notable gaps]\n\n📧 EMAIL HIGHLIGHTS\n[Top priority emails with one-line summaries]\n[Total unread count]\n\n⚡ ACTION ITEMS\n[Overdue tasks — URGENT]\n[Tasks due today]\n[PRs needing your review]\n\n🌤️ WEATHER\n[Only if notable — rain, extreme temps, etc.]\n\n💻 DEV ACTIVITY\n[CI failures, new issues, PR updates]\n\n📰 NEWS\n[3-5 relevant headlines, one line each]\n\n---\nHave a great day! Reply with any item number to dive deeper." }, { "title": "Prioritization Logic", "body": "The briefing should feel like a smart assistant, not a data dump. Apply these rules:\n\nUrgent items surface first: overdue tasks, meeting in <1 hour, CI failures, emails from boss/clients\nCombine related items: if there's a meeting about a PR, mention them together\nBe concise by default: one line per item. The user can ask to expand any section\nSkip empty sections: don't show \"No new emails\" — just omit the section\nTime-aware: morning briefings focus on today. Evening briefings (\"what did I miss\") focus on what happened today" }, { "title": "Setting Up Recurring Briefings", "body": "If the user asks to \"send me a briefing every morning\" or \"set up a daily digest\":\n\nHelp them configure a cron job via OpenClaw's cron system\nSuggested schedule: weekdays at 7:00 AM local time (ask user preference)\nDeliver via their preferred channel (Telegram, Slack, WhatsApp, Discord)\nStore the briefing configuration in the workspace for persistence\n\nExample cron setup:\n\n{\n \"schedule\": \"0 7 * * 1-5\",\n \"prompt\": \"Generate my daily briefing and send it to me\",\n \"channel\": \"telegram\"\n}" }, { "title": "Customization", "body": "The user can customize their briefing at any time:\n\n\"Add RSS feeds to my briefing\" → ask for feed URLs, store in memory\n\"Skip weather in my briefings\" → remember this preference\n\"I want briefings at 6 AM\" → update cron schedule\n\"Focus on GitHub and email only\" → disable other sections\n\"Add Stripe revenue to my briefing\" → extend with financial data source\n\nStore all preferences in OpenClaw's memory system so they persist across sessions." }, { "title": "Edge Cases", "body": "First run: If this is the first briefing, explain what you're doing and ask about preferences rather than generating a sparse briefing with no data\nWeekend briefings: lighter tone, skip work email/GitHub, focus on personal calendar and weather\nEvening trigger: if user asks for briefing after 5 PM, shift to \"end of day recap\" — what happened today, what's tomorrow\nNo data at all: if literally no tools are configured, help the user set up at least calendar + email before generating a briefing\nMultiple calendars: if user has personal + work calendars, show both but label them clearly" }, { "title": "Example Interactions", "body": "User: \"Brief me\"\n→ Generate full briefing with all available sources\n\nUser: \"What's on my plate today?\"\n→ Focus on calendar + tasks, lighter on news\n\nUser: \"Set up a daily morning briefing on Telegram at 7 AM\"\n→ Configure cron job, confirm channel, generate a test briefing\n\nUser: \"What did I miss today?\"\n→ Evening recap: summarize the day's emails, completed tasks, GitHub activity\n\nUser: \"Add Hacker News to my daily briefing\"\n→ Store preference, confirm, show preview of how it'll look" } ], "body": "Daily Briefing Hub\n\nYour AI Chief of Staff. This skill pulls data from multiple sources and generates a single, prioritized daily briefing — delivered however the user wants it.\n\nWhy This Exists\n\nMost OpenClaw users end up building their own morning briefing by manually calling 5-8 separate tools. This skill does it in one step: gather everything, prioritize it, format it beautifully, and deliver it.\n\nHow It Works\n\nWhen triggered, gather data from whichever sources the user has available, then compose a structured briefing. Not every source needs to be configured — the skill gracefully skips unavailable sources and works with whatever is connected.\n\nData Sources\n\nAttempt to pull from these sources in order. If a source is unavailable (tool not enabled, API not configured), skip it silently and move on. Never fail because one source is missing.\n\n1. Calendar (High Priority)\n\nUse the gog tool or Google Calendar CLI to fetch today's events.\n\nShow: event name, time, location, attendees (if available)\nFlag conflicts (overlapping events)\nNote gaps longer than 2 hours as \"focus time\" opportunities\nIf tomorrow's first event is early, mention it as a heads-up\n2. Email (High Priority)\n\nUse Gmail via gog or the configured email tool to scan recent unread messages.\n\nSummarize the top 5-10 most important unread emails (skip newsletters, promotions)\nPrioritize: emails from known contacts > emails with urgent keywords > everything else\nFor each: sender, subject, one-line summary, suggested action (reply/read/archive)\nCount total unread and note if inbox is getting out of control (>50 unread = flag it)\n3. Weather (Medium Priority)\n\nUse curl to fetch weather from a public API, or use an installed weather skill.\n\nIf user location is known (from memory or config), fetch automatically\nIf not, ask once and remember for future briefings\nShow: current temp, high/low, conditions, rain probability\nOnly mention weather if it's notable (rain, extreme temps, storms) — skip \"sunny and 72°F\"\nSuggest: \"bring an umbrella\" or \"dress warm\" when relevant\n4. GitHub / Dev Activity (Medium Priority — skip for non-developers)\n\nUse the GitHub CLI (gh) or GitHub skill to check activity.\n\nOpen PRs awaiting your review (with age: \"PR #142 waiting 3 days\")\nPRs you authored that have new reviews or comments\nCI/CD failures on your repos in the last 24 hours\nNew issues assigned to you\nSkip this section entirely if the user doesn't have GitHub configured\n5. Tasks (Medium Priority)\n\nCheck configured task managers: Todoist, ClickUp, Linear, GitHub Issues, or local task files.\n\nShow tasks due today and overdue tasks\nGroup by project/label if available\nFlag overdue items prominently\n6. News & Feeds (Low Priority)\n\nUse web_search or RSS feeds to pull relevant headlines.\n\nIf the user has specified interests (in memory or config), filter for those topics\nDefault: top 3-5 tech/business headlines from the last 24 hours\nKeep summaries to one sentence each\nHacker News top 3 stories (if user is a developer)\nBriefing Format\n\nALWAYS structure the briefing like this. Adapt sections based on available data:\n\n☀️ Good [morning/afternoon], [Name]! Here's your briefing for [Day, Date].\n\n📅 TODAY'S SCHEDULE\n[Calendar events in chronological order]\n[Flag any conflicts or notable gaps]\n\n📧 EMAIL HIGHLIGHTS\n[Top priority emails with one-line summaries]\n[Total unread count]\n\n⚡ ACTION ITEMS\n[Overdue tasks — URGENT]\n[Tasks due today]\n[PRs needing your review]\n\n🌤️ WEATHER\n[Only if notable — rain, extreme temps, etc.]\n\n💻 DEV ACTIVITY\n[CI failures, new issues, PR updates]\n\n📰 NEWS\n[3-5 relevant headlines, one line each]\n\n---\nHave a great day! Reply with any item number to dive deeper.\n\nPrioritization Logic\n\nThe briefing should feel like a smart assistant, not a data dump. Apply these rules:\n\nUrgent items surface first: overdue tasks, meeting in <1 hour, CI failures, emails from boss/clients\nCombine related items: if there's a meeting about a PR, mention them together\nBe concise by default: one line per item. The user can ask to expand any section\nSkip empty sections: don't show \"No new emails\" — just omit the section\nTime-aware: morning briefings focus on today. Evening briefings (\"what did I miss\") focus on what happened today\nSetting Up Recurring Briefings\n\nIf the user asks to \"send me a briefing every morning\" or \"set up a daily digest\":\n\nHelp them configure a cron job via OpenClaw's cron system\nSuggested schedule: weekdays at 7:00 AM local time (ask user preference)\nDeliver via their preferred channel (Telegram, Slack, WhatsApp, Discord)\nStore the briefing configuration in the workspace for persistence\n\nExample cron setup:\n\n{\n \"schedule\": \"0 7 * * 1-5\",\n \"prompt\": \"Generate my daily briefing and send it to me\",\n \"channel\": \"telegram\"\n}\n\nCustomization\n\nThe user can customize their briefing at any time:\n\n\"Add RSS feeds to my briefing\" → ask for feed URLs, store in memory\n\"Skip weather in my briefings\" → remember this preference\n\"I want briefings at 6 AM\" → update cron schedule\n\"Focus on GitHub and email only\" → disable other sections\n\"Add Stripe revenue to my briefing\" → extend with financial data source\n\nStore all preferences in OpenClaw's memory system so they persist across sessions.\n\nEdge Cases\nFirst run: If this is the first briefing, explain what you're doing and ask about preferences rather than generating a sparse briefing with no data\nWeekend briefings: lighter tone, skip work email/GitHub, focus on personal calendar and weather\nEvening trigger: if user asks for briefing after 5 PM, shift to \"end of day recap\" — what happened today, what's tomorrow\nNo data at all: if literally no tools are configured, help the user set up at least calendar + email before generating a briefing\nMultiple calendars: if user has personal + work calendars, show both but label them clearly\nExample Interactions\n\nUser: \"Brief me\" → Generate full briefing with all available sources\n\nUser: \"What's on my plate today?\" → Focus on calendar + tasks, lighter on news\n\nUser: \"Set up a daily morning briefing on Telegram at 7 AM\" → Configure cron job, confirm channel, generate a test briefing\n\nUser: \"What did I miss today?\" → Evening recap: summarize the day's emails, completed tasks, GitHub activity\n\nUser: \"Add Hacker News to my daily briefing\" → Store preference, confirm, show preview of how it'll look" }, "trust": { "sourceLabel": "tencent", "provenanceUrl": "https://clawhub.ai/ariktulcha/daily-briefing-hub", "publisherUrl": "https://clawhub.ai/ariktulcha/daily-briefing-hub", "owner": "ariktulcha", "version": "1.0.0", "license": null, "verificationStatus": "Indexed source record" }, "links": { "detailUrl": "https://openagent3.xyz/skills/daily-briefing-hub", "downloadUrl": "https://openagent3.xyz/downloads/daily-briefing-hub", "agentUrl": "https://openagent3.xyz/skills/daily-briefing-hub/agent", "manifestUrl": "https://openagent3.xyz/skills/daily-briefing-hub/agent.json", "briefUrl": "https://openagent3.xyz/skills/daily-briefing-hub/agent.md" } }