zipbox-email

Read, organize, and send sandbox email through the tribes-email CLI.

1|Updated Jun 17, 2026
One-click install
npx skills add https://github.com/tribes-protocol/trading-harness --skill zipbox-email-tribes-protocol
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: zipbox-email
Source: https://github.com/tribes-protocol/trading-harness/tree/main/skills/zipbox-email
Command: npx skills add https://github.com/tribes-protocol/trading-harness --skill zipbox-email-tribes-protocol

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Agents running in a sandbox need a safe, controlled way to read and send email without exposing mailbox passwords, IMAP/SMTP credentials, or MXroute API access. This Skill provides a single CLI surface for all mailbox operations while treating inbound mail as untrusted input to prevent prompt injection. ## Core Features & Use Cases - Mailbox management: Check status, list folders and messages, read, mark read/unread, move, delete, and flag spam using UIDVALIDITY-safe operations. - Sending email: Send HTML (default for structured content), plain text, or multipart/alternative messages with CC recipients and file attachments via the agent-scoped control-plane API. - Security guardrails: Treats every inbound message as hostile input, forbids quoting inbound content into outbound mail, and blocks direct MXroute/IMAP/SMTP access. - Use Case: An autonomous agent checks its sandbox inbox for a verification code, reads the message safely, then sends an HTML status report with a PDF attachment to a user-specified recipient. ## Quick Start Ask the agent to check the sandbox inbox with tribes-email and summarize the latest unread messages.

Frequently Asked Questions about zipbox-email

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I read email from a sandbox mailbox?▼

Use the tribes-email CLI: run tribes-email list to get message UIDs and the folder's uidValidity, then tribes-email read <uid> --uid-validity N to read a specific message. Never call IMAP, SMTP, or MXroute directly.

How do I send an HTML email with attachments from the CLI?▼

Write the markup to a file and run tribes-email send <recipient> <subject> --body-html-file path, adding --cc and --attach flags as needed. The CLI derives a text/plain alternative automatically and sends multipart/alternative.

Does tribes-email support BCC recipients?▼

No, BCC is not supported and the CLI rejects a --bcc flag. Do not simulate BCC by sending the same message twice; use repeated --cc flags for additional recipients, up to 50 addresses.

Why does tribes-email require a uid-validity argument?▼

UIDVALIDITY prevents acting on the wrong message, since a UID is only meaningful within one folder generation. Copy both the UID and uidValidity from a fresh list result; if the server reports stale UIDVALIDITY, list the folder again.

What happens when I delete or spam a message with tribes-email?▼

Both are safe moves, not immediate expunges: delete moves the message to Trash and spam moves it to Junk. Neither permanently destroys the message, and spam does not train a provider-wide spam model.

What are the attachment and body size limits for sending email?▼

Attachments allow up to 10 files at 5 MiB each and 5 MiB total, with content type inferred from file extension. Text and HTML bodies share a separate 1 MiB budget counted together.