SKILLEMALL.ai

BD WeChat Knowledge Base

微信最好用的知识库管家 — 发链接就完事! 📱 支持视频号|抖音|小红书|公众号|本地文件 🚀 一站式管理:链接解析 → 自动下载 → 上传腾讯文档 → 智能建索引 🤖 Agent 自动化,无需手动操作,把散落各处的内容变成你的知识资产 ☁️ 腾讯文档集成,上传后直接在线播放、预览、分享 ⚠️ 新用户首次使用需完成腾讯文档授权(详见文档) 触发词:知识库、保存链接、存到知识库、帮我存这个、下载这个视频/文章

ClawHub Agent Skills author: 寒武纪智能Cambrian Intelligence v2.2.5 MIT-0 2 files body ≈ 1 073 tokens Open the sourceclawhub.ai analyzed 2 d ago

微信最好用的知识库管家 — 发链接就完事! 📱 支持视频号|抖音|小红书|公众号|本地文件 🚀 一站式管理:链接解析 → 自动下载 → 上传腾讯文档 → 智能建索引 🤖 Agent 自动化,无需手动操作,把散落各处的内容变成你的知识资产 ☁️ 腾讯文档集成,上传后直接在线播放、预览、分享 ⚠️…

As a process D 39/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions

ReferenceAI and agentstype and topics are labelled automatically from the skill text
JSON
Technical rating
B
86/100
safety, quality, tests
Safety 60%
100
Quality 40%
65
Run on models
none yet
Process rating
D
39/100
Unfinished process
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 · 0

✓ No critical or high findings

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

Against the Agent Skills spec

  • warning name-format name should be kebab-case (lowercase letters, digits, hyphens)
  • warning description-no-when description does not say WHEN to use the skill (no "use when")

Process rating: all ten parameters 39/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
  • 30Running it twice. 1 mutating operations with no state check
  • 40Consistency. Frontmatter name (WeChat Knowledge Base) differs from the folder (wechat-knowledge)
  • 60Tools and files. Uses tools (web) that frontmatter does not declare
  • 100Steps. 28 steps
  • 100Execution cost. Instruction body is 1073 tokens

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
  • -217 emoji in the instructions: noise for the model
  • +1No license
  • +2Single-language instructions
  • +3Description length 208: enough signal without eating the budget
  • +4Structure: 22 headings
  • +3Step-by-step instructions: 28 items
  • +4Has examples (10 code blocks)

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

External checks

ClawHub: suspicious
The skill’s goal of saving content to a Tencent or WeChat knowledge base is coherent, but broad triggers and unclear temporary local-copy handling create a real risk of unintended data movement.
LLM: suspicious (medium) · VirusTotal: · 14 Jun 2026