BB tiktok-video-search
Search TikTok videos by keyword with Gecho Bridge MCP and return video metadata, creators, engagement metrics, and links. Requires the Gecho Chrome extension, an active TikTok session, and the Gecho Bridge MCP server.
Search TikTok videos by keyword with Gecho Bridge MCP and return video metadata, creators, engagement metrics, and links.
As a process B 70/100 · Nearly there — weak spots: when it triggers, running it twice
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- For Hermes the description must be one sentence under 60 characters; move the conditions to a "When to Use" section.
- 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: 3. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-long-hermesdescription is 217 chars; the Hermes authoring standard requires ≤ 60 (one sentence, ending with a period) - warning
description-no-whenneither description nor a "## When to Use" section says when to use the skill
Process rating: all ten parameters 70/100
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 1 mutating operations with no state check
- 60Tools and files. Uses tools (bash, web) that frontmatter does not declare
- 60Result and completion. Output format stated, no completion criterion
- 60Consistency. The Hermes dialect needs category and tags
- 70Execution cost. Instruction body is 4019 tokens
- 100Steps. 78 steps
- 100Inputs and preconditions. Inputs and preconditions are listed
- 100Failures and branches. 5 branches, has a failure section
- 100Progress reporting. Reports progress
- low 17 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)
- +1No license
- +2Single-language instructions
- +3Description length 217: enough signal without eating the budget
- +4Structure: 28 headings
- +3Step-by-step instructions: 78 items
- +3Output format is stated explicitly
- +4Has examples (11 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 69.