SKILLEMALL.ai
RU Sign in

BC meta-cloudbase

由 model-distillation 从教师技能 cloudbase 蒸馏并增强的超越型元技能。 蒸馏其全栈开发部署体系(Web/小程序/移动/云函数/CloudRun/NoSQL·MySQL/鉴权/AI Agent) 与"先识别场景→读对应源技能→再写码"的路由契约，叠加自验证、自我反思、super-agent 编排与持续自进化闭环，并在常见失败根因(鉴权漏配/SDK边界误用)上做对抗验证，逐步超越教师。

ClawHub Agent Skills author: qq435912743 v1.0.0 MIT-0 5 files body ≈ 514 tokens Open the sourceclawhub.ai↗ analyzed 36 h ago

由 model-distillation 从教师技能 cloudbase 蒸馏并增强的超越型元技能。 蒸馏其全栈开发部署体系(Web/小程序/移动/云函数/CloudRun/NoSQL·MySQL/鉴权/AI Agent)…

As a process C 53/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions

IntegrationMySQLAI 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
B
88/100
safety, quality, tests
Safety 60%
100
Quality 40%
69
Run on models
none yet
Process rating
C
53/100
Has gaps
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: 5. 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 "agent_created"
  • note frontmatter-key unknown frontmatter key "visibility"

Process rating: all ten parameters 53/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
  • 100Tools and files. No external tools needed
  • 100Steps. 20 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 514 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
  • +4No input/output examples
  • +1No license
  • +2Single-language instructions
  • +3Description length 207: enough signal without eating the budget
  • +4Structure: 7 headings
  • +3Step-by-step instructions: 20 items
  • +3All 1 scripts are documented

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

External checks

ClawHub: suspicious
The skill is not malicious, but it asks agents to handle live CloudBase deployment and database work without enough scoping or safety controls.
LLM: suspicious (high) · 14 Aug 2026