BC video-call-agent
Start a video call with a real-time AI avatar using the Runway Characters API. The agent sends the user a call invite link — for standups, urgent alerts, check-ins, or any conversation that's better face-to-face.
Start a video call with a real-time AI avatar using the Runway Characters API.
As a process C 55/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
- 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 · 3
✓ No critical or high findings
Medium and low: 3
-
low Exfiltration
exfil-webhook-urlSKILL.md:47Webhook / callback URL commonly used for exfiltration (verify the destination) (placeholder value)- **Tunnel**: `https://xxxx.trycloudflare.com` — shareable, works from phone
placeholder -
low Exfiltration
exfil-webhook-urlSKILL.md:360Webhook / callback URL commonly used for exfiltration (verify the destination) (placeholder value)"tunnel": "https://xxxx.trycloudflare.com/call/abc-123-def"
placeholder -
low Exfiltration
exfil-webhook-urlSKILL.md:375Webhook / callback URL commonly used for exfiltration (verify the destination) (placeholder value)> **Join the call:** https://xxxx.trycloudflare.com/call/abc-123-def
placeholder
Files scanned: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - warning
body-longSKILL.md body ≈ 5444 tokens (recommended < 5000); move details to references/
Process rating: all ten parameters 55/100
- 0Result and completion. Does not say what the result is
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Inputs and preconditions. Does not say what the process needs to start
- 60Tools and files. Uses tools (bash, web) that frontmatter does not declare
- 70Execution cost. Instruction body is 5444 tokens
- 85Steps. 57 steps, 1 vague phrases
- 100Failures and branches. 15 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Running it twice. Mutating operations check current state
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- 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)
- +3Output format is not stated: the model decides each time
- -2localhost URLs: will not work for another user
- +1No license
- +2Single-language instructions
- +3Description length 212: enough signal without eating the budget
- +4Structure: 21 headings
- +3Step-by-step instructions: 57 items
- +4Has examples (23 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 60.