shitty-emailCreate and manage temporary disposable email inboxes
Install via ClawdBot CLI:
clawdbot install johanski/shitty-emailGrade Fair — based on market validation, documentation quality, package completeness, maintenance status, and authenticity signals.
Sends data to undocumented external endpoint (potential exfiltration)
POST → https://shitty.email/api/inboxCalls external URL not in known-safe list
https://shitty.email`AI Analysis
The skill interacts with a documented external API (shitty.email) for its stated purpose of managing disposable email inboxes. While it sends data to an external server, this is consistent with the skill's functionality and does not appear to harvest credentials or contain hidden malicious instructions. The primary risk is reliance on a third-party service for temporary email handling.
Audited Apr 16, 2026 · audit v1.0
Generated Mar 21, 2026
Developers and QA engineers use temporary email addresses to test email sending functionality, sign-up flows, and verification processes in applications without cluttering personal or corporate inboxes. This ensures accurate testing of email-based features like password resets, notifications, and confirmations in staging or development environments.
Consumers create disposable emails to sign up for e-commerce newsletters, promotional offers, or free trials without exposing their primary email to potential spam. This allows them to access discounts or trial services while maintaining privacy and avoiding unwanted marketing communications.
Security professionals and privacy-conscious users employ temporary inboxes to register on websites or services that may have questionable data practices, reducing the risk of data breaches or phishing attacks. It helps isolate potential threats and protects sensitive personal information from being compromised.
Marketing teams use disposable emails to test email campaigns, track deliverability, and analyze engagement metrics without affecting real customer data. This enables A/B testing of subject lines, content, and timing in a controlled environment before launching to actual audiences.
Instructors and students in tech courses utilize temporary emails to practice email integration, API usage, or automation scripts without needing personal accounts. This supports hands-on learning in programming, web development, or IT security classes with real-world email handling scenarios.
Offer a free tier with basic features like inbox creation and limited email checks, while charging for premium features such as extended inbox lifetimes, higher email size limits, or advanced analytics. Revenue is generated through subscription plans or pay-as-you-go API calls for high-volume users.
Provide customizable temporary email services that companies can integrate into their own platforms, such as for customer support testing or internal tool development. Revenue comes from licensing fees, customization services, and ongoing technical support for enterprise clients.
Offer the service for free to individual users, generating revenue through targeted advertisements displayed in the user interface or within email content. This model attracts a large user base, with monetization via ad clicks, impressions, or sponsored integrations with other tools.
💬 Integration Tip
Always store and reuse the token from inbox creation for subsequent API calls to maintain session consistency and avoid unnecessary rate limiting.
Scored Jun 19, 2026
Gmail API integration with managed OAuth. Read, send, and manage emails, threads, labels, and drafts. Use this skill when users want to interact with Gmail. For other third party apps, use the api-gateway skill (https://clawhub.ai/byungkyu/api-gateway).
Microsoft Outlook API integration with managed OAuth. Read, send, and manage emails, folders, calendar events, and contacts via Microsoft Graph. Use this skill when users want to interact with Outlook. For other third party apps, use the api-gateway skill (https://clawhub.ai/byungkyu/api-gateway).
API-first email platform designed for AI agents. Create and manage dedicated email inboxes, send and receive emails programmatically, and handle email-based workflows with webhooks and real-time events. Use when you need to set up agent email identity, send emails from agents, handle incoming email workflows, or replace traditional email providers like Gmail with agent-friendly infrastructure.
Use when building email features, emails going to spam, high bounce rates, setting up SPF/DKIM/DMARC authentication, implementing email capture, ensuring compliance (CAN-SPAM, GDPR, CASL), handling webhooks, retry logic, or deciding transactional vs marketing.
Provides your AI agent with its own email address to send, receive, search, and manage emails independently under human supervision.
Fetches recent emails from Gmail and provides concise summaries. Use when the user wants to check emails, get email summaries, or review their inbox.