Shitty Email
VerifiedCreate and manage temporary disposable email inboxes
$ Add to .claude/skills/ About This Skill
# Shitty Email - Temporary Inbox Skill
Create disposable email addresses instantly. Perfect for signups, testing, and privacy.
When to Use This Skill
- Use this skill when the user needs to:
- Create a temporary/disposable email address
- Sign up for a service without using their real email
- Test email sending functionality
- Wait for a verification or confirmation email
- Extract codes or links from emails
Important: Token Management
When you create an inbox, you receive a token. This token is required for ALL subsequent operations. Always store and reuse the token for the same inbox session.
API Reference
Base URL: `https://shitty.email`
Create a New Inbox
```bash curl -s -X POST https://shitty.email/api/inbox | jq ```
Response: ```json { "email": "[email protected]", "token": "a1b2c3d4e5f6..." } ```
Store both the email and token - you need the token for all other operations.
Check Inbox for Emails
```bash curl -s -H "X-Session-Token: {token}" https://shitty.email/api/inbox | jq ```
Response: ```json { "emails": [ { "id": "msg_a1b2c3d4e5", "from": "[email protected]", "subject": "Welcome!", "date": "2026-02-03T12:00:00Z" } ] } ```
Get Full Email Content
Use the `id` field from the inbox response (e.g. `msg_a1b2c3d4e5`). This is NOT the email address.
```bash curl -s -H "X-Session-Token: {token}" https://shitty.email/api/email/{email_id} | jq ```
Response includes `html` and `text` fields with the email body.
Extend Inbox Lifetime
Inboxes expire after 1 hour by default. Extend by 1 hour (max 24 hours total):
```bash curl -s -X POST -H "X-Session-Token: {token}" https://shitty.email/api/inbox/extend | jq ```
Delete Inbox
Clean up when done:
```bash curl -s -X DELETE -H "X-Session-Token: {token}" https://shitty.email/api/inbox ```
Common Workflows
Wait for a Verification Email
Poll the inbox until an email matching criteria arrives:
```bash # Create inbox RESPONSE=$(curl -s -X POST https://shitty.email/api/inbox) EMAIL=$(echo $RESPONSE | jq -r '.email') {token}=$(echo $RESPONSE | jq -r '.token')
# Poll for emails (check every 5 seconds, max 60 seconds) for i in {1..12}; do EMAILS=$(curl -s -H "X-Session-Token: ${token}" https://shitty.email/api/inbox) COUNT=$(echo $EMAILS | jq '.emails | length') if [ "$COUNT" -gt "0" ]; then echo "Email received!" echo $EMAILS | jq '.emails[0]' break fi sleep 5 done ```
Extract Verification Code
After receiving an email, extract common verification patterns:
```bash # Get email content CONTENT=$(curl -s -H "X-Session-Token: ${token}" https://shitty.email/api/email/${email_id} | jq -r '.text')
# Common patterns to look for: # - 6-digit codes: grep -oE '[0-9]{6}' # - Verification links: grep -oE 'https?://[^ ]+verify[^ ]*' ```
Best Practices
- Reuse tokens - Don't create new inboxes unnecessarily
- Poll responsibly - Wait 5 seconds between checks
- Clean up - Delete inbox when done to free resources
- Extend if needed - If waiting for slow emails, extend the inbox
Limitations
- Inboxes expire after 1 hour (extendable to 24 hours max)
- Email size limit: 1MB
- Rate limited: Don't spam inbox creation
- No outbound email - receive only
Example Conversation
User: "Create a temp email for me" → Call POST /api/inbox, return the email address, store the token
User: "Sign me up for newsletter.example.com" → Use the temp email to fill the signup form, then poll for confirmation
User: "Did I get the confirmation?" → Check inbox using stored token, report results
User: "What's the verification code?" → Fetch email content, extract the code pattern, return it
User: "I'm done, delete the inbox" → Call DELETE /api/inbox with the token
Use Cases
- Send emails programmatically from AI agent workflows
- Draft professional emails based on context and recipient information
- Automate email composition and sending for routine communications
Pros & Cons
Pros
- +Well-adopted with 1,828+ downloads showing reliable real-world usage
- +Well-structured approach ensures consistent and reliable results
- +Integrates smoothly into existing workflows
Cons
- -Focused scope means it may not cover edge cases outside its primary use case
- -May require adaptation for non-standard project configurations
FAQ
What does Shitty Email do?
What platforms support Shitty Email?
What are the use cases for Shitty Email?
100+ free AI tools
Writing, PDF, image, and developer tools — all in your browser.
Next Step
Use the skill detail page to evaluate fit and install steps. For a direct browser workflow, move into a focused tool route instead of staying in broader support surfaces.