Smart Email

Email assistant skill — check emails, AI summaries, daily digests. Supports Gmail, Outlook/M365, Google Workspace. Users interact through their chat platform...

What to consider before installing/using this skill: - The skill will ask you for mailbox access: OAuth tokens or app passwords. These are stored locally in data/email.db (plaintext). Do not install if you require encrypted-at-rest storage unless you add/enforce encryption yourself. - SKILL.md claims local encrypted storage, but the code does not encrypt secrets—this is a false claim. Treat stored passwords/tokens as plaintext on disk. - The skill sends email text to the configured AI API (ai_api_base). Only set ai_api_base to a trusted provider (and prefer keeping sensitive content off third-party services). If you must use external summarization, prefer a provider you control or one with appropriate privacy commitments. - Prefer OAuth (Outlook/M365) over app passwords when possible. Avoid pasting app passwords into public or untrusted chat channels; the skill’s UX sometimes expects the user to supply passwords via chat which can be insecure. - The web UI exposes an access token and accepts it via query parameter; run the web UI only bound to localhost and avoid port-forwarding to the public internet. Protect <SKILL_DIR>/data and config.json with strict filesystem permissions. - If you need strong assurances (encrypted storage, audited network endpoints), review/modify the code: implement encrypted credential storage, restrict ai_api_base to allowed hosts, and add logging/consent notices before sending email bodies externally. If you’re not comfortable auditing or modifying the code yourself, run the skill in an isolated environment (VM/container) or decline installation.

Type: OpenClaw Skill Name: smart-email Version: 1.2.0 The skill provides legitimate email management and AI summarization features, but it is classified as suspicious due to several security vulnerabilities and a discrepancy between documentation and implementation. Specifically, 'store.js' stores email passwords and OAuth tokens in plain text in a local SQLite database, contradicting the 'SKILL.md' claim of 'locally encrypted storage.' Furthermore, 'imap.js' allows disabling TLS certificate verification for custom servers, which exposes users to man-in-the-middle (MITM) attacks, and 'server.js' prints a sensitive web access token directly to the console. While no intentional malicious exfiltration was found, these flaws represent significant risks when handling sensitive communication data.