SKILLEMALL.ai

BF blog-manager-kit

封装 Blog System REST API 的管理 skill,提供文章/标签/用户/评论/留言/说说/上传/健康检查 共 8 模块 28 个子命令的命令行能力。无认证(公开 API)。

ClawHub Agent Skills author: yangaiwu v0.1.0 MIT-0 6 files body ≈ 2 933 tokens Open the sourceclawhub.ai analyzed 2 d ago

封装 Blog System REST API 的管理 skill,提供文章/标签/用户/评论/留言/说说/上传/健康检查 共 8 模块 28 个子命令的命令行能力。无认证(公开 API)。

As a process F 45/100 · Will not run — References files that are not bundled: references/api-reference.md, templates/test-vars.json

IntegrationInfrastructuretype and topics are labelled automatically from the skill text
JSON
Technical rating
B
84/100
safety, quality, tests
Safety 60%
100
Quality 40%
61
Run on models
none yet
Process rating
F
45/100
Will not run
References files that are not bundled: references/api-reference.md, templates/test-vars.json
Tools and files w 18
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.
  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: 6. 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: references/api-reference.md
  • warning missing-ref reference to a missing file: templates/test-vars.json
  • note frontmatter-key unknown frontmatter key "triggers"
  • note frontmatter-key unknown frontmatter key "tools"

Process rating: all ten parameters 45/100

Will not run. References files that are not bundled: references/api-reference.md, templates/test-vars.json
  • 0Tools and files. 2 referenced file(s) missing: references/api-reference.md, templates/test-vars.json
  • 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
  • 30Running it twice. 37 mutating operations with no state check
  • 50When it triggers. No condition that starts the skill
  • 60Result and completion. Output format stated, no completion criterion
  • 100Steps. 38 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 2933 tokens
  • low 11 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

  • +5Description has no quoted example phrases that should trigger the skill
  • +4Description does not say when NOT to use the skill (false activations)
  • +3Description length 95: 120–800 characters recommended
  • +1No license
  • +2Single-language instructions
  • +4Structure: 56 headings
  • +3Step-by-step instructions: 38 items
  • +3Output format is stated explicitly
  • +4Has examples (36 code blocks)

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

External checks

ClawHub: suspicious
This appears to be a real blog-management tool, but it can change or delete public blog content and upload local files to an unauthenticated HTTP service with too little scoping or confirmation.
LLM: suspicious (high) · 23 Aug 2026