lumbox
Skill0 starsChanged 5 months agoMITView on GitHub
Give an AI agent its own email — create inboxes, send and receive email, wait for OTP codes, all self-service with no human signup. Use when an agent needs an email address to sign up for services, receive verification codes, or manage correspondence.
- Reads credentials
1 other project uses a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- kumard3/lumbox-skillsedited, first seen Jun 19, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 1
- kumard3/lumbox-skills★ 036% same
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 13
If LUMBOX_API_KEY is not set:
- Distinctive: line 34
All output is JSON.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Lumbox — email for AI agents
Lumbox gives agents real email inboxes. An agent can provision itself with no human account creation. This plugin also loads the Lumbox MCP server (87 tools).
Setup (self-service)
If LUMBOX_API_KEY is not set:
npx lumbox signup --source claude-codeCreates an org + API key, saved to ~/.lumbox/config.json. Tell the user where the key
lives. Export it as LUMBOX_API_KEY so the MCP server picks it up too.
Free tier: 3 inboxes, 5,000 inbound + 100 outbound emails/month. Signup limited to 3 orgs/hour per IP.
Core flows (CLI)
npx lumbox inbox create --name assistant # {id, address}
npx lumbox send --inbox <id> --to a@b.com --subject "Hi" --text "Hello"
npx lumbox wait-otp --inbox <id> --timeout 120 # blocks, prints {"code": "847291", ...}
npx lumbox inbox listAll output is JSON.
Core flows (REST)
Base https://api.lumbox.co, auth Authorization: Bearer $LUMBOX_API_KEY:
POST /v1/orgs self-signup (unauthenticated, returns api_key once)
POST /v1/inboxes create inbox
GET /v1/inboxes/:id/wait long-poll next email (parsed OTPs, links, category)
GET /v1/inboxes/:id/otp long-poll OTP, returns parsed code
POST /v1/inboxes/:id/send send
POST /v1/inboxes/:id/reply reply in-threadMCP tools
This plugin configures the lumbox MCP server automatically (87 tools): inboxes, email,
browser automation sessions, encrypted credential vault, TOTP 2FA, webhooks, custom
domains, contact lists. Prefer MCP tools when available; the CLI is the fallback.
Docs: https://docs.lumbox.co • Agent signup guide: https://docs.lumbox.co/docs/agent-signup
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

