SKILLEMALL.ai

BF personal-wiki

个人知识库(LLM Wiki)操作 skill。 当用户提到以下意图时触发: - Ingest:处理新内容、更新知识库、"处理IMA新内容"、"处理印象笔记"、"处理raw里的文件"、"帮我ingest" - Query:查 wiki、"wiki里有没有关于XX"、"从知识库里找XX" - Lint:整理wiki、"检查知识库"、"清理一下wiki" - Visualize:可视化知识图谱、"看看wiki长什么样"、"生成关系图"、"知识库图谱" - Demo生成:基于 Demo Script 生成定制版本、"帮我做一个XX客户的demo"

ClawHub Agent Skills author: heavenchenggong v1.1.0 MIT-0 8 files body ≈ 2 594 tokens Open the sourceclawhub.ai analyzed 4 d ago

As a process F 37/100 · Will not run — References files that are not bundled: path.md, 来源类型

AnalyzerInfrastructureAI and agentstype and topics are labelled automatically from the skill text
JSON
Technical rating
B
87/100
safety, quality, tests
Safety 60%
100
Quality 40%
68
Run on models
none yet
Process rating
F
37/100
Will not run
References files that are not bundled: path.md, 来源类型
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: 8. 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: path.md
  • warning missing-ref reference to a missing file: 来源类型

Process rating: all ten parameters 37/100

Will not run. References files that are not bundled: path.md, 来源类型
  • 0Tools and files. 2 referenced file(s) missing: path.md, 来源类型
  • 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
  • 20When it triggers. No condition that starts the skill
  • 100Steps. 42 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 2594 tokens
  • 100Running it twice. No mutating operations
  • 100Progress reporting. Reports progress
  • 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)
  • +3Output format is not stated: the model decides each time
  • +1No license
  • +2Single-language instructions
  • +5Description quotes 9 example trigger phrases
  • +3Description length 273: enough signal without eating the budget
  • +4Structure: 44 headings
  • +3Step-by-step instructions: 42 items
  • +4Has examples (17 code blocks)

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

External checks

ClawHub: suspicious
The skill mostly matches a personal wiki workflow, but it asks the agent to persist an Evernote token in the user's shell profile and can modify remote Evernote notes, so it needs human review before install.
LLM: suspicious (high) · 20 Jul 2026