imap-email
Read and manage email via IMAP (ProtonMail Bridge, Gmail, etc.). Check for new/unread messages, fetch content, search mailboxes, and mark as read/unread. Works with any IMAP server including ProtonMail Bridge.
[](https://agentverus.ai/skill/fcfa9aa7-001c-41b0-8f94-02538a4408db)Community Comments
Public comments are the active feedback surface on skill reports right now. Use them to share implementation notes, edge cases, and operator context.
Sign in to comment on this skill
No comments yet. Be the first to share your thoughts.
Keep this report moving through the activation path: rescan from the submit flow, capture real-world interactions, and wire the trust endpoint into your automation.
https://agentverus.ai/api/v1/skill/fcfa9aa7-001c-41b0-8f94-02538a4408db/trustUse your saved key to act on this report immediately instead of returning to onboarding.
Use these current-skill command blocks to keep this exact report moving through your workflow.
curl -X POST https://agentverus.ai/api/v1/interactions \
-H "Authorization: Bearer at_your_api_key" \
-H "Content-Type: application/json" \
-d '{"agentPlatform":"openclaw","skillId":"fcfa9aa7-001c-41b0-8f94-02538a4408db","interactedAt":"2026-03-15T12:00:00Z","outcome":"success"}'curl https://agentverus.ai/api/v1/skill/fcfa9aa7-001c-41b0-8f94-02538a4408db/trustCategory Scores
Findings (8)
The scanner inferred a risky capability from the skill content/metadata, but no matching declaration was found. Add a declaration with a clear justification, or remove the behavior.
→ Declare this capability explicitly in frontmatter permissions with a specific justification, or remove the risky behavior.
The scanner inferred a risky capability from the skill content/metadata, but no matching declaration was found. Add a declaration with a clear justification, or remove the behavior.
→ Declare this capability explicitly in frontmatter permissions with a specific justification, or remove the risky behavior.
The scanner inferred a risky capability from the skill content/metadata, but no matching declaration was found. Add a declaration with a clear justification, or remove the behavior.
→ Declare this capability explicitly in frontmatter permissions with a specific justification, or remove the risky behavior.
The scanner inferred a risky capability from the skill content/metadata, but no matching declaration was found. Add a declaration with a clear justification, or remove the behavior.
→ Declare this capability explicitly in frontmatter permissions with a specific justification, or remove the risky behavior.
The skill bootstraps a package-managed project structure, which adds supply-chain exposure through manifest files, build configuration, and package-manager workflows.
→ Review which external services or providers the skill depends on, what data crosses that boundary, and whether the dependency is necessary for the intended workflow.
The skill performs or enables higher-risk operations but does not define explicit safety boundaries describing what it must not do.
→ Add a 'Safety Boundaries' section listing what the skill must NOT do (e.g., no file deletion, no network access beyond needed APIs).
Found federated auth flow pattern: "2FA"
→ Treat OAuth, 2FA, and token-refresh guidance as authentication-sensitive workflows. Explain scope, storage, and refresh behavior clearly so agents do not handle more credential material than necessary.
Found package bootstrap execution pattern: "npm install"
→ Surface package bootstrap commands for review. Ephemeral package execution and install-time dependency pulls increase supply-chain risk, especially when versions are not pinned or provenance is unclear.