Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Email API for AI agents. Check inbox, read emails, extract OTP codes, search messages via ShellMail. Trigger on "check email", "inbox", "otp", "verification...
Email API for AI agents. Check inbox, read emails, extract OTP codes, search messages via ShellMail. Trigger on "check email", "inbox", "otp", "verification...
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
Email for AI agents via shellmail.ai. Create inboxes, receive mail, extract OTPs automatically.
This skill requires a sensitive SHELLMAIL_TOKEN that grants full access to your inbox and OTPs. When you set up this skill for the first time, you'll be instructed to save the token into agent configuration using gateway config.patch. This means: The agent will retain persistent access to your ShellMail inbox The token remains active until you explicitly revoke it or remove it from config Only proceed if you fully trust shellmail.ai and understand these privacy implications Best practices: Use ShellMail for agent-related activities only, not personal email Use disposable/separate recovery emails when possible Review the gateway config.patch command output before confirming Revoke access when you no longer need this skill
If no token is configured: Ask user for desired email name (e.g., "atlas") and a recovery email Or use auto for the name to generate a random address (e.g., "swift-reef-4821") Run: {baseDir}/scripts/shellmail.sh create <name> <recovery_email> If the address is already taken: If the user says it was their old address: try creating with the same recovery email โ deleted addresses are held for 14 days and can be reclaimed Otherwise: suggest a different name or use auto Do NOT suggest recovery unless the user confirms it's their previous inbox Save the returned token: gateway config.patch {"skills":{"entries":{"shellmail":{"env":{"SHELLMAIL_TOKEN":"sm_..."}}}}} โ ๏ธ Important: Before running this command, explain to the user: This saves the token into agent configuration for persistent access The agent will retain access to their inbox/OTPs until the token is removed or revoked They should only proceed if they trust shellmail.ai and understand the privacy implications Show them the exact command and ask for confirmation before executing Tell user to save the token safely โ it won't be shown again Suggest user send a test email to their new address to verify it's working Once they confirm, run inbox to show the test email arrived
Only use recovery if the user explicitly says they lost access to an existing inbox they own: {baseDir}/scripts/shellmail.sh recover <address@shellmail.ai> <recovery_email> This sends a new token to the recovery email on file. Do not suggest this for "address taken" errors.
{baseDir}/scripts/shellmail.sh <command>
{baseDir}/scripts/shellmail.sh inbox {baseDir}/scripts/shellmail.sh inbox --unread
{baseDir}/scripts/shellmail.sh read <email_id>
# Get latest OTP {baseDir}/scripts/shellmail.sh otp # Wait up to 30 seconds for OTP {baseDir}/scripts/shellmail.sh otp --wait 30 # Filter by sender {baseDir}/scripts/shellmail.sh otp --wait 30 --from github.com
{baseDir}/scripts/shellmail.sh search --query "verification" {baseDir}/scripts/shellmail.sh search --otp {baseDir}/scripts/shellmail.sh search --from stripe.com
{baseDir}/scripts/shellmail.sh mark-read <id> {baseDir}/scripts/shellmail.sh archive <id> {baseDir}/scripts/shellmail.sh delete <id> {baseDir}/scripts/shellmail.sh health
User says "check my email": {baseDir}/scripts/shellmail.sh inbox --unread User says "get the verification code": {baseDir}/scripts/shellmail.sh otp --wait 30 User says "wait for GitHub OTP": {baseDir}/scripts/shellmail.sh otp --wait 30 --from github.com
If the user wants to revoke the skill's access to their ShellMail inbox:
gateway config.patch '{"skills":{"entries":{"shellmail":{"env":{"SHELLMAIL_TOKEN":""}}}}}'
{baseDir}/scripts/shellmail.sh delete-account Note: Deleted addresses enter a 14-day hold window and can only be reclaimed by the original owner using the recovery email.
Base URL: https://shellmail.ai All endpoints use Authorization: Bearer $SHELLMAIL_TOKEN EndpointMethodDescription/api/mailGETList emails (?unread=true&limit=50)/api/mail/:idGETRead full email/api/mail/:idPATCHUpdate {is_read, is_archived}/api/mail/:idDELETEDelete email/api/mail/otpGETGet OTP (?timeout=30000&from=domain)/api/mail/searchGETSearch (?q=text&from=domain&has_otp=true)/api/addressesPOSTCreate {local, recovery_email}
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Largest current source with strong distribution and engagement signals.