agent-email-cli

Original：🇺🇸 English

Translated

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.

20.7kinstalls

Sourcezaddy6/agent-email-skill

Added on2026-02-28

NPX Install

npx skill4agent add zaddy6/agent-email-skill agent-email-cli

SKILL.md Content

View Translation Comparison →

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.

bash

command -v agent-email
agent-email --help

If missing, install:

bash

npm install -g @zaddy6/agentemail
# or
bun install -g @zaddy6/agentemail

Create a mailbox account.

bash

agent-email create

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.

Read latest messages.

bash

agent-email read <email|default>

For inbox waiting/polling:

bash

agent-email read <email|default> --wait 30 --interval 2

For full message payloads:

bash

agent-email read <email|default> --full

Retrieve one message in detail.

bash

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.

bash

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.

bash

agent-email delete <email|default> <messageId>

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 (
```
AUTH_REQUIRED
```
/401), rerun command once and request user intervention if credentials must be re-established.
For rate limits (
```
RATE_LIMITED
```
/429), retry after short delay.

Troubleshooting

```
command not found
```
: ensure
```
~/.bun/bin
```
or npm global bin path is on
```
PATH
```
.

NO_ACTIVE_ACCOUNT

: run

agent-email create

or

agent-email use <email>

.

ACCOUNT_NOT_FOUND

: 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.

agent-email-cli

NPX Install

Tags

SKILL.md Content

Agent Email CLI

Overview

Workflow

Operational Guidance

Troubleshooting

References