SKILLEMALL.ai
GitHub ↗ RU Sign in

AC blog-mini-kit-mys

管理 Blog System (FastAPI) 全部 32 个 API 端点：文章/标签/用户/评论/留言/说说/ 文件上传/健康检查/博客页面/后台管理。无认证公开 API，支持 CLI 子命令调用。

ClawHub Agent Skills author: yangaiwu v1.0.0 MIT-0 16 files body ≈ 1 948 tokens Open the sourceclawhub.ai↗ analyzed 3 d ago

管理 Blog System (FastAPI) 全部 32 个 API 端点：文章/标签/用户/评论/留言/说说/ 文件上传/健康检查/博客页面/后台管理。无认证公开 API，支持 CLI 子命令调用。

As a process C 63/100 · Has gaps — weak spots: inputs and preconditions, failures and branches, running it twice

IntegrationInfrastructuretype 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
A
91/100
safety, quality, tests
Safety 60%
100
Quality 40%
77
Run on models
none yet
Process rating
C
63/100
Has gaps
Inputs and preconditions w 11
0
Failures and branches w 10
0
Progress reporting w 2
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: 16. 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")
  • note frontmatter-key unknown frontmatter key "triggers"
  • note frontmatter-key unknown frontmatter key "tools"

Process rating: all ten parameters 63/100

  • 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. 14 mutating operations with no state check
  • 50When it triggers. No condition that starts the skill
  • 60Result and completion. Output format stated, no completion criterion
  • 100Tools and files. Tools declared in frontmatter
  • 100Steps. 45 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 1948 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 102: 120–800 characters recommended
  • +1No license
  • +2Single-language instructions
  • +4Structure: 28 headings
  • +3Step-by-step instructions: 45 items
  • +3Output format is stated explicitly
  • +4Has examples (15 code blocks)
  • +4Reference files are cited in the instructions (11 of 11)
  • +3All 1 scripts are documented

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

External checks

ClawHub: suspicious
This is a disclosed blog-management skill, but it can create, upload, and delete live public content with weak safeguards, so it needs review before installation.
LLM: suspicious (high) · 25 Aug 2026