AB open-utter
Headless Google Meet bot that joins meetings and captures live captions as transcripts.
As a process B 69/100 · Nearly there — weak spots: result and completion, consistency, running it twice
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 · 0
✓ No critical or high findings
Files scanned: 6. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- note
frontmatter-keyunknown frontmatter key "homepage"
Process rating: all ten parameters 69/100
- 0Result and completion. Does not say what the result is
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 10 mutating operations with no state check
- 40Consistency. Frontmatter name (open-utter) differs from the folder (openutter)
- 60Tools and files. Uses tools (bash, read) that frontmatter does not declare
- 100Steps. 30 steps
- 100When it triggers. States when to use and when not to
- 100Inputs and preconditions. Inputs and preconditions are listed
- 100Failures and branches. 5 branches, has a failure section
- 100Execution cost. Instruction body is 2369 tokens
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 12 top-level sections: this looks like several domains in one skill
- low The response is described with custom markup (3 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)
- +3Description length 87: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +4Structure: 19 headings
- +3Step-by-step instructions: 30 items
- +4Has examples (10 code blocks)
- +3All 4 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 83.
External checks
ClawHub: suspicious
This is a disclosed Google Meet transcript bot, but it needs Review because it can capture and share sensitive meeting visuals/transcripts, reuse a saved Google session, disguise browser automation, and has an unsafe shell command path.
LLM: suspicious (high) · VirusTotal: · 29 May 2026