Terminal-based disposable email inbox management for agent automation workflows.
Works with
Create temporary mailboxes, poll for new messages with configurable wait/interval, and retrieve full message details including body and source
JSON-native output with key fields ( email , messageId , subject , from.address , createdAt ) designed for agent parsing and summarization
Manage multiple mailbox profiles locally with accounts list , use , and remove commands; supports default alias for simplifie
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionagent-email-cliExecute the skills CLI command in your project's root directory to begin installation:
Fetches agent-email-cli from zaddy6/agent-email-skill and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate agent-email-cli. Access via /agent-email-cli in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
0
total installs
0
this week
6
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
6
stars
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.
command -v agent-email
agent-email --help
If missing, install:
npm install -g @zaddy6/agentemail
# or
bun install -g @zaddy6/agentemail
agent-email create
Record these fields from JSON output:
data.emaildata.accountIddata.activeEmailDo not record, repeat, or print secret values such as mailbox passwords or tokens.
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
agent-email show <email|default> <messageId>
Use show when you need body/source details for verification links, codes, or full content extraction.
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.
agent-email delete <email|default> <messageId>
default alias when user does not specify an email.password, token) from command output.code and hint fields directly.AUTH_REQUIRED/401), rerun command once and request user intervention if credentials must be re-established.RATE_LIMITED/429), retry after short delay.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.Prerequisites
Time Estimate
15-45 minutes depending on use case complexity
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
shadowcz007/skills
aaronontheweb/dotnet-skills
vercel-labs/agent-browser
panniantong/agent-reach
github/awesome-copilot
fluxa-agent-payment/fluxa-ai-wallet-mcp
Keeps context tight: agent-email-cli is the kind of skill you can hand to a new teammate without a long onboarding doc.
agent-email-cli is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Useful defaults in agent-email-cli — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Registry listing for agent-email-cli matched our evaluation — installs cleanly and behaves as described in the markdown.
agent-email-cli reduced setup friction for our internal harness; good balance of opinion and flexibility.
Useful defaults in agent-email-cli — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Keeps context tight: agent-email-cli is the kind of skill you can hand to a new teammate without a long onboarding doc.
I recommend agent-email-cli for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Registry listing for agent-email-cli matched our evaluation — installs cleanly and behaves as described in the markdown.
Registry listing for agent-email-cli matched our evaluation — installs cleanly and behaves as described in the markdown.
showing 1-10 of 61