SKILLEMALL.ai

BC douyin-sensitive-check

抖音/短视频违禁词和敏感词检测(本地词库版,无需 API Key)。每天首次使用自动从 GitHub 开源词库更新本地缓存,离线检测文案合规性。支持多词库合并(广告极限词、平台限流词、暴恐、色情、涉枪涉爆等)。使用场景:(1) 生成短视频文案后自动检测违禁词,(2) 用户要求检查某段文字是否有问题,(3) 抖音/快手/B站内容合规审核,(4) 直播话术自查。触发词:违禁词、敏感词、检测、合规、抖音风控、限流词、能不能发。

ClawHub Agent Skills author: MasterLin v1.0.2 5 files body ≈ 315 tokens Open the sourceclawhub.ai analyzed 3 d ago

As a process C 53/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions

IntegrationGitHubSoftware developmenttype and topics are labelled automatically from the skill text
JSON
Technical rating
B
88/100
safety, quality, tests
Safety 60%
99
Quality 40%
71
Run on models
none yet
Process rating
C
53/100
Has gaps
Result and completion w 14
0
Inputs and preconditions w 11
0
Failures and branches w 10
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 Obfuscation obf-hex-escape-chain scripts/update_words.py:40
    Escaped/char-code string obfuscation (quoted — discussed, not commanded)
    ("bigdata-labs/sensitive-stop-words", "涉枪涉爆违法信息关键词", "https://raw.githubusercontent.com/bigdata-labs/sensitive-stop-words/master/%E6%B6%89%E6%9E%AA%E6%B6%89%E7%88%86%E8%BF%9D%E6%B3%95%E4%BF%A1%E6%81%A
    quoted

Files scanned: 5. 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 53/100

  • 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
  • 100Tools and files. No external tools needed
  • 100Steps. 15 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 315 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
  • -41 reference files, but SKILL.md never points to them: the model will not open them
  • +1No license
  • +2Single-language instructions
  • +3Description length 212: enough signal without eating the budget
  • +4Structure: 7 headings
  • +3Step-by-step instructions: 15 items
  • +4Has examples (2 code blocks)
  • +3All 2 scripts are documented

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

External checks

ClawHub: clean
The artifacts show a coherent local sensitive-word checker with disclosed GitHub word-list updates and no evidence of credential use, hidden execution, or uploading checked text.
LLM: benign (high) · VirusTotal: · 29 May 2026