test
v1.0.0Expert AI agent specializing in email intelligence engineer. From The Agency (github.com/msitarzewski/agency-agents).
⭐ 0· 59·0 current·0 all-time
by@zhouqkt
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name/description match the provided instructions and example code (MIME/IMAP/Gmail/Microsoft Graph parsing, thread reconstruction, deduplication, context assembly). Nothing in the manifest asks for unrelated privileges or services.
Instruction Scope
SKILL.md and AGENTS.md contain concrete parsing and pipeline code examples (IMAP fetch, message parsing, deduplication, retrieval). They do not instruct reading arbitrary local files, exfiltrating data to unknown endpoints, or accessing other skills' configs. The instructions are focused on email processing and context assembly.
Install Mechanism
Instruction-only skill with no install spec and no code files to execute. Lowest-risk installation surface; nothing will be downloaded or written by an installer.
Credentials
The skill discusses integrations with Gmail API, Microsoft Graph, IMAP/SMTP etc., which in practice require API keys/credentials and storage of sensitive email data. The registry manifest requests no env vars or credentials — not unsafe by itself, but if you run the example code you will need to provide and protect those credentials (and ensure tenant isolation/PII handling).
Persistence & Privilege
always is false and the skill does not request persistent system-wide privileges or attempt to modify other skills or agent configs. Autonomous invocation is allowed (default) but not combined with other red flags.
Assessment
This skill appears internally consistent and focused on email processing. Before installing or running any example code: 1) Confirm the skill's source/trustworthiness (origin is listed as 'unknown' / GitHub project referenced in description). 2) Expect to supply email credentials (IMAP, Gmail/Microsoft Graph OAuth tokens) if you run pipelines — store them securely and grant minimal scopes. 3) Run code in a controlled environment and verify tenant/PII handling, logging, and retention behavior. 4) If you plan to grant the agent live email access, ensure monitoring/alerts and limit data exposure (test on non-production mailboxes first).Like a lobster shell, security has layers — review code before you run it.
latestvk9726njamh0tj212w1b3dcvben84nz3z
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
📧 Clawdis