SKILLEMALL.ai
GitHub ↗ RU Sign in

BC vexa

Send Vexa bots to meetings and operate transcript workflows end-to-end (during and after meetings): parse meeting links, request/stop bots, read live/final transcripts, create basic meeting reports, set webhook delivery, and enrich meeting metadata. Use when a user drops a Google Meet/Teams link, asks to auto-join meetings from calendar events, or needs transcript retrieval/summarization/knowledge updates from Vexa. After a meeting ends, create a report with meeting info, transcript, and placeholders for summary/decisions/action items. Treat transcript purge (meeting delete) as destructive and require explicit confirmation.

modbender/skill-library-mcp Agent Skills author: modbender MIT 9 files body ≈ 1 647 tokens Open the sourcegithub.com↗ analyzed 2 d ago

Send Vexa bots to meetings and operate transcript workflows end-to-end (during and after meetings): parse meeting links, request/stop bots, read live/final…

As a process C 52/100 · Has gaps — weak spots: result and completion, inputs and preconditions, failures and branches

ProcedureData and analyticsPersonal productivitytype and topics are labelled automatically from the skill text
Runs in: OpenClaw Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) Goose OpenCode
JSON
Technical rating
B
84/100
safety, quality, tests
Safety 60%
80
Quality 40%
91
Run on models
none yet
Process rating
C
52/100
Has gaps
Result and completion w 14
0
Inputs and preconditions w 11
0
Failures and branches w 10
0
the three weakest of ten parameters · all ten

What is at stake

Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.

Exfiltration medium severity

Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.

If you install

The instructions or scripts send data out: environment variables, keys, file contents, chat history. You may never notice, because the agent performs the upload as "part of the task".

For the author

If the upload is not needed for the task, remove it: catalogs flag such skills and delist them. If it is needed, name the destination explicitly, say what leaves the machine, and give the user a switch.

How to improve

    For the model run — optional
    • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
    • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

    Guard findings · 4

    ✓ No critical or high findings

    Medium and low: 4
    • medium Exfiltration net-redirectable-api-key scripts/audit.mjs:38
      Helper sends the API key to a host configured by an environment variable — the key can be redirected to another server
      API key + configurable base URL from environment
    • medium Exfiltration net-redirectable-api-key scripts/ingest.mjs:40
      Helper sends the API key to a host configured by an environment variable — the key can be redirected to another server
      API key + configurable base URL from environment
    • medium Exfiltration net-redirectable-api-key scripts/onboard.mjs:28
      Helper sends the API key to a host configured by an environment variable — the key can be redirected to another server
      API key + configurable base URL from environment
    • medium Exfiltration net-redirectable-api-key scripts/vexa.mjs:53
      Helper sends the API key to a host configured by an environment variable — the key can be redirected to another server
      API key + configurable base URL from environment

    Files scanned: 9. Evidence is masked. Grey chips explain why severity was lowered.

    Against the Agent Skills spec

    ✓ No remarks against the Agent Skills spec

    Process rating: all ten parameters 52/100

    • 0Result and completion. Does not say what the result is
    • 0Inputs and preconditions. Does not say what the process needs to start
    • 0Failures and branches. Linear process with no failure handling
    • 0Progress reporting. Says nothing while it works
    • 60Tools and files. Uses tools (bash, web, node) that frontmatter does not declare
    • 70When it triggers. States when to use, but not when not to
    • 100Steps. 53 steps
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 1647 tokens
    • 100Running it twice. Mutating operations check current state
    • low The response is described with custom markup (8 tags): a typed call is more reliable

    Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

    Quality signals

    • +5Description has no quoted example phrases that should trigger the skill
    • +4Description does not say when NOT to use the skill (false activations)
    • +3Output format is not stated: the model decides each time
    • +1No license
    • +2Single-language instructions
    • +3Description length 631: enough signal without eating the budget
    • +4Structure: 14 headings
    • +3Step-by-step instructions: 53 items
    • +4Has examples (0 code blocks)
    • +4Reference files are cited in the instructions (3 of 3)
    • +3All 5 scripts are documented

    Quality base 70; lint remarks subtract, signals add up to 100. Result: 91.