SKILLEMALL.ai
GitHub ↗ RU Sign in

DC huawei-cloud-cce-cluster-migrator

End-to-end Kubernetes cluster migration assistant for migrating self-hosted, on-premise, or third-party cloud Kubernetes workloads to Huawei Cloud Cloud Container Engine (CCE). Covers source cluster assessment, CCE cluster sizing, container image synchronization to SWR, multi-type persistent volume (PV/PVC) migration across EVS, SFS Turbo, and OBS, ConfigMap and Secret migration with endpoint adaptation, Velero workload backup and restore, and smooth traffic cutover with Huawei Cloud Dedicated ELB and DNS. Triggers include: "CCE集群迁移", "Kubernetes迁移到CCE", "自建K8s迁移华为云", "K8s跨云迁移", "CCE Workload Migration", "migrate kubernetes to CCE", "migrate k8s to huawei cloud cce", "cce cluster migrator".

ClawHub Agent Skills author: huaweicloudskill v1.0.0 MIT-0 30 files · 2 scripts body ≈ 3 128 tokens Open the sourceclawhub.ai↗ analyzed 6 d ago

End-to-end Kubernetes cluster migration assistant for migrating self-hosted, on-premise, or third-party cloud Kubernetes workloads to Huawei Cloud Cloud…

As a process C 61/100 · Has gaps — weak spots: result and completion, when it triggers, running it twice

ProcedureKubernetesDockerPostgreSQLInfrastructuretype 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
D
76/100
safety, quality, tests
Safety 60%
75
Quality 40%
78
Run on models
none yet
Process rating
C
61/100
Has gaps
Result and completion w 14
0
Progress reporting w 2
0
When it triggers w 12
20
the three weakest of ten parameters · all ten

What is at stake

Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.

Dangerous commands medium severity

Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.

If you install

The skill contains commands that delete files, rewrite disks or execute code fetched from the network. The agent may run them without asking if it believes the instructions require it.

For the author

Replace destructive commands with safe equivalents that ask for confirmation, scope them to one folder, and stop piping curl into a shell: pin a version and a checksum.

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 · 5

✓ No critical or high findings

Medium and low: 5
  • medium Dangerous commands cmd-privilege references/cli-installation-guide.md:18
    Privilege escalation / world-writable permissions
    sudo mv hcloud /usr/local/bin/
  • medium Dangerous commands cmd-privilege references/cli-installation-guide.md:19
    Privilege escalation / world-writable permissions
    sudo chmod +x /usr/local/bin/hcloud
  • medium Dangerous commands cmd-privilege references/cli-installation-guide.md:27
    Privilege escalation / world-writable permissions
    sudo mv hcloud /usr/local/bin/
  • medium Dangerous commands cmd-privilege references/cli-installation-guide.md:28
    Privilege escalation / world-writable permissions
    sudo chmod +x /usr/local/bin/hcloud
  • medium Dangerous commands cmd-privilege references/cli-installation-guide.md:119
    Privilege escalation / world-writable permissions
    sudo mv "velero-${VELERO_VERSION}-lin…d64/velero" /usr/local/bin/

Files scanned: 30. 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 edit-residue the text marks something as outdated (lines 30): check that old rules are not kept next to new ones — the full check reads the text for contradictions

Process rating: all ten parameters 61/100

  • 0Result and completion. Does not say what the result is
  • 0Progress reporting. Says nothing while it works
  • 20When it triggers. No condition that starts the skill
  • 30Running it twice. 3 mutating operations with no state check
  • 60Tools and files. Uses tools (bash, web) that frontmatter does not declare
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 100Steps. 39 steps
  • 100Failures and branches. 2 branches, has a failure section
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 3128 tokens
  • low The response is described with custom markup (4 tags): a typed call is more reliable

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)
  • +3Output format is not stated: the model decides each time
  • -32 of 2 scripts are never mentioned in SKILL.md
  • +1No license
  • +2Single-language instructions
  • +5Description quotes 8 example trigger phrases
  • +3Description length 699: enough signal without eating the budget
  • +4Structure: 14 headings
  • +3Step-by-step instructions: 39 items
  • +4Has examples (5 code blocks)
  • +4Reference files are cited in the instructions (13 of 15)

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

External checks

ClawHub: clean
This skill is a high-impact but coherent Kubernetes-to-Huawei CCE migration assistant; its credential, secret, data-transfer, and cluster-mutation steps are disclosed and aligned with that purpose.
LLM: benign (high) · VirusTotal: · 9 Oct 2026