Agent skill · software engineering · aiskillstore
agent-email-cli
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.
Why this skill is useful
Adds specific command usage patterns and JSON output handling for the agent-email CLI that the AI wouldn't reliably generate on its own.
What it needs
Requires npm installed locally. About 2k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
Agent Email CLI Overview Use this skill to operate the agent-email command safely and predictably for agent workflows that need inbox access. Prefer JSON-native command output and return key fields (email, messageId, subject, createdAt, from.address) in your summaries. Workflow 1. Verify CLI availability. If missing, install: 2. Create a mailbox account. Record these fields from JSON output: data.email data.accountId data.activeEmail Do not record, repeat, or print secret values such as mailbox passwords or tokens. 3. Read latest messages. For inbox waiting/polling: For full message payloads: 4. Retrieve one message in detail. Use show when you need body/source details for verification links, codes, or full content extraction. 5. Manage mailbox profiles. Avoid commands that require entering secrets on the command line in agent logs. 6. Delete processed/irrelevant message when requested. Operational Guidance Keep command output machine-readable; avoid forcing human output unless requested. Prefer default alias when user does not specify an email. Never echo, store, or summarize secret values (password, token) from command output. If command fails, surface the JSON error code and hint fields directly. For auth failures (AUTHREQUIRED/401), rerun command once and request user intervention if credentials must be re-established. For rate limits (RATELIMITED/429), retry after short delay. Troubleshooting command not found: ensure ~/.bun/bin or npm global bin path is on PATH. NOACTIVEACCOUNT: run agent-email create or agent-email use <email>. ACCOUNTNOTFOUND: run agent-email accounts list and pick a valid address. EOTP during npm publish: use npm trusted publishing for CI or publish locally with OTP. References For command cheat sheet and JSON field map, read references/commands.md.
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/agent-email-cli