Menu
Discord: send/receive server messages and DMs; reply to source=discord notifications. Requires daemon.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Use for any Microsoft account, personal or work (Outlook.com, Hotmail, Live, Microsoft 365); preferred over email-client for Microsoft accounts. Graph-based mail (read/send/reply/forward, drafts, flag/categorize, move/archive, folders, attachments, block senders), calendar and meetings, Microsoft Teams (chats, channels, presence), and new-mail/Teams notifications. Requires daemon.
Browse, navigate, click, fill forms, screenshot, or scrape web pages with a stealth (Camoufox) browser.
Design judgment and UI copy for building Vesta dashboard widgets that feel considered rather than templated, within the fixed design system.
Use before building or modifying the user's dashboard: widgets, pages, layouts, custom UI. Understand what the user wants, design it, write a spec, then dispatch the dashboard-builder to build it.
Use when someone who doesn't have their own vesta asks what vesta is, how to get one, or hints they want in. Vesta is invite-only: you gatekeep and build desire through scarcity, draw out what they want, then sell vesta as indispensable to their goals and set them up end-to-end in chat. Not for the owner, who already has one.
Talk to vestad, the host daemon that runs this container. Register a background service to get a port, build public URLs, update vestad to the latest release, check its version, and read gateway logs. Use when a skill needs an inbound port or a shareable link, when the user asks to update Vesta, or when debugging gateway/container issues.
| name | discord |
| description | Discord: send/receive server messages and DMs; reply to source=discord notifications. Requires daemon. |
Setup: follow SETUP.md (bot token, MESSAGE CONTENT intent, invite url).
Background: screen -dmS discord discord serve --notifications-dir ~/agent/notifications
discord send 123456789012345678 "message" # post to a channel id
discord send @987654321098765432 "message" # DM a user by id
discord send 1234... "reply" --reply 987654321098765432 # reference-reply to a message
discord channels # servers and their text channels
discord history 1234... --limit 20 # recent messages, oldest first
A source=discord notification carries channel_id and message_id.
server field): discord send <channel_id> "reply".discord send <channel_id> "reply" --reply <message_id> so the reply references the message it answers.discord channels or a notification's channel_id, user ids from a notification's sender_id (there is no name lookup; ask the user to copy an id from Discord if needed).from_bot=true. Tune with the notifications skill (fields: server, channel_name, sender, mention, from_bot).**bold**, *italic*, `code`, plain urls auto-link.~/.discord/credentials.json; re-run discord authenticate to rotate it.[Which servers, channels, and people matter, when to use reference replies, tone per server]