SKILLEMALL.ai

BC tiktok-live-mon

TikTok Live stream monitoring and recording automation. Uses Playwright for visual detection and network traffic monitoring to capture FLV stream URLs. Supports automatic live status checks, stream recording to disk, and notification integration.

ClawHub Agent Skills author: Karim Kiki v1.0.0 MIT-0 7 files · 2 scripts body ≈ 149 tokens Open the sourceclawhub.ai analyzed 3 d ago

As a process C 61/100 · Has gaps — weak spots: result and completion, when it triggers, failures and branches

IntegrationPlaywrightInfrastructureMarketingtype and topics are labelled automatically from the skill text
JSON
Technical rating
B
88/100
safety, quality, tests
Safety 60%
99
Quality 40%
72
Run on models
none yet
Process rating
C
61/100
Has gaps
Result and completion w 14
0
Failures and branches w 10
0
Progress reporting w 2
0
the three weakest of ten parameters · all ten

How to improve

  1. Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
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 · 1

✓ No critical or high findings

Medium and low: 1
  • low Dangerous commands cmd-privilege tiktok-get-stream.js:86
    Privilege escalation / world-writable permissions (detector / deny-list definition; string literal in code, not executed)
    args: ['--no-sandbox', '--disable-setuid-sandbox', '--disable-gpu', '--disable-dev-shm-usage']
    detectorcode literal

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

Against the Agent Skills spec

  • warning description-no-when description does not say WHEN to use the skill (no "use when")

Process rating: all ten parameters 61/100

  • 0Result and completion. Does not say what the result is
  • 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
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 100Tools and files. No external tools needed
  • 100Steps. 6 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 149 tokens
  • 100Running it twice. No mutating operations

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 246: enough signal without eating the budget
  • +4Structure: 4 headings
  • +3Step-by-step instructions: 6 items
  • +4Has examples (1 code blocks)

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

External checks

ClawHub: suspicious
This skill mostly does what it claims, but unsafe shell command handling can let crafted input run local commands on the user's machine.
LLM: suspicious (high) · VirusTotal: · 29 May 2026