Agent email cli
A collection of curated, useful, and safe skills for Autohand Code CLI Agent
npx -y skills add autohandai/community-skills --skill agent-email-cliAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 9 stars9 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
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.
SKILL.md
2.7 KB, as published. Nobody here has run it
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
defaultalias 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
codeandhintfields 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/binor npm global bin path is onPATH.NO_ACTIVE_ACCOUNT: runagent-email createoragent-email use <email>.ACCOUNT_NOT_FOUND: runagent-email accounts listand pick a valid address.EOTPduring 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.