skill-vexa_skill

This skill sends bots to Zoom, Google Meet, and Teams meetings to capture transcripts, recordings, and reports with self-hosted or cloud options.
  • Python

2.6k

GitHub Stars

2

Bundled Files

2 months ago

Catalog Refreshed

3 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill openclaw/skills --skill skill-vexa

  • _meta.json277 B
  • SKILL.md9.9 KB

Overview

This skill deploys autonomous meeting bots into Zoom, Google Meet, and Microsoft Teams to capture live transcripts, recordings, and produce post‑meeting reports. It can run self‑hosted or in the cloud and operates without calling external APIs. The tool is driven by a simple CLI and stores artifacts locally in a gitignored secrets directory.

How this skill works

You start a bot by pointing the CLI at a meeting URL or native meeting ID; the bot joins the meeting, streams audio (or polls transcripts), and records metadata. After the meeting it can generate a bundled report containing transcript segments, recordings, summaries, action items, and shareable links. Configuration and credentials are managed via env files and per‑endpoint secrets so you can switch between prod and local development easily.

When to use it

  • Capture live transcripts and real‑time meeting summaries
  • Record and archive meetings for compliance or notes retrieval
  • Automate post‑meeting report creation and action‑item extraction
  • Integrate with calendar tools to batch start bots for events
  • Run locally for private deployments without external APIs

Best practices

  • Always run secrets check before onboarding: node skills/vexa/scripts/onboard.mjs --check-secrets
  • Use endpoint files (vexa-prod.env, vexa-local.env) for per‑environment API keys and avoid pasting keys into shared logs
  • After starting a bot, proactively verify webhook configuration so finished meetings auto‑trigger reports
  • Prefer meetings:update for metadata changes instead of destructive delete; require explicit --confirm DELETE for deletions
  • Store recordings and generated reports in the memory/meetings directory and keep skills/vexa/secrets/ gitignored

Example use cases

  • Quickly join an ad hoc Meet link and stream transcript: bots:start --meeting_url "<url>" --bot_name "Claw" --language en
  • Batch start bots for calendar events: fetch events, extract links, then bots:start per event to auto‑capture sessions
  • Post‑meeting ingestion: create a report and write to memory/meetings with report or ingest scripts
  • Stream near‑real‑time transcript via Vexa WebSocket API for live captioning or monitoring
  • Generate shareable transcript links and download recording media for audits

FAQ

Run node skills/vexa/scripts/onboard.mjs --check-secrets; it returns {"secrets_ok": true} or false and guides next steps.

Can I run Vexa locally for development?

Yes — use the local endpoint in secrets/vexa-endpoints.json or set VEXA_BASE_URL to your local instance, then switch with env:use local.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational