email-skill

Route email requests to public mailbox push or IMAP/SMTP flows.

Updated May 4, 2026
One-click install
npx skills add https://github.com/234194027-cpu/xianclaw --skill email-skill-234194027-cpu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: email-skill
Source: https://github.com/234194027-cpu/xianclaw/tree/main/resources/openclaw/config/skills/email-skill
Command: npx skills add https://github.com/234194027-cpu/xianclaw --skill email-skill-234194027-cpu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill handles email-related requests by interpreting the user’s intent and routing it to the correct downstream email capability, so users don’t need to know the technical differences between simple message pushes and full IMAP/SMTP email operations.

Core Features & Use Cases

  • Unified email entry point: Detects email intent and sends the task to the appropriate downstream skill instead of executing actions itself.
  • Smart routing logic: Chooses between public-skill (push to the user’s own mailbox, plain-text, no attachments) and imap-smtp-email (third-party recipients, CC/BCC, HTML, attachments, inbox search, and download scenarios).
  • Fallback and safety guardrails: Defines when a public-skill failure should fall back to imap-smtp-email, and includes restrictions against leaking sensitive credentials or unsafe file paths.

Quick Start

Ask your agent to send a daily report to your email using the phrase “每天把日报推到我邮箱”,and the request will be routed to public-skill for a plain-text self-delivery flow.

Frequently Asked Questions about email-skill

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How does email intent routing work for different IMAP and SMTP requests?

Email intent routing analyzes your request keywords to direct tasks to either a plain-text public mailbox push flow or a full IMAP/SMTP flow for third-party recipients, CC/BCC, and attachments. It acts as a recognition layer without executing email scripts itself.

When do I need full IMAP and SMTP email capabilities instead of a simple push?

You need full IMAP and SMTP email capabilities when sending to third parties, using CC/BCC, composing HTML messages, attaching files, or performing inbox search and attachment downloads. Simple plain-text self-delivery requests use the public mailbox push flow.

Can I send emails with attachments and HTML formatting using intent routing?

Yes, intent routing detects attachment and HTML composition requirements and routes your request to the full IMAP/SMTP email flow, enabling third-party recipients, CC/BCC, inbox search, and attachment downloads.

What happens if a public mailbox push notification fails to send?

If a public mailbox push notification fails, the routing logic includes fallback rules that redirect the email request to the full IMAP/SMTP email flow to ensure delivery completion.

What safety constraints apply when routing email requests with sensitive credentials?

The email routing layer enforces safety constraints that restrict leaking sensitive credentials and unsafe file paths, ensuring secure intent recognition and routing without exposing vulnerable data during the email handling process.