Sovereign Daily Digest

ReviewAudited by ClawScan on May 10, 2026.

Overview

This skill mostly does what it says, but its script can read local calendar files from common folders even when the user has not explicitly configured those calendar sources.

Before installing, review the helper script and configuration. If you use this skill, restrict calendar sources to ones you intentionally configure, check the output/archive directory, and only enable email or scheduled runs if you are comfortable with the access and retention involved.

Findings (4)

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.

Concern

ASI02: Tool Misuse and Exploitation

What this means

A digest could include events from local calendar files the user did not explicitly add to the digest configuration.

Why it was flagged

The script reads calendar files from common local directories automatically, even though the skill instructions describe using configured calendar sources. Local calendars can contain sensitive personal or work information.

Skill content

# Check for local .ics files in common locations
    for ics_path in ~/calendars/*.ics ~/.local/share/calendars/**/*.ics; do
        if [[ -f "$ics_path" ]]; then
            ...
            parse_ics "$(cat "$ics_path")" "$name"

Recommendation

Limit calendar reads to explicitly configured paths/URLs, or add a clear opt-in setting and user warning before scanning local calendar directories.

Note

ASI03: Identity and Privilege Abuse

What this means

If enabled, the skill can access sensitive email content for the digest.

Why it was flagged

Email access is optional and disabled by default, but if enabled it uses account credentials and reads unread message metadata/body snippets.

Skill content

email:
    enabled: false                 # disabled by default — requires auth
    provider: "imap"
    ...
    # Password should be stored in environment variable DIGEST_EMAIL_PASS
...
1. Connect via IMAP.
2. Fetch unread messages from the last N hours.

Recommendation

Enable email only intentionally, use an app-specific password or tightly scoped account, and avoid including mailboxes with highly sensitive content unless needed.

Note

ASI06: Memory and Context Poisoning

What this means

Sensitive personal information may remain in local digest archives for up to the configured retention period.

Why it was flagged

The skill stores generated briefings locally and archives them by default. Those briefings may summarize calendar, task, email, and other personal data.

Skill content

output_dir: "~/.openclaw/daily-digest/output"
  archive: true                    # keep previous digests
  max_archive_days: 30

Recommendation

Review the output directory permissions, reduce or disable archiving if needed, and avoid adding sources whose summaries should not be retained.

Note

ASI10: Rogue Agents

What this means

If the user installs the cron entry, the digest can run every day without a fresh interactive prompt.

Why it was flagged

The documentation shows how to configure recurring cron execution. This is user-directed and aligned with a daily digest, but it creates persistent scheduled behavior.

Skill content

0 7 * * * cd ~/.openclaw/skills/daily-digest && bash scripts/digest.sh --format both

Recommendation

Only add scheduled execution if desired, and review or remove the cron/Task Scheduler entry when no longer needed.