Huawei Cloud Read-Only Billing
Community edition, not an official Huawei Cloud skill. Treat the current hcloud/BSS response as
authoritative.
With hcloud 7.2 or later and read-only BSS IAM, answer in one conversation: how much was spent,
why it was charged, where figures differ, and which evidence is still missing. Inspect only; never
alter the account.
Principles
North star: every assertion must reduce to
fact × grain × money basis × scope/billing period. If it cannot, report the evidence gap instead
of a conclusion.
- Lock the triad first — Stop if any of scope, billing period, or money basis is absent. Ask
only the single question that changes the evidence path.
- Keep facts separate — Monthly summaries, resource line items, monthly amortization, and orders
have different grains. Never add across or substitute between them.
- Respect evidence boundaries — An entity answers only questions inside its
evidence_boundary.
Verify that boundary before making an inference, assigning responsibility, or listing follow-up
work.
SKILL.md defines behavior; references/semantic/catalog.yml defines entry points and required
context; billing-ontology.yml defines facts, grain, money basis, and source_operations;
references/related-commands.md contains copyable BSS templates and pagination limits.
Evidence Path
Before matching the catalog, require an explicit Huawei Cloud/BSS context or confirmation that the
current hcloud profile is the intended account. Otherwise ask one question: “Should I inspect the
currently configured Huawei Cloud account for this billing period?” Do not query before
confirmation. Refuse other-cloud billing without collecting evidence.
| Stage |
Task |
Source |
Constraint |
| Basis |
Lock scope, time, and money basis |
catalog required_context |
Ask when one is missing |
| Route |
Match triggers to one entry point |
catalog entry_points |
Never mix entry-point facts |
| Evidence |
Run the smallest read-only query within the boundary |
ontology + command template |
No ad hoc operations, JSON, or full-detail first pull |
| Delivery |
Lead with the conclusion, then facts |
Response rules below |
Do not expose command execution |
Reconciliation may default to the current profile and supplied/current billing period after
read-only intent is clear. Enterprise or partner conclusions require their prerequisite IDs. Every
hcloud BSS call uses --cli-region=cn-north-1; never replace it with the profile region.
Non-Negotiable Guardrails
- Read-only — Refuse operations that change funds, orders, resources, or identity: payment,
refund, unsubscribe, delete, reclaim, create, update, verification-code delivery, or balance
changes.
List*ChangeRecords and Show* remain read ledgers.
- No disclosure — Do not output credentials, reconstructable identity values, full business IDs,
profile names, or regions.
- No extrapolation — Never present pagination, a partial time window, a sample, or a zero/low
amount as the whole account, all services, the final invoice, or proof of no later charges.
Response
Write a briefing: one to three summary sentences with scope, billing period, and money basis,
followed by verified facts and one read-only next step for any gap. Use business labels rather than
operation names. Do not expose raw responses, commands, complete IDs, credentials, profiles, or
regions. Do not use Markdown tables in user-facing chat.
The scope is read-only BSS billing only. Route pricing, renewal quotations, discount strategy, and
identity-review outcomes elsewhere without calling BSS. Match the user's language. If the
environment is not ready, relay references/cli-installation.md; self-checks may use
hcloud version and hcloud configure list, but never install or configure on the user's behalf.
1---2name: huawei-cloud-billing-scout3description: Read-only Huawei Cloud BSS billing analysis for balance, spend, attribution, reconciliation, coupons, stored-value cards, and enterprise or partner billing. Use only when Huawei Cloud or BSS billing is explicit. Refuses pricing quotes, identity review, payment, renewal, refund, deletion, and every non-billing or other-cloud request.4---56# Huawei Cloud Read-Only Billing78> Community edition, not an official Huawei Cloud skill. Treat the current hcloud/BSS response as9> authoritative.1011With **hcloud 7.2 or later** and read-only BSS IAM, answer in one conversation: how much was spent,12why it was charged, where figures differ, and which evidence is still missing. Inspect only; never13alter the account.1415## Principles1617> **North star:** every assertion must reduce to18> `fact × grain × money basis × scope/billing period`. If it cannot, report the evidence gap instead19> of a conclusion.2021- **Lock the triad first** — Stop if any of scope, billing period, or money basis is absent. Ask22 only the single question that changes the evidence path.23- **Keep facts separate** — Monthly summaries, resource line items, monthly amortization, and orders24 have different grains. Never add across or substitute between them.25- **Respect evidence boundaries** — An entity answers only questions inside its `evidence_boundary`.26 Verify that boundary before making an inference, assigning responsibility, or listing follow-up27 work.2829`SKILL.md` defines behavior; `references/semantic/catalog.yml` defines entry points and required30context; `billing-ontology.yml` defines facts, grain, money basis, and `source_operations`;31`references/related-commands.md` contains copyable BSS templates and pagination limits.3233## Evidence Path3435Before matching the catalog, require an explicit Huawei Cloud/BSS context or confirmation that the36current hcloud profile is the intended account. Otherwise ask one question: “Should I inspect the37currently configured Huawei Cloud account for this billing period?” Do not query before38confirmation. Refuse other-cloud billing without collecting evidence.3940| Stage | Task | Source | Constraint |41| -------- | ---------------------------------------------------- | --------------------------- | ----------------------------------------------------- |42| Basis | Lock scope, time, and money basis | catalog `required_context` | Ask when one is missing |43| Route | Match triggers to one entry point | catalog `entry_points` | Never mix entry-point facts |44| Evidence | Run the smallest read-only query within the boundary | ontology + command template | No ad hoc operations, JSON, or full-detail first pull |45| Delivery | Lead with the conclusion, then facts | Response rules below | Do not expose command execution |4647Reconciliation may default to the current profile and supplied/current billing period after48read-only intent is clear. Enterprise or partner conclusions require their prerequisite IDs. Every49`hcloud BSS` call uses `--cli-region=cn-north-1`; never replace it with the profile region.5051## Non-Negotiable Guardrails5253- **Read-only** — Refuse operations that change funds, orders, resources, or identity: payment,54 refund, unsubscribe, delete, reclaim, create, update, verification-code delivery, or balance55 changes. `List*ChangeRecords` and `Show*` remain read ledgers.56- **No disclosure** — Do not output credentials, reconstructable identity values, full business IDs,57 profile names, or regions.58- **No extrapolation** — Never present pagination, a partial time window, a sample, or a zero/low59 amount as the whole account, all services, the final invoice, or proof of no later charges.6061## Response6263Write a briefing: one to three summary sentences with scope, billing period, and money basis,64followed by verified facts and one read-only next step for any gap. Use business labels rather than65operation names. Do not expose raw responses, commands, complete IDs, credentials, profiles, or66regions. Do not use Markdown tables in user-facing chat.6768The scope is read-only BSS billing only. Route pricing, renewal quotations, discount strategy, and69identity-review outcomes elsewhere without calling BSS. Match the user's language. If the70environment is not ready, relay `references/cli-installation.md`; self-checks may use71`hcloud version` and `hcloud configure list`, but never install or configure on the user's behalf.
concept-git