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.

Safety Notice

This listing is imported from skills.sh public index metadata. Review upstream SKILL.md and repository scripts before running.

Copy this and send it to your AI assistant to learn

Install skill "agent-email-cli" with this command: npx skills add zaddy6/agent-email-skill/zaddy6-agent-email-skill-agent-email-cli

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.
command -v agent-email
agent-email --help

If missing, install:

npm install -g @zaddy6/agentemail
# or
bun install -g @zaddy6/agentemail
  1. Create a mailbox account.
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.

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

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

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

Source Transparency

This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.

Related Skills

Related by shared tags or category signals.

Coding

Workspace Init

Use this skill to initialize or update a multi-repo workspace created from dev-config-template. Invoke whenever the user wants to: set up a fresh workspace c...

Registry SourceRecently Updated
Coding

Google Seo Assistant

A client-facing SEO assistant grounded in Google's official SEO Starter Guide. Use this skill whenever a user mentions SEO, search rankings, Google visibilit...

Registry SourceRecently Updated
Coding

Version Drift

One command to check if your entire stack is up to date. SSHes into servers, queries APIs, and compares installed versions against latest — across every serv...

Registry SourceRecently Updated