vexa
Send bots to Zoom, Google Meet, and Microsoft Teams meetings. Get live transcripts, recordings, and reports. Works with Vexa Cloud or your own self-hosted instance.
Install via CLI (Recommended)
clawhub install openclaw/skills/skills/dmitriyg228/vexaChat-oriented interactions
Speak directly to the user as in a natural chat. Do not output internal reasoning, plan summaries, or procedural notes ("I need to...", "According to the skill...", "I will inform..."). Reply with only what you would say to the user — conversational, warm, and to the point.
Plain text formatting for meeting chat
When sending messages to meeting chat (Google Meet, Teams, etc.), always use plain text — no markdown. These chat surfaces do not render markdown, so asterisks, hash headers, backticks, and bullet dashes appear as ugly raw characters. Use line breaks and spacing for structure instead.
Use the bundled CLI:
node skills/vexa/scripts/vexa.mjs ...node skills/vexa/scripts/onboard.mjs ...node skills/vexa/scripts/ingest.mjs ...node skills/vexa/scripts/audit.mjs
Environment
Required: VEXA_API_KEY — get yours from https://vexa.ai/dashboard/api-keys
Set VEXA_API_KEY in your environment or create skills/vexa/secrets/vexa.env manually with:
VEXA_API_KEY=your_key_here
Optional: VEXA_BASE_URL (env override — takes priority over endpoint config)
Endpoint switching (prod / local dev)
The CLI supports named endpoints stored in secrets/vexa-endpoints.json. Default endpoints: prod (https://api.cloud.vexa.ai) and local (http://localhost:8000).
- List endpoints & active env:
node skills/vexa/scripts/vexa.mjs env:list - Switch to local dev:
node skills/vexa/scripts/vexa.mjs env:use local - Switch to prod:
node skills/vexa/scripts/vexa.mjs env:use prod - Add custom endpoint:
node skills/vexa/scripts/vexa.mjs env:set staging --url https://staging.vexa.ai - Remove endpoint:
node skills/vexa/scripts/vexa.mjs env:remove staging
Priority: VEXA_BASE_URL env var > vexa-endpoints.json active endpoint > default prod URL.
Secrets-first check (before any onboarding)
Always check first: node skills/vexa/scripts/onboard.mjs --check-secrets
- If output is
{"secrets_ok": true}→ secrets exist. Skip onboarding. Use normal flows. - If output is
{"secrets_ok": false}→ run onboarding. Loadreferences/onboarding-flow.md.
Webhook — proactive setup: Whenever secrets exist and you're working with Vexa, run node skills/vexa/scripts/onboard.mjs --check-webhook. If webhook_configured is false, advise adding the vexa mapping (see references/webhook-setup.md). For onboarding-only details (webhook requirements, pipeline validation, mock webhook), load references/onboarding-flow.md.
When secrets are missing: Direct the user to get their key from https://vexa.ai/dashboard/api-keys and set it up themselves. They should either set VEXA_API_KEY in their environment or create skills/vexa/secrets/vexa.env manually with VEXA_API_KEY=their_key_here. Do not ask users to paste API keys in chat.
Metadata
Not sure this is the right skill?
Describe what you want to build — we'll match you to the best skill from 16,000+ options.
Find the right skillPaste this into your clawhub.json to enable this plugin.
{
"plugins": {
"official-dmitriyg228-vexa": {
"enabled": true,
"auto_update": true
}
}
}