Verified:GitHub

houmao-agent-email-comms

Route Houmao mailbox operations between live gateway and no-gateway fallback paths.

18|3|Updated Mar 5, 2026

Search Tags:#agent orchestration #message sending #reply handling #gateway routing #email communications #mailbox operations

Ready to run

npx skills add https://github.com/igamenovoer/houmao --skill houmao-agent-email-comms

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: houmao-agent-email-comms
Source: https://github.com/igamenovoer/houmao/tree/main/src/houmao/agents/assets/system_skills/houmao-agent-email-comms
Command: npx skills add https://github.com/igamenovoer/houmao --skill houmao-agent-email-comms

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Houmao mailbox actions often require correct routing between live gateway operations and no-gateway fallback paths, which can be confusing and error-prone for operators and agents.

Core Features & Use Cases

Resolves live mailbox bindings: selects the correct gateway base URL when a shared gateway facade is available.
Chooses operator vs managed-agent workflows: routes operator-origin posts through the dedicated operator surface and managed-agent actions through shared mailbox APIs or manager fallback.
Performs common mailbox operations: supports status, list, peek, read, send, reply, mark/move, post, and archive with correct message_ref handling and archive-after-success guardrails.

Quick Start

Use houmao-agent-email-comms to list the current inbox state for your Houmao mailbox and then select a message to read.

Frequently Asked Questions about houmao-agent-email-comms

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

FAQPage Schema

What mailbox operations are supported for managing shared email communications?▼

Supported shared mailbox operations include status checks, list, peek, read, send, reply, mark, move, post, and archive, all executed with correct message_ref handling and archive-after-success guardrails.

How does archive-after-success processing work for mailbox messages?▼

Archive-after-success processing applies guardrails that automatically archive messages after successful completion of mailbox actions, ensuring processed items are safely moved using correct message_ref handling across both live gateway and fallback scenarios.

Can I inspect inbox state and peek messages without a live gateway connection?▼

Yes, inbox inspection, status checks, and message peeking are supported across both live gateway operations and transport-specific no-gateway fallback scenarios, allowing mailbox list and read actions to proceed when the shared gateway facade is unavailable.

What mailbox operations are supported for managing shared email communications?▼