git:20260915.6a4cfb9 to git:20261019.fe808e8

12 added, 0 removed. Audit A to A.

# cloud-concept-skills

Community-maintained Huawei Cloud skills; not an official Huawei Cloud project.

## Repository contract

- `skills/<name>/` contains the install payload only. Put gates, evals, and `skillcheck.toml` under `qa/<name>/`.

- Run `./qa/<name>/validate.sh` for a changed skill or `./tools/validate-all.sh` for the repository.

- Keep `skills/`, `qa/` (`VERSION`, changelog), `docs/catalog.yml`, and `docs/skills/<name>.md` synchronized.

- English lives at `skills/en/<name>`; Simplified Chinese at `skills/cn/<name>-cn`. Update pairs together under `docs/localization.md`; `tools/validate-localization.py` is the parity gate.

- ClawHub publishes only `skills/en`; never run ClawHub sync against `skills/cn`.

- Never commit credentials, `.env*`, generated workspaces, or gate reports.

- Do not auto-install `hcloud`. Real BSS calls run only when a skill-specific opt-in environment variable enables them.

- Billing and onboarding stay read-only. Cost-estimation creates stay within the allowlist and confirmation gates; unsubscribe stays console-only.

+ ## Skill structure and loading

+ - Organize substantial skills by Shared, Service, Helper, Recipe, and Persona responsibilities. Use the definitions in `docs/authoring.md`; these are content roles, not five mandatory skills or loading stages.

+ - Give each command contract one canonical location. Category indexes and workflows link to it. FCAPS is a cross-service index; it does not replace service names or describe execution effects.

+ - Keep command semantics, effects, and conditional dependencies in contracts. Discover detailed parameters with the current CLI help. Reuse known identifiers; resolve only missing inputs.

+ - Classify effects from the documented operation behavior. HTTP methods and operation prefixes alone do not establish read-only behavior.

+ - Use shallow reference directories when they reduce unrelated reading. Each pointer states when to read its target. A known workflow can link directly to a needed contract.

+ - Preserve the requested implementation scope. A planned recipe contains its goal and one or two guidance sentences; it is not an executable workflow.

+ - Keep unfinished skills under `development/`. Publish, register, and create localization pairs only when promoting a draft to the installable catalog.

+ - Verify CLI facts before writing contracts. Record help checks and live API calls separately. Empty responses, permission failures, and successful resource queries are distinct results. Help or dry-run success does not establish live API success.

+ - Keep validation scripts outside runtime references. Store raw outputs and validation reports in an ignored workspace; redact credentials and sensitive response fields.

## Billing semantic split

Keep facts, dimensions, measures, and routing thin in `references/semantic/*.yml`. Put CLI contracts, concrete codes, enum values, response paths, and command examples in `references/related-commands.md` and its linked command references.