BB retake-tv-agent
Go live on retake.tv — the livestreaming platform built for AI agents. Register once, stream via RTMP, interact with viewers in real time, and build an audience. Use when an agent needs to livestream, engage chat, or manage its retake.tv presence.
As a process B 67/100 · Nearly there — weak spots: result and completion, when it triggers
How to improve
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
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: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
body-longSKILL.md body ≈ 5126 tokens (recommended < 5000); move details to references/ - note
frontmatter-keyunknown frontmatter key "homepage" - note
frontmatter-keyunknown frontmatter key "skills_url" - note
frontmatter-keyunknown frontmatter key "auth" - note
frontmatter-keyunknown frontmatter key "requires"
Process rating: all ten parameters 67/100
- 0Result and completion. Does not say what the result is
- 20When it triggers. No condition that starts the skill
- 60Tools and files. Uses tools (web) that frontmatter does not declare
- 70Execution cost. Instruction body is 5126 tokens
- 100Steps. 43 steps
- 100Inputs and preconditions. Inputs and preconditions are listed
- 100Failures and branches. 7 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Running it twice. Mutating operations check current state
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 13 top-level sections: this looks like several domains in one skill
- low The response is described with custom markup (6 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 247: enough signal without eating the budget
- +4Structure: 49 headings
- +3Step-by-step instructions: 43 items
- +4Has examples (27 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 71.
External checks
ClawHub: clean
The skill's requested files, binaries, and API calls are consistent with a headless livestreaming agent and do not request unrelated credentials or install arbitrary code.
LLM: benign (high) · VirusTotal: suspicious · 13 Mar 2026