bot-email

What This Skill Does

The bot-email skill provides an integration with BotEmail.ai, enabling the OpenClaw agent to manage dedicated, permanent email addresses for automated tasks. It allows users to create email addresses instantly without complex signups, making it ideal for testing signup flows, receiving verification codes, or automating monitoring workflows. The skill supports full inbox management, including listing, viewing, and deleting emails. It also offers a 'heartbeat' notification system where the agent periodically monitors the inbox for new activity and alerts the user when new messages arrive.

Installation

To integrate this skill into your OpenClaw agent, use the following command in your terminal: clawhub install openclaw/skills/skills/claw-silhouette/bot-email-skill After installation, ensure you manage your API keys securely, preferably using a password manager or an environment variable file (.env). The agent will prompt you for these credentials when setting up monitoring or accessing your inbox.

Use Cases

• Verification Code Retrieval: Automatically grab OTPs or confirmation links during automated signups.
• End-to-End Testing: Validate that your web applications are successfully sending registration or transactional emails.
• Notification Monitoring: Keep tabs on third-party service updates or alerts sent to your bot account.
• Inbox Cleanup: Programmatically clear old emails to keep your testing environment clutter-free.

Example Prompts

1. "Get me a bot email for my new testing project and save the credentials securely."
2. "Check my bot email address and list the latest verification code I received from the signup service."
3. "Set up a heartbeat for my bot email; let me know immediately if any new messages arrive in the inbox."

Tips & Limitations

• Storage: Emails are stored for 6 months.
• Limits: The free tier supports 1 address and 1,000 requests per day.
• Formatting: All addresses automatically follow the format [email protected].
• Directionality: This skill is receive-only; sending emails is not supported via this API.
• Privacy: Only store API keys if explicitly requested, and always prioritize security best practices when handling sensitive credentials.