← Back to Skills Marketplace
🔌

Resend

by OOMOL · GitHub ↗ · v1.0.0 · MIT-0
cross-platform ✓ Security Clean
27
Downloads
0
Stars
0
Active Installs
1
Versions
Install in OpenClaw
/install oo-resend
Description
Resend (resend.com). Use this skill for ANY Resend request — reading, creating, and updating data. Whenever a task involves Resend, use this skill instead of...
README (SKILL.md)

Resend

Operate Resend through your OOMOL-connected account. This skill calls the resend connector with the oo CLI; OOMOL injects credentials server-side, so you never handle raw tokens.

Category: Communication, Marketing. Exposes 1 action(s).

Running an action

Assume the user has already installed the oo CLI, signed in, and connected Resend. Do not run oo auth login or open the connection URL proactively — just run the action. Fall back to First-time setup only when a command actually fails with an auth or connection error.

1. Inspect the contract to get the authoritative input/output schema before building a payload:

oo connector schema "resend" --action "\x3Caction_name>"

2. Run the action with a JSON payload that matches the input schema:

oo connector run "resend" --action "\x3Caction_name>" --data '\x3Cjson>' --json
  • --data takes a JSON object string or @path/to/file.json; omit it to send {}.
  • The response is { "data": ..., "meta": { "executionId": "..." } }; the execution id lives under meta.executionId.

Each action below links to a reference file with its purpose and exact commands. Read the linked file, then fetch the live schema with oo connector schema before constructing --data.

Available actions

Safety

  • Read actions (get / list / search) are safe to run directly.
  • Create, update, send, or post actions change Resend state — confirm the exact payload and effect with the user before running.
  • Delete or remove actions are destructive — always confirm the target and get explicit approval first.

First-time setup

These are one-time steps — do not repeat them on every call. Run a step only when a command fails for the matching reason.

  • oo: command not found — install the oo CLI (other platforms: \x3Chttps://cli.oomol.com/install-guide.md>):

    curl -fsSL https://cli.oomol.com/install.sh | bash    # macOS / Linux
    
    irm https://cli.oomol.com/install.ps1 | iex           # Windows PowerShell
    
  • Not signed in / authentication error — sign in to your OOMOL account once:

    oo auth login
    
  • scope_missing / credential_expired / app_not_ready / app_not_found — Resend is not connected, or the connection expired or lacks a scope. Connect once (auth type: API key) at:

    https://console.oomol.com/app-connections?provider=resend
    
  • HTTP 402 / OOMOL_INSUFFICIENT_CREDIT — billing stop. Recharge at https://console.oomol.com/billing/token-recharge before retrying.

Resources

Usage Guidance
Install only if you trust OOMOL as the connector provider and intend to let your agent send email through your connected Resend account. Review the recipient, subject, body, and sending domain before approving any send action, and treat the CLI installation step as a one-time setup from OOMOL’s own installer.
Capability Tags
requires-sensitive-credentials
Capability Assessment
Purpose & Capability
The artifact’s stated purpose is operating Resend through OOMOL, and the only listed action is sending email through the Resend connector.
Instruction Scope
Runtime instructions are scoped to inspecting the connector schema and running the named Resend action; write/send actions explicitly require confirming the exact payload and effect first.
Install Mechanism
First-time setup includes installing the OOMOL CLI from OOMOL URLs if the CLI is missing, but this is disclosed, conditional on failure, and coherent with using the connector.
Credentials
The skill needs sensitive Resend/OOMOL credentials and can send email, which is meaningful account authority, but the credential handling is disclosed as server-side injection and tied to the stated integration.
Persistence & Privilege
No background persistence, local indexing, hidden files, destructive automation, or privilege escalation is present in the artifacts reviewed.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install oo-resend
  3. After installation, invoke the skill by name or use /oo-resend
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
- Connects agents to Resend through the OOMOL `resend` connector, using server-side credential injection so raw API tokens are not handled locally. - Provides a focused `send_email` action for sending email through a connected Resend account. - Guides agents to inspect the live connector schema before building payloads, keeping requests aligned with upstream contract changes. - Standardizes `oo connector run` usage with JSON payloads and structured responses that include `meta.executionId`. - Includes safety rules for write actions, requiring confirmation of the exact email payload and intended effect before sending.
Metadata
Slug oo-resend
Version 1.0.0
License MIT-0
All-time Installs 0
Active Installs 0
Total Versions 1
Frequently Asked Questions

What is Resend?

Resend (resend.com). Use this skill for ANY Resend request — reading, creating, and updating data. Whenever a task involves Resend, use this skill instead of... It is an AI Agent Skill for Claude Code / OpenClaw, with 27 downloads so far.

How do I install Resend?

Run "/install oo-resend" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is Resend free?

Yes, Resend is completely free, licensed under MIT-0. You can download, install and use it at no cost.

Which platforms does Resend support?

Resend is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created Resend?

It is built and maintained by OOMOL (@oomol); the current version is v1.0.0.

💬 Comments