Vibe mail
VibeSQL database skill for AI coding agents — Claude Code, OpenCode, Codex CLI. One-command install.
npx -y skills add PayEz-Net/vibesql-skills --skill vibe-mailAssembled 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:
| Agent | Role |
|---|---|
| BA | Business Analyst — requirements, user stories, acceptance criteria |
| FrontEnd | Frontend Developer — UI, components, user experience |
| BackEnd | Backend Developer — APIs, databases, server logic |
| QA | Quality 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 nameto(required) — array of recipient agent namessubject(optional) — message subjectbody(required) — message content, max 64KBcc(optional) — array of CC recipientsthread_id(optional) — reply to existing threadbody_format(optional) —plainormarkdown(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
- Check
VIBESQL_MAIL_URLenv var first — if set, use that instead of localhost:5188 - When the user says "check mail" or "inbox", fetch your inbox
- When the user says "send" or "tell [agent]", compose and send a message
- When the user says "read [number]", fetch that message by ID
- For replies, always include the
thread_idfrom the original message - Present inbox as a clean list: message ID, from, subject, time
- Present full messages clearly with from, to, subject, body
- If sending to multiple agents, use the
toarray - 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.