Agent Email Cli

1---2name: agent-email-cli3description: Operate the agent-email CLI to create disposable inboxes, poll for new mail, retrieve full message details, and manage local mailbox profiles. Use when the user needs terminal-based email inbox access for LLM or agent automation workflows.4---5 6# Agent Email CLI7 8## Overview9 10Use this skill to operate the `agent-email` command safely and predictably for agent workflows that need inbox access.11 12Prefer JSON-native command output and return key fields (`email`, `messageId`, `subject`, `createdAt`, `from.address`) in your summaries.13 14## Workflow15 161. Verify CLI availability.17 18```bash19command -v agent-email20agent-email --help21```22 23If missing, install:24 25```bash26npm install -g @zaddy6/agentemail27# or28bun install -g @zaddy6/agentemail29```30 312. Create a mailbox account.32 33```bash34agent-email create35```36 37Record these fields from JSON output:38 39- `data.email`40- `data.accountId`41- `data.activeEmail`42 43Do not record, repeat, or print secret values such as mailbox passwords or tokens.44 453. Read latest messages.46 47```bash48agent-email read <email|default>49```50 51For inbox waiting/polling:52 53```bash54agent-email read <email|default> --wait 30 --interval 255```56 57For full message payloads:58 59```bash60agent-email read <email|default> --full61```62 634. Retrieve one message in detail.64 65```bash66agent-email show <email|default> <messageId>67```68 69Use `show` when you need body/source details for verification links, codes, or full content extraction.70 715. Manage mailbox profiles.72 73```bash74agent-email accounts list75agent-email use <email|default>76agent-email accounts remove <email>77```78 79Avoid commands that require entering secrets on the command line in agent logs.80 816. Delete processed/irrelevant message when requested.82 83```bash84agent-email delete <email|default> <messageId>85```86 87## Operational Guidance88 89- Keep command output machine-readable; avoid forcing human output unless requested.90- Prefer `default` alias when user does not specify an email.91- Never echo, store, or summarize secret values (`password`, `token`) from command output.92- If command fails, surface the JSON error `code` and `hint` fields directly.93- For auth failures (`AUTH_REQUIRED`/401), rerun command once and request user intervention if credentials must be re-established.94- For rate limits (`RATE_LIMITED`/429), retry after short delay.95 96## Troubleshooting97 98- `command not found`: ensure `~/.bun/bin` or npm global bin path is on `PATH`.99- `NO_ACTIVE_ACCOUNT`: run `agent-email create` or `agent-email use <email>`.100- `ACCOUNT_NOT_FOUND`: run `agent-email accounts list` and pick a valid address.101- `EOTP` during npm publish: use npm trusted publishing for CI or publish locally with OTP.102 103## References104 105- For command cheat sheet and JSON field map, read [references/commands.md](references/commands.md).