Marketplace 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.
install
source · Clone the upstream repo
git clone https://github.com/aiskillstore/marketplace
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/aiskillstore/marketplace "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/zaddy6/agent-email-cli" ~/.claude/skills/aiskillstore-marketplace-agent-email-cli && rm -rf "$T"
manifest:
skills/zaddy6/agent-email-cli/SKILL.mdsource content
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
- Verify CLI availability.
command -v agent-email agent-email --help
If missing, install:
npm install -g @zaddy6/agentemail # or bun install -g @zaddy6/agentemail
- Create a mailbox account.
agent-email create
Record these fields from JSON output:
data.emaildata.accountIddata.activeEmail
Do not record, repeat, or print secret values such as mailbox passwords or tokens.
- Read latest messages.
agent-email read <email|default>
For inbox waiting/polling:
agent-email read <email|default> --wait 30 --interval 2
For full message payloads:
agent-email read <email|default> --full
- Retrieve one message in detail.
agent-email show <email|default> <messageId>
Use
show when you need body/source details for verification links, codes, or full content extraction.
- Manage mailbox profiles.
agent-email accounts list agent-email use <email|default> agent-email accounts remove <email>
Avoid commands that require entering secrets on the command line in agent logs.
- Delete processed/irrelevant message when requested.
agent-email delete <email|default> <messageId>
Operational Guidance
- Keep command output machine-readable; avoid forcing human output unless requested.
- Prefer
alias when user does not specify an email.default - Never echo, store, or summarize secret values (
,password
) from command output.token - If command fails, surface the JSON error
andcode
fields directly.hint - For auth failures (
/401), rerun command once and request user intervention if credentials must be re-established.AUTH_REQUIRED - For rate limits (
/429), retry after short delay.RATE_LIMITED
Troubleshooting
: ensurecommand not found
or npm global bin path is on~/.bun/bin
.PATH
: runNO_ACTIVE_ACCOUNT
oragent-email create
.agent-email use <email>
: runACCOUNT_NOT_FOUND
and pick a valid address.agent-email accounts list
during npm publish: use npm trusted publishing for CI or publish locally with OTP.EOTP
References
- For command cheat sheet and JSON field map, read references/commands.md.