SKILLEMALL.ai
GitHub ↗ RU Sign in

AF btpanel

宝塔面板 Skill，让 AI Agent 调用宝塔面板能力，管理网站、文件、数据库、Docker、计划任务及服务器环境，完成状态查询、故障排查和安全检查等日常运维操作；支持自动部署宝塔面板与 MCP 服务，并接入 Claude Code、Codex、Cursor、WorkBuddy 等 AI Agent。当用户需要通过 AI 管理服务器、安装宝塔面板或配置宝塔 MCP 服务时使用。

ClawHub Agent Skills author: aapanel.com v1.0.5 MIT-0 13 files body ≈ 1 504 tokens Open the sourceclawhub.ai↗ analyzed 3 d ago

As a process F 35/100 · Will not run — References files that are not bundled: assets/bt-skills/

ProcedureDockerAI and agentstype 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
90/100
safety, quality, tests
Safety 60%
100
Quality 40%
74
Run on models
none yet
Process rating
F
35/100
Will not run
References files that are not bundled: assets/bt-skills/
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: 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: assets/bt-skills/

Process rating: all ten parameters 35/100

Will not run. References files that are not bundled: assets/bt-skills/
  • 0Tools and files. 1 referenced file(s) missing: assets/bt-skills/
  • 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
  • 100Steps. 40 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 1504 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
  • +2Single-language instructions
  • +3Description length 193: enough signal without eating the budget
  • +4Structure: 15 headings
  • +3Step-by-step instructions: 40 items
  • +4Has examples (7 code blocks)
  • +4Reference files are cited in the instructions (1 of 1)
  • +3All 1 scripts are documented
  • +1License stated

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

External checks

ClawHub: suspicious
The skill is mostly coherent for BT panel administration, but some bundled troubleshooting/deployment instructions allow high-impact server changes with weak or misleading user-control language.
LLM: suspicious (high) · 21 Aug 2026