uspeedo-email-sending-channel
by @code-by-ai
Sends user-authorized transactional email via uSpeedo API with ACCESSKEY credentials (env preferred). Before SendEmail, calls GetSenderList to resolve SendEm...
clawhub install uspeedo-email-sending-channel📖 About This Skill
name: uspeedo-email-sending-channel description: "Sends user-authorized transactional email via uSpeedo API with ACCESSKEY credentials (env preferred). Before SendEmail, calls GetSenderList to resolve SendEmail (default first enabled sender; user may override). Requires explicit confirmation of sender, recipients, subject, and content before sending." version: 1.0.0 metadata: openclaw: requires: env: - ACCESSKEY_ID - ACCESSKEY_SECRET primaryEnv: ACCESSKEY_SECRET homepage: "https://uspeedo.com/?ChannelCode=OpenClaw"
Send Email via uSpeedo Sending Channel
Before You Use (Installation Considerations)
1. Platform key handling: Confirm how your AI platform handles credentials and conversation history. Do not paste long-lived keys into chat unless the platform provides a temporary or secret input mechanism.
2. Key practice: Prefer short-lived or least-privilege API keys for testing; rotate keys after testing if they were exposed.
3. Credentials in metadata (OpenClaw): Frontmatter declares metadata.openclaw.requires.env (ACCESSKEY_ID, ACCESSKEY_SECRET) and metadata.openclaw.primaryEnv (ACCESSKEY_SECRET). Integrations and registries should surface these so users know key requirements before use.
4. Email content: The skill sends the user’s raw plain text or HTML. Avoid sending sensitive content or unvalidated HTML to prevent abuse or leakage.
5. If in doubt: If you cannot verify how the platform stores keys or how uSpeedo is used, treat credentials as highly sensitive and use one-time or test credentials only.
Platform persistence: This skill instructs the agent not to persist keys, but conversation context or platform logs may still retain user input. Prefer platforms that support ephemeral or secure credential input.
Credentials and Environment Variables
Prefer environment variables over user-provided credentials whenever possible.
| Variable | Required | Purpose | |----------|----------|---------| | ACCESSKEY_ID | Yes | uSpeedo API Basic auth (ID) | | ACCESSKEY_SECRET | Yes | uSpeedo API Basic auth (Secret) |
Obtaining environment variables (ACCESSKEY_ID / ACCESSKEY_SECRET): Go to Email API Key management to create or view API keys, and set them in .env or your system environment. If both environment variables and user-provided keys are present, environment variables take precedence. Keys are for authenticating the current request only; do not cache or persist them, and do not commit .env to version control.
Usage Restrictions (Mandatory)
ACCESSKEY_ID and ACCESSKEY_SECRET are for authenticating the current request only. They must not be written to session memory, knowledge base, cache, logs, code, or any storage that can be read later; after the call completes they are considered consumed and must not be retained or referenced.Authorization header, ACCESSKEY_SECRET, or full raw request/response payloads.Mandatory Safety Gates Before Sending
Run these checks before every send request:
1. Parameter confirmation gate (required):
- Resolve SendEmail first (see "Get Sender List and SendEmail resolution" below), then confirm SendEmail, all TargetEmailAddress, Subject, and Content with the user in the same turn.
- If any required field is missing/ambiguous, stop and ask for correction.
2. Recipient format gate (required):
- Reject obviously invalid emails (missing @, missing domain, empty items, non-string entries).
- De-duplicate recipients before sending.
3. HTML safety gate (required for HTML content):
- If content is HTML, warn the user that active content is not allowed.
- Reject or require user rewrite when HTML contains risky patterns such as