Email Management
PassAudited by ClawScan on May 1, 2026.
Overview
This appears to be a coherent, local-first email triage skill with explicit approval boundaries, though it keeps local email-related memory.
This skill looks reasonable for local email triage and drafting. Before installing, be comfortable with persistent files under ~/email-management/, avoid placing passwords or full sensitive emails in memory, and only approve sends, forwarding, mailbox changes, or recurring reminders after reviewing the exact action.
Findings (3)
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.
Your assistant may keep a local record of email priorities, contacts, commitments, and summaries for reuse in later sessions.
The skill stores persistent local email-management context, including follow-ups, VIP contacts, and digests, which can influence future inbox decisions and may contain sensitive metadata.
Memory lives in `~/email-management/` ... `follow-ups.md` ... `vip-contacts.md` ... `digests/`
Use the local memory only for durable preferences and commitments, avoid storing secrets or raw email dumps, and periodically review or clear ~/email-management/.
If paired with a mail integration, approving these actions could send messages, forward mail, alter mailbox behavior, or create recurring notifications.
These are high-impact email or account actions, but the artifact explicitly gates them behind user approval.
Requires Explicit Approval: Sending any message to external recipients; Auto-forwarding messages; Changing external mailbox rules; Enabling recurring reminders or scheduled digests.
Review the exact recipients, content, rules, and schedule before approving any send, forward, mailbox-rule, or recurring-reminder action.
Installing or initializing the skill may create local files that persist email workflow context.
The setup instructions include shell commands that create and permission local files, but they are scoped to the skill directory and require explicit approval.
ask for explicit approval before writing files: mkdir -p ~/email-management/digests ... chmod 700 ~/email-management
Approve the setup commands only if you are comfortable creating the ~/email-management/ directory and storing local email-management state there.