Daily Briefing Hub
PassAudited by ClawScan on May 10, 2026.
Overview
The skill is a coherent instruction-only daily briefing workflow, but it intentionally reads sensitive personal services and can remember settings, run on a schedule, and send summaries to chat apps.
Install this only if you are comfortable with the agent reading the connected accounts you choose for briefings. Use least-privilege account permissions, pick a private delivery channel, review any recurring cron setup, and periodically clear stored location, feed, or briefing preferences you no longer want kept.
Findings (5)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
If connected tools are available, the agent may read calendar events, unread email, tasks, and GitHub activity to prepare the briefing.
The skill is designed to access multiple private account-backed services. This is expected for a daily briefing, but it involves delegated access to sensitive personal and work data.
Google Calendar events, Gmail/Outlook email highlights, weather forecast, GitHub PR and CI status ... Todoist/ClickUp/Linear tasks
Connect only the accounts you intend to use, review service permissions, and prefer least-privilege scopes where available.
The briefing can trigger multiple local or connected tools during one request, which may query several services at once.
The skill orchestrates several tools and CLIs. That is central to its purpose, but users should know it may use whatever configured integrations are available.
Use the `gog` tool or Google Calendar CLI ... Use `curl` to fetch weather ... Use the GitHub CLI (`gh`) or GitHub skill
Make sure only trusted integrations are configured, and ask the agent to limit sources if you do not want a particular service included.
Private calendar, email, task, or GitHub highlights could appear in a third-party chat channel if delivery is enabled.
The skill may send the aggregated briefing to external messaging providers. This is disclosed and user-directed, but the briefing may contain sensitive account summaries.
delivered via Telegram, Slack, WhatsApp, or Discord
Choose a private destination, verify the recipient/channel before enabling delivery, and avoid sending sensitive briefings to shared workspaces unless intended.
Personal preferences or location may be retained and reused in later briefings.
The skill stores and reuses user preferences such as location, and elsewhere references memory/config for interests. This supports personalization but creates persistent context to review.
If user location is known (from memory or config), fetch automatically ... If not, ask once and remember for future briefings
Review or clear stored briefing preferences if they become outdated, sensitive, or no longer wanted.
After setup, the briefing may run automatically on the chosen schedule until disabled.
The skill can set up recurring briefings and persistent configuration, but the instructions tie this to an explicit user request for daily delivery.
Help them configure a cron job via OpenClaw's cron system ... Store the briefing configuration in the workspace for persistence
Confirm the schedule, delivery channel, and stored configuration, and disable the cron job when recurring briefings are no longer needed.