Huawei Cloud CCI Skill: Manage Serverless Containers

Lets an agent run Huawei Cloud CCI serverless containers from the command line: namespaces, networks, workloads, public IPs and logs.

Installs: 17.5K; on skills.sh
Stars: 59; on GitHub
Files: 16; besides SKILL.md
Updated: Oct 2026; last repo commit

This is Huawei Cloud's own skill for Cloud Container Instance (CCI), its serverless container service. The agent builds hcloud CCI commands for namespaces, networks, Deployments, StatefulSets, Pods and EIPPools, reads pod status and logs, and follows a create, run, clean up order. SKILL.md's routing table points to 13 reference guides for these tasks.

It needs the hcloud CLI (7.2.2 or newer) with credentials in environment variables, and one bundled Python helper that creates the network because hcloud cannot pass the annotation key. SKILL.md asks for a preview and your explicit confirmation before every delete, and deleting a namespace removes everything under it.

Good for

Developers who run containers on CCI and want an agent to build the long hcloud commands
Teams that need a namespace, network and deployment set up in the right order
Ops engineers checking pod status and logs

Install huawei-cloud-cci-instance-management

Claude Code

Copy this prompt.

Install the huawei-cloud-cci-instance-management skill in Claude Code. Run this command:

npx skills add huaweicloud/huaweicloud-skills --skill huawei-cloud-cci-instance-management

Then check that it loaded and tell me how to use it.

2
Paste it into Claude Code. It shows the change and asks before running it.

Requires Node.js.

SKILL.md needs hcloud 7.2.2 or newer. The KooCLI command shown comes from the OBS bucket create skill's install guide, because the CCI folder has no install guide, and it installs the latest version. Set both pairs of key variables before you start. The repo has no plugin manifest, so there is no plugin route.

Built from the package data we hold. Not yet tested by us. Source.

What's in the skill

When it loads

Huawei Cloud CCI (Cloud Container Instance) full lifecycle management using hcloud CLI. Covers Namespace, Network, Deployment, StatefulSet, Pod creation/update/delete/status, EIPPool for public IP, logs and metrics. Two-step confirmation for all destructive operations (delete namespace cascades all resources under it). Use this skill when the user wants to operate CCI serverless containers via command line. Triggers: CCI, 云容器实例, serverless container, 容器实例, namespace, deployment, statefulset, pod, EIPPool, CCI负载, 无服务器容器, 创建容器实例, 删除容器实例, 容器状态, 容器日志

Sections in SKILL.md

Overview
Constraints and Rules
Security Rules
Resource Constraints
hcloud CLI Constraints
Standard Workflow
Prerequisites
1. hcloud CLI Requirements (MANDATORY)
2. Credential Configuration
3. Validation Check
Security Constraints
Dangerous Operation Confirmation Mechanism
Credential Security
Command Format Standard
CCI-Specific Parameter Rules
Parameter Format Details

Key facts

Author: Huawei Cloud (the skill is in the vendor's own huaweicloud/huaweicloud-skills repo; the README calls these officially maintained Huawei Cloud Agent Skills)
License: MIT (LICENSE file and README badge; the LICENSE copyright line still reads "[year] [fullname]")
Installs on skills.sh: 17,506 (Nov 2, 2026)
skills.sh audits: Gen Agent Trust Hub warn, Socket warn, Snyk warn (Nov 2, 2026)
GitHub stars: 59 for the whole huaweicloud/huaweicloud-skills repo (Nov 2, 2026)
Last repo commit: Oct 31, 2026
What it includes: 17 files including SKILL.md (counted from the repo tree): 15 Markdown files in references/ and 1 Python script, scripts/cci_network_helper.py.
Needs: hcloud (KooCLI) 7.2.2 or newer, credentials in environment variables, and a VPC subnet that is not 10.247.0.0/16 (SKILL.md)
Works in: The README names no client; it says the skills are "compatible with mainstream AI Agents"

What it includes

Creates, lists, reads and deletes CCI namespaces
Uses hcloud CCI createCoreV1Namespace and related commands. Every namespace needs the flavor annotation general-computing or gpu-accelerated. Deleting a namespace deletes every resource under it.
Try: “Create a CCI namespace named dev-ns with general-computing flavor in cn-north-4.”
Delete · Namespace
Creates the namespace network with scripts/cci_network_helper.py
hcloud cannot pass the dotted annotation key, so the bundled helper signs and sends the create request to the CCI API itself. It also has delete and status subcommands, and it reads HW_ACCESS_KEY and HW_SECRET_KEY, separate from the hcloud credentials.
Try: “Create a CCI network in dev-ns for my subnet.”
Delete · Network (Python helper)
Creates, scales, updates and deletes workloads
Builds the long hcloud CCI commands for Deployments and StatefulSets, and enforces that resource limits equal requests.
Try: “Deploy nginx in dev-ns with 500m CPU and 1Gi memory.”
Delete · Deployment and StatefulSet
Creates, reads, logs and deletes single pods
Creates a pod, reads its status and phase, reads container logs, and deletes it on request.
Try: “Show the logs of my pod in dev-ns.”
Delete · Pod
Creates a pool of public IPs for pods
Creates EIPs for pods with a network type, bandwidth size and charge mode, and binds a pool to a pod by annotation.
Delete · EIPPool
Finds the VPC, subnet and network ID the network needs
Runs hcloud VPC ListVpcs, ListSubnets and ShowSubnet to get the neutron network ID that network creation requires.
Runs code · VPC lookups
Preview first, delete only after you confirm
For deleting a namespace, network, Deployment, StatefulSet, Pod or EIPPool, the agent shows the command, resource details and risk and waits for your explicit yes.
Read · Two-step confirmation

From the official docs

Permissions

High risk

It creates and deletes billable cloud resources with your key, and deleting a namespace removes everything under it. Use a test project and a limited key, and read each command before it runs.

What it can do

Read your data
Create and change things
Delete things
Read-only mode

Watch out for

Deleting a namespace deletes everything in it
SKILL.md rates it critical: all networks, pods and deployments under the namespace go. The agent must preview and wait for your yes. Read the namespace name twice. github.com
Creates cost money and have no confirmation rule
The two-step confirmation in SKILL.md covers deletes. Creating pods, workloads and EIPPools with bandwidth is billed and is not covered. Ask the agent to show the command before it runs. github.com
The helper uses a second set of credentials
cci_network_helper.py reads HW_ACCESS_KEY and HW_SECRET_KEY, independent of the hcloud login, runs hcloud through a shell to find the project ID, and can create, delete and check networks. Give both keys the same limited scope. github.com
It installs helper packages and the CLI
The helper needs pip install requests huaweicloudsdkcore, and SKILL.md needs hcloud 7.2.2 or newer. The first hcloud run asks you to accept a privacy statement, which SKILL.md answers with printf "y\n" | hcloud version. github.com

Security advisories

No published security advisories as of Nov 2, 2026.

Technical details

Turning on read-only	No read-only mode. Status and log commands only read.
Talks to	Huawei Cloud API through hcloud. cci.<region>.myhuaweicloud.com, called directly by the Python helper
Sign-in and keys	hcloud reads its own profile or environment variables. The helper reads HW_ACCESS_KEY and HW_SECRET_KEY. SKILL.md says never to expose key values.
Scopes	Creates, updates and deletes CCI namespaces, networks, workloads and EIPPools in your account Creates public IPs with bandwidth through EIPPool Runs hcloud and a bundled Python helper that signs requests with your key Reads HUAWEI_CLOUD_AK and HUAWEI_CLOUD_SK for hcloud, and HW_ACCESS_KEY and HW_SECRET_KEY for the helper

Questions

What does huawei-cloud-cci-instance-management do?

It makes an agent manage Huawei Cloud CCI serverless containers with the hcloud CLI: create a namespace and network, run Deployments, StatefulSets and Pods, attach public IPs, read status and logs, and clean up.

Does it need an API key?

Yes. SKILL.md has you set HUAWEI_CLOUD_AK and HUAWEI_CLOUD_SK (plus a region, and a security token for temporary keys) for hcloud. The Python network helper reads HW_ACCESS_KEY and HW_SECRET_KEY instead, so set both pairs. SKILL.md tells the agent never to show or request the key.

Is huawei-cloud-cci-instance-management official?

It is in Huawei Cloud's own huaweicloud/huaweicloud-skills repo, which the README calls officially maintained Huawei Cloud Agent Skills.

Is it safe to run?

It creates and deletes billable cloud resources with your key. SKILL.md asks for confirmation before deletes, but creating workloads and public IPs is not covered by that rule. Our advice: use a test project, and read each command the agent prints before you let it run.

Does it work in Claude Code, Codex or the Claude app?

The install box has Claude Code, Codex and standalone tabs. Huawei says only that the skills are compatible with mainstream AI Agents and names none, and it documents no Claude app upload. This skill runs command-line tools on your machine, so the box has no Claude app tab.

Why does network creation use a Python script?

SKILL.md says hcloud treats dots in an annotation key as nested levels, and that annotations given as JSON input show in a dry run but are not sent. So the bundled cci_network_helper.py builds and signs the request directly.

Information

updated Nov 2, 2026

Repository: huaweicloud/huaweicloud-skills
Folder: skills/container/cci/huawei-cloud-cci-instance-management

huaweicloud/huaweicloud-skills skills.sh

Sources

Docs, issue trackers and discussions this page is built from.

Show all 4

huawei-cloud-cci-instance-management SKILL.md · github.com
huaweicloud-skills README · github.com
huaweicloud-skills LICENSE · github.com
cci_network_helper.py · github.com