Menu
Host-side Email work-inbox channel for LionClaw.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Use this skill when asked to communicate with another local LionClaw project instance, teammate, reviewer, QA instance, or sibling agent through team-local. Use it to list reachable instances, resolve routes, and send requested questions, results, updates, or /runtime attachments via the LionClaw channel_send MCP tool.
First-party LionClaw channel for local project instance communication.
Use when the user invokes $lionclaw-private-context, asks what LionClaw remembers, or wants to remember, update, or clarify durable memory, style, preferences, or private context.
Host-side LionClaw private-context skill for deterministic projection, committed-turn recording, and explicit profile or memory management.
Handle LionClaw email-channel turns and replies without touching mailbox credentials or raw mail transport.
Run and operate a Telegram channel worker for LionClaw using the kernel channel bridge APIs.
| name | channel-email |
| description | Host-side Email work-inbox channel for LionClaw. |
This skill runs the host-side Email channel worker. It owns mailbox auth, IMAP/SMTP transport, held-mail state, and provider-specific email handling. The runtime never receives mailbox credentials or OAuth tokens.
The channel admits only exact approved senders through LionClaw channel grants.
Unknown mail is held or suppressed by the worker and must not become runtime
work unless the local operator explicitly approves the sender or releases an
authenticated held item. Full message bodies are fetched only after approval
and are capped by EMAIL_MAX_MESSAGE_BYTES before any runtime work is queued.
Mailbox auth is either EMAIL_AUTH_MODE=basic with IMAP/SMTP passwords, or
EMAIL_AUTH_MODE=xoauth2 with an absolute EMAIL_XOAUTH2_TOKEN_CMD; missing
EMAIL_AUTH_MODE defaults to basic for legacy configs. The normal OAuth2 setup
path is lionclaw connect email <provider> ..., which runs this channel's
setup helper from the installed channel snapshot. The channel binary also
exposes the lower-level oauth2 setup and oauth2 token commands; token
refresh runs host-side without a shell and prints only a short-lived access
token to stdout. Refresh-token state remains outside runtime projection.
This channel package also carries the runtime-facing email Agent Skill at
runtime/email/. LionClaw projects that facet into runtimes when this skill is
bound as the email channel, while keeping the host-side channel package and
mail transport credentials out of the runtime.
Detailed architecture, setup, QA, one-shot release behavior, and packaged asset
notes for this channel live in README.md in this skill directory.
