LegalGo Mail Assistant

Use this skill to send emails through LegalGo.

Read only what you need:

• Read references/api.md for request and response formats.
• Read references/mail-constraints.md for sending prerequisites and safety checks.
• Read references/error-handling.md when the API returns a send failure.

Required configuration

Require these environment variables:

• LEGALGO_API_BASE_URL
• LEGALGO_MAIL_SEND_KEY

LEGALGO_MAIL_SEND_KEY must be sent as an HTTP header on every runtime request:

X-LegalGo-Key: {LEGALGO_MAIL_SEND_KEY}

Do not assume OpenClaw will automatically transform this environment variable into an auth header. If this skill is implemented through direct HTTP requests instead of bundled scripts, explicitly inject the header when calling:

• /openclaw/credential/me
• /openclaw/mail/send

Run scripts/check_credential.py --skill mail_send if the credential may be missing or invalid.

Use this skill when

• the user clearly wants actual delivery
• recipient, subject, and final body content are already known
• the send should go through a bound LegalGo mail account

Do not use this skill for:

• trade lead search
• email generation or rewriting
• sending when key facts are still missing

Input requirements

Require all of:

• account_id
• recipient email
• subject
• final email body

If any of these are missing, stop and ask for the missing send-critical field rather than sending.

Execution flow

1. Confirm the user wants actual delivery.
2. Ensure send-critical fields are present.
3. Run scripts/send_mail.py, or make an equivalent HTTP request that includes X-LegalGo-Key.
4. Report send result clearly.

Never imply an email was sent unless the API confirms success.

Output style

Return:

• recipient
• send status
• record id or message id if present

Keep the explanation short and practical.