AB huawei-cloud-cce-container-migration-planner
Huawei Cloud CCE container migration planning skill using Python SDK dispatcher for read-only resource inventory, dependency mapping, migration batch design, risk assessment, and rollback strategy generation. Use this skill when the user wants to: (1) plan CCE cluster migration including same-region, cross-region, multi-cluster, hybrid cloud, version upgrade, or architecture adjustment, (2) inventory source cluster workloads, networking, storage, and configuration resources, (3) build dependency matrices and migration batches, (4) generate risk lists, rollback strategies, validation plans, and manual confirmation checklists. Trigger: user mentions "container migration", "容器迁移", "migration planning", "迁移规划", "migration assessment", "迁移评估", "workload migration", "工作负载迁移", "cluster migration", "集群迁移", "migration plan", "迁移方案", "migration inventory", "迁移盘点", "dependency mapping", "依赖梳理", "migration batch", "迁移批次", "migration risk", "迁移风险"
Huawei Cloud CCE container migration planning skill using Python SDK dispatcher for read-only resource inventory, dependency mapping, migration batch design…
As a process B 74/100 · Nearly there — weak spots: running it twice
How to improve
- 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: 1. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- note
frontmatter-keyunknown frontmatter key "id"
Process rating: all ten parameters 74/100
- 30Running it twice. 11 mutating operations with no state check
- 50Failures and branches. 0 branches, has a failure section
- 60Tools and files. Uses tools (bash, web, python, node) that frontmatter does not declare
- 60Result and completion. Output format stated, no completion criterion
- 70Inputs and preconditions. Inputs and preconditions are listed
- 85Steps. 49 steps, 1 vague phrases
- 100When it triggers. States when to use and when not to
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 3856 tokens
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 10 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)
- +3Description length 948: 120–800 characters recommended
- +1No license
- +2Single-language instructions
- +5Description quotes 11 example trigger phrases
- +4Structure: 20 headings
- +3Step-by-step instructions: 49 items
- +3Output format is stated explicitly
- +4Has examples (3 code blocks)
- +4Reference files are cited in the instructions (3 of 3)
- +3All 1 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 95.