sendmux-attachments

Manage Sendmux email attachments with local paths, presigned URLs, or base64.

31|1|Updated Jun 17, 2026
One-click install
npx skills add https://github.com/Sendmux/skills --skill sendmux-attachments
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sendmux-attachments
Source: https://github.com/Sendmux/skills/tree/main/plugins/sendmux/skills/sendmux-attachments
Command: npx skills add https://github.com/Sendmux/skills --skill sendmux-attachments

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines attachment workflows for Sendmux, reducing model context waste on base64 encoding and improving the efficiency of email communication.

Core Features & Use Cases

  • Attachment Management: Upload, download, read, forward, and send email attachments.
  • Efficient File Handling: Choose between local file paths, presigned upload URLs, or inline base64 depending on file size and context.
  • Use Case: When you need to send a large document via email, you can use this Skill to upload it as a presigned URL, avoiding the need for base64 encoding which would consume excessive tokens.

Quick Start

Upload the attachment 'invoice.pdf' to your Sendmux mailbox and use it in a message.

Frequently Asked Questions about sendmux-attachments

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

FAQPage Schema
How do I send large email attachments without wasting tokens on base64 encoding?

To manage email attachments without wasting tokens, choose between local file paths, presigned upload URLs, or inline base64 based on file size. Using presigned URLs for large files avoids base64 encoding and reduces context waste.

What is the best way to handle file attachments in batch email communications?

Handling file attachments in batch emails is best done by evaluating file size and context to select the right processing method. Choosing presigned URLs or local paths over inline base64 optimizes token usage and prevents context overflow.

When should I use a presigned upload URL instead of inline base64 for email attachments?

Use a presigned upload URL instead of inline base64 when dealing with large documents. Presigned URLs prevent excessive token consumption by keeping heavy file data out of the model's context window during email workflows.

Can I upload, forward, and download email attachments using Sendmux API interactions?

Yes, you can upload, download, read, forward, and send email attachments through Sendmux API interactions. The workflow supports multiple file handling options to manage context efficiently across various attachment scenarios.

Does Sendmux support local file paths for managing email attachments?

Yes, Sendmux supports local file paths as a file handling option for managing email attachments. This method, alongside presigned URLs and inline base64, helps optimize token usage depending on file size and context.