SKILLEMALL.ai
GitHub ↗ RU Sign in

BF guaikei-douyin-collection

当用户做短视频营销或投放决策需要数据支撑时，使用本技能：搜关键词看赛道内容、抓博主作品估账号价值、读评论判断口碑、查热榜蹭对热点。用户说"这个号值不值得投""这条视频口碑如何"时也要用，即使没说"抖音"。不负责实际投放与视频制作。

ClawHub Agent Skills author: engheng-art v1.0.0 MIT-0 34 files body ≈ 922 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 documentstype 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%
72
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
  • note frontmatter-key unknown frontmatter key "title"

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. 26 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 922 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 115: 120–800 characters recommended
  • +3Output format is not stated: the model decides each time
  • +2Single-language instructions
  • +5Description quotes 2 example trigger phrases
  • +4Structure: 13 headings
  • +3Step-by-step instructions: 26 items
  • +4Has examples (7 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: 72.

External checks

ClawHub: suspicious
The skill mostly matches its Douyin data-collection purpose, but its activation rules are too broad and its runtime token-error behavior contradicts its own review-facing claims.
LLM: suspicious (high) · 19 Aug 2026