huawei-cloud-maas-setup

Automates Huawei Cloud MaaS service purchase, API key creation, and model activation via browser scripts.

Updated Aug 31, 2026
One-click install
npx skills add https://github.com/DreamMacer/jiuwenswarm --skill huawei-cloud-maas-setup-dreammacer
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: huawei-cloud-maas-setup
Source: https://github.com/DreamMacer/jiuwenswarm/tree/main/resources/agent/workspace/skills/huawei-cloud-maas-setup
Command: npx skills add https://github.com/DreamMacer/jiuwenswarm --skill huawei-cloud-maas-setup-dreammacer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires playwright, pyyaml, and includes scripts (resource) and references (resource) components.

What problem does it solve? Setting up Huawei Cloud MaaS (ModelArts as a Service) requires navigating multiple console pages, completing authorization, creating API keys, and activating models one by one. This Skill automates the repetitive browser steps while keeping the user in control of sensitive actions like login, payment, and identity verification, reducing the whole setup to about 3-5 minutes. ## Core Features & Use Cases - Browser automation via CDP: Scripts launch a Chromium-based browser, navigate Huawei Cloud console pages, close guide popups, and detect real-name authentication status automatically. - Automated credential and model setup: Automatically completes MaaS delegation authorization, creates an API Key (with insufficient-balance and real-name detection), and batch-activates preset text-generation models defined in models.json. - Guided user decisions: Uses structured prompts for login, recharge, and identity verification, with per-step failure fallback to manual browser operation. - Use Case: A first-time user wants to add Huawei Cloud models (GLM, Kimi, DeepSeek) to their jiuwenswarm configuration. The Skill walks them through login and payment, then automatically authorizes the service, creates the API key, activates the models, and writes the configuration to .env and config.yaml without changing their default model. ## Quick Start Ask the assistant to run the Huawei Cloud MaaS one-click setup to configure the API key and activate models for jiuwenswarm.

Frequently Asked Questions about huawei-cloud-maas-setup

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set up Huawei Cloud MaaS API access automatically?▼

Run the guided setup flow: scripts launch a browser via CDP, navigate to the Huawei Cloud console, and automate authorization, API key creation, and model activation. You only handle login, recharge, and real-name verification manually.

What steps in Huawei Cloud MaaS setup require manual user action?▼

Login, account recharge, and real-name identity verification must be done by the user because they involve credentials, payment, and personal information. Authorization, API key creation, and model activation are fully automated by scripts.

Which browsers are supported for the Huawei Cloud automation scripts?▼

The scripts support Chromium-based browsers: Edge, Chrome, and Chromium. On Windows Edge is preferred since it is preinstalled; on macOS and Linux Chrome is preferred. The browser is launched with a dedicated user-data directory and CDP debugging port.

Why does API key creation fail with insufficient balance or real-name errors?▼

Huawei Cloud requires account balance and completed real-name authentication before creating API keys. The script detects these states and returns specific error stages, then the flow guides you to recharge or verify identity before retrying.

How do I change which models get activated and written to config?▼

Edit the models.json file in the skill directory. Each entry defines display_name for console activation, api_name for config.yaml, alias, and description. Both the activation script and config writer read from this single file.

Does the setup overwrite my existing model configuration?▼

No. The config writer appends new model entries by alias and never modifies any is_default flags. Environment variables use the HUAWEI_MAAS_ prefix in .env, so existing credentials and default model settings remain untouched.