SKILLEMALL.ai
GitHub ↗ RU Sign in

BF guaikei-douyin-data-feed

当用户问"抖音搜一下""这个博主最近发了什么""这条视频评论怎么看""今天抖音热搜是什么"时，使用本技能，分别对应搜索、博主作品、评论、热榜四项能力。用户换口语问法（"网上火啥""评论区啥风向"）时同样触发。不适用于其他平台或视频发布。

ClawHub Agent Skills author: engheng-art v1.0.0 MIT-0 34 files body ≈ 834 tokens Open the sourceclawhub.ai↗ analyzed 3 d ago

当用户问"抖音搜一下""这个博主最近发了什么""这条视频评论怎么看""今天抖音热搜是什么"时，使用本技能，分别对应搜索、博主作品、评论、热榜四项能力。用户换口语问法（"网上火啥""评论区啥风向"）时同样触发。不适用于其他平台或视频发布。

As a process F 35/100 · Will not run — References files that are not bundled: assets/*.schema.json

ProcedureWriting and documentsMedia and videotype and topics are labelled automatically from the skill text
Runs in: OpenClaw Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) Goose OpenCode
JSON
Technical rating
B
89/100
safety, quality, tests
Safety 60%
100
Quality 40%
73
Run on models
none yet
Process rating
F
35/100
Will not run
References files that are not bundled: assets/*.schema.json
Tools and files w 18
0
Result and completion w 14
0
Inputs and preconditions w 11
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.
  2. The text references files that are not there: add them or drop the references.
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: 34. 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")
  • warning missing-ref reference to a missing file: assets/*.schema.json

Process rating: all ten parameters 35/100

Will not run. References files that are not bundled: assets/*.schema.json
  • 0Tools and files. 1 referenced file(s) missing: assets/*.schema.json
  • 0Result and completion. Does not say what the result is
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 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
  • 100Steps. 32 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 834 tokens
  • 100Running it twice. No mutating operations
  • low 12 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

  • +4Description does not say when NOT to use the skill (false activations)
  • +3Description length 118: 120–800 characters recommended
  • +3Output format is not stated: the model decides each time
  • +2Single-language instructions
  • +5Description quotes 4 example trigger phrases
  • +4Structure: 13 headings
  • +3Step-by-step instructions: 32 items
  • +4Has examples (5 code blocks)
  • +4Reference files are cited in the instructions (2 of 2)
  • +1License stated

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

External checks

ClawHub: suspicious
This skill mostly does what it says, but its broad triggers, automatic data logging, and runtime token-error messages need human review before installation.
LLM: suspicious (high) · 19 Aug 2026