ClawHub

Email Management

v1.0.0

Triage inbox email, draft clear replies, and manage follow-ups with priority routing, commitment tracking, and reusable templates.

⭐ 3· 2k·17 current·17 all-time
byIván@ivangdavila
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
✓
Purpose & Capability
Name/description match the declared behavior. Required config path (~/email-management/) and the files/templates described are appropriate for a local email management workflow. No unrelated environment variables or binaries are requested.
ℹ
Instruction Scope
Runtime instructions are local and constrained: the agent expects email text supplied by the user or a separate mail-integration skill, creates/reads files under ~/email-management/, and will not send mail or collect credentials without explicit approval. Caveat: the skill instructs storing 'short observations' and other context in memory files — that can include sensitive email content if the user or an integration supplies it. The skill asks for explicit approval before writing the directory, which is appropriate.
✓
Install Mechanism
No install spec and no code files — instruction-only. No downloads, executables, or package installs are specified, which minimizes install-time risk.
✓
Credentials
The skill requests no credentials or environment variables and limits file access to a single local config path. This is proportionate to the stated purpose. The only requested persistent state is local files containing templates, memory, and tracking data.
✓
Persistence & Privilege
always:false (not force-included). The skill writes only to its own config path and does not modify other skills or system-wide settings. Autonomous model invocation is allowed (default) but not combined with elevated privileges or credential access.
Assessment
This skill appears coherent and local, but review and approve the initial setup before allowing it to create ~/email-management/. Do not paste full sensitive emails or credentials into chat — prefer connecting a trusted mail-integration skill if you need mailbox access. Verify that files stored in ~/email-management/ (memory.md, follow-ups.md, templates.md, vip-contacts.md) do not contain passwords or full payment details and keep that directory out of unencrypted cloud sync if it will store PII. Confirm any automation that would send messages or change mailbox rules before enabling it.

Like a lobster shell, security has layers — review code before you run it.

latestvk9726h75k1659p5bjjjd7am0qs820mk5

License

MIT-0
Free to use, modify, and redistribute. No attribution required.
Termshttps://spdx.org/licenses/MIT-0.html

Runtime requirements

📬 Clawdis
OSLinux · macOS · Windows
Config~/email-management/

Comments