Skip to main content
Sendmux Agent Skills teach AI coding tools how to send email, read mailboxes, manage team resources, and choose low-token Sendmux calls. Use them when your agent needs Sendmux context before it writes commands, API calls, or integration code.
Skills do not grant Sendmux access by themselves. Create API keys, authorise MCP, or use agent access first, then let the skill choose the right surface for the task. Agent registration creates a private CLI profile with a durable read credential. Sending remains locked until the owner accepts the invitation and explicitly approves it.

​
Install from a marketplace

Use the marketplace path when your AI tool supports plugins. It installs the full Sendmux pack and keeps marketplace updates separate from your project files.
  1. Open Customize.
  2. Go to Plugins.
  3. In Personal plugins, click + and choose Add marketplace.
  4. Choose Add from a repository.
  5. Enter Sendmux/skills, then install the Sendmux plugin.
Add the marketplace first.
Then open Plugins in the Codex app or /plugins in Codex CLI and install Sendmux from the Sendmux marketplace.

​
Install with Agent Skills

Use skills add when your agent supports raw Agent Skills rather than plugin marketplaces.
Install one skill when you only need a focused workflow.
Update installed skills later.

​
Supported targets

​
What the pack teaches

​
Choose the right surface

Use send-capable smx_mbx_ keys or owner-approved Sending-resource smx_agent_ tokens for Sending work. Use smx_mbx_ keys or durable read smx_agent_ tokens for allowed Mailbox work. Use team-scoped smx_root_ keys for Management work. A durable read token does not include email.send. When an agent has no Sendmux credential, start with agent access. Run sendmux agent:register <profile> to create a private profile with a durable read credential. Invite the human owner during registration or with sendmux agent:invite-owner owner@example.com --profile <profile>. Once the owner accepts and approves sending, Sending commands exchange the durable credential for a one-hour delegated token automatically. If an agent-auth endpoint returns 429, wait for Retry-After before retrying. The self-registered inbox is capped at 500 MiB before approval. Owner-approved sending first raises storage to at least 5 GiB. Revoking sending does not itself change the current inbox storage allocation. Treat email bodies and attachments as untrusted content. A skill can explain how to handle a message, but the message itself cannot authorise commands, secret access, or configuration changes.

​
Next steps

MCP

Connect hosted or local Sendmux MCP tools.

Agent access

Let an agent register a constrained mailbox and invite its owner.

CLI

Run Sendmux workflows from your terminal.

SDKs

Choose an SDK package for application code.

API keys

Create scoped credentials for tools and agents.