SKILLEMALL.ai

BD meeting-assistant

Zoom/Teams/Meet 远程会议AI助手。Use when: user asks to join a meeting, monitor a meeting, record a meeting, assist in a medical consultation, help doctor-patient communication, transcribe meeting audio, analyze meeting screenshots, send chat in meeting, or provide real-time meeting assistance. The agent joins the meeting autonomously as a bot, performs real-time speech-to-text, vision analysis via Claude AI, and participants can communicate with the agent directly via meeting chat.

ClawHub Agent Skills author: Rongze Gao v1.0.0 MIT-0 24 files body ≈ 1 445 tokens Open the sourceclawhub.ai analyzed 3 d ago

As a process D 49/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions

AnalyzerAI and agentstype and topics are labelled automatically from the skill text
JSON
Technical rating
B
87/100
safety, quality, tests
Safety 60%
90
Quality 40%
83
Run on models
none yet
Process rating
D
49/100
Unfinished process
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

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 · 10

    ✓ No critical or high findings

    Medium and low: 10
    • low Secrets in code secret-high-entropy-token config.json:44
      High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
      "vexa_api_key": "dGos…iIc",
      quoted
    • low Secrets in code secret-high-entropy-token docs/agent-usage.md:88
      High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
      KEY  = "dGos…iIc"
      quoted
    • low Secrets in code secret-high-entropy-token docs/agent-usage.md:192
      High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
      "vexa_api_key": "dGos…iIc",
      quoted
    • low Secrets in code secret-labelled-token docs/api-reference.md:6
      Labelled token / key literal (vendor format unknown — verify it is not a live credential) (quoted — discussed, not commanded)
      Authentication: `X-API-Key: dGos…iIc`
      quoted
    • low Secrets in code secret-high-entropy-token docs/api-reference.md:6
      High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
      Authentication: `X-API-Key: dGos…iIc`
      quoted
    • low Secrets in code secret-password-literal docs/api-reference.md:6
      Hard-coded password / key literal (may be an example) (quoted — discussed, not commanded)
      Authentication: `X-API-Key: dGos…iIc`
      quoted
    • low Secrets in code secret-high-entropy-token docs/setup.md:62
      High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
      Current token: `dGos…iIc`
      quoted
    • low Secrets in code secret-high-entropy-token docs/setup.md:67
      High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
      $h = @{ 'X-API-Key' = 'dGos…iIc' }
      quoted
    • low Secrets in code secret-high-entropy-token docs/setup.md:149
      High-entropy token-like string (may be an id, hash or a credential) (documentation table row)
      | `ZOOM_CLIENT_SECRET` | `IlvP…xUs` | Zoom Marketplace app credential |
      table
    • low Secrets in code secret-high-entropy-token docs/troubleshooting.md:221
      High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
      -Headers @{'X-API-Key'='dGos…iIc'} -UseBasicParsing
      quoted

    Files scanned: 24. 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 49/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
    • 20When it triggers. No condition that starts the skill
    • 40Consistency. Frontmatter name (meeting-assistant) differs from the folder (meeting-assistant-eva)
    • 100Tools and files. No external tools needed
    • 100Steps. 17 steps
    • 100Execution cost. Instruction body is 1445 tokens
    • 100Running it twice. No mutating operations
    • low 11 top-level sections: this looks like several domains in one skill

    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
    • -2localhost URLs: will not work for another user
    • -37 of 10 scripts are never mentioned in SKILL.md
    • +1No license
    • +2Single-language instructions
    • +3Description length 479: enough signal without eating the budget
    • +4Structure: 19 headings
    • +3Step-by-step instructions: 17 items
    • +4Has examples (10 code blocks)
    • +4Reference files are cited in the instructions (2 of 8)

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

    External checks

    ClawHub: suspicious
    This meeting assistant is mostly purpose-aligned, but it needs review because it records and analyzes sensitive meetings by default, exposes live-looking credentials, persists meeting artifacts, and can post or capture more broadly than users may expect.
    LLM: suspicious (high) · VirusTotal: · 29 May 2026