Menu
Discover and install new capabilities from the GitHub skill registry.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
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.
Baseado na classificação ocupacional SOC
| name | skills-registry |
| description | Discover and activate new capabilities from the local skill registry. |
Every Vesta skill ships on disk under ~/agent/skills/. There is no download step: a skill
is either active (linked so you can use it) or inactive. Activating one records it for the
next restart; deactivating one removes that record.
~/agent/skills/skills-registry/scripts/skills-search # list all available skills
~/agent/skills/skills-registry/scripts/skills-search email # search by keyword
Active skills are marked [active].
~/agent/skills/skills-registry/scripts/skills-activate <name>
After activating, restart yourself with the restart_vesta tool to load the new skill into context.
~/agent/skills/skills-registry/scripts/skills-deactivate <name>
python3 -m json.tool ~/agent/data/config.json | sed -n '/"active_skills"/,/]/p'
Many skills ship a command line tool in cli/. Install it, or reinstall it after
you edit it, as an editable uv tool. That links the command to its source, so
your edits and upstream updates take effect on the command's next run:
uv tool install --editable ~/agent/skills/<name>/cli
Never install a skill's CLI with uv pip install -e or pip install -e. Run from
~/agent those resolve the engine venv, dropping the skill's command into
~/agent/.venv/bin, which leads your PATH and shadows the real tool: the command
and its daemon then break with an import error. uv tool install keeps the CLI
isolated and on ~/.local/bin, so use it every time.
active_skills in ~/agent/data/config.json; the boot entrypoint links it into ~/.claude/skillsSETUP.md