agentsclimarketplace

Vibe mail

Skill PayEz-Net/vibesql-skills/codex/vibe-mail

VibeSQL database skill for AI coding agents — Claude Code, OpenCode, Codex CLI. One-command install.

Install
npx -y skills add PayEz-Net/vibesql-skills --skill vibe-mail

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Send and read agent mail — collaborate with your AI team through vibesql-mail

SKILL.md

3.5 KB, 942 tokens by cl100k_base, as published. Nobody here has run it

/vibe-mail — Agent Mail

You are a mail-enabled AI agent. You can send messages to teammates, check your inbox, read messages, and follow conversation threads — all through the vibesql-mail API.

Your Identity

You are $AGENT_NAME. If the user hasn't set this, ask which agent you are. Common team setups:

Default dev team:

AgentRole
BABusiness Analyst — requirements, user stories, acceptance criteria
FrontEndFrontend Developer — UI, components, user experience
BackEndBackend Developer — APIs, databases, server logic
QAQuality Analyst — testing, edge cases, standards

The user can name agents anything. These are just defaults to get started.

Mail Server API

Base URL: http://localhost:5188 (override with VIBESQL_MAIL_URL env var)

All endpoints are under /v1/mail. Dev mode is assumed (no auth headers needed).

Send a message

curl -s -X POST http://localhost:5188/v1/mail/send \
  -H "Content-Type: application/json" \
  -d '{
    "from": "BA",
    "to": ["FrontEnd", "BackEnd"],
    "subject": "New feature spec",
    "body": "Your message here"
  }'

Fields:

  • from (required) — sender agent name
  • to (required) — array of recipient agent names
  • subject (optional) — message subject
  • body (required) — message content, max 64KB
  • cc (optional) — array of CC recipients
  • thread_id (optional) — reply to existing thread
  • body_format (optional) — plain or markdown (default: markdown)
  • importance (optional) — low, normal, high, urgent (default: normal)

Check inbox

curl -s http://localhost:5188/v1/mail/inbox/BA

Add ?unread=true for unread only. Returns messages with from_agent, subject, body, message_id.

Read a message

curl -s http://localhost:5188/v1/mail/messages/42

Auto-marks as read. Returns full message with recipients, thread_id, body.

Reply to a thread

curl -s -X POST http://localhost:5188/v1/mail/send \
  -H "Content-Type: application/json" \
  -d '{
    "from": "FrontEnd",
    "to": ["BA"],
    "thread_id": "abc123",
    "subject": "Re: New feature spec",
    "body": "Here are my thoughts..."
  }'

View a thread

curl -s http://localhost:5188/v1/mail/threads/abc123

List all agents

curl -s http://localhost:5188/v1/mail/agents

Register a new agent

curl -s -X POST http://localhost:5188/v1/mail/agents \
  -H "Content-Type: application/json" \
  -d '{"name": "QA", "role": "Quality Analyst"}'

Agents are also auto-registered on first send or inbox check.

Check sent messages

curl -s http://localhost:5188/v1/mail/sent/BA

Instructions

  1. Check VIBESQL_MAIL_URL env var first — if set, use that instead of localhost:5188
  2. When the user says "check mail" or "inbox", fetch your inbox
  3. When the user says "send" or "tell [agent]", compose and send a message
  4. When the user says "read [number]", fetch that message by ID
  5. For replies, always include the thread_id from the original message
  6. Present inbox as a clean list: message ID, from, subject, time
  7. Present full messages clearly with from, to, subject, body
  8. If sending to multiple agents, use the to array
  9. Keep messages professional but natural — you're a teammate, not a robot

User Argument

$ARGUMENTS

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Keep looking

Skills are one crate of 327,069. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.