Unified entry point for Volcano commodity transactions, orchestrating three actions: buy (activate purchase) / price (inquiry) / unsubscribe (unsubscribe) . The customer's complete transaction flow is inquiry → purchase → unsubscribe, and any one of these capabilities can also be used independently.
How to use
- Determine the user's transaction action according to the "Intent Routing" table below.
- Read the process file for that action and execute according to the steps in it.
Intent Routing
| Action | Keywords (Chinese and English, case-insensitive) | Process File |
|---|---|---|
| price inquiry | how much, price, quote, fee, charge, how is it charged, how is it billed, billing method, billing rules, charging standard, price list, unit price, total price, estimated cost, cost, budget, price, pricing, quote, cost | references/price/README.md |
| unsubscribe | unsubscribe, refund, cancel subscription, don't want it anymore, cancel it, won't renew, unsubscribe, cancel subscription, refund | references/unsubscribe/README.md |
| buy activate purchase | activate, purchase, place order, buy, sell, want to buy, order, buy, purchase, subscribe, provision | references/buy/README.md |
Only handle requests that match the table above. If none of the rows are matched, it does not fall within the scope of this skill, indicating that this skill only handles the three types of transaction execution scenarios: inquiry, purchase, and unsubscribe, and returns to the upper-layer agent,without calling any transaction interface and without providing fallback answers。
Common unmatched scenarios: billed statements and arrears details (metering and billing disputes), discount and voucher applications, price negotiation and stamped quotations, and free quota inquiries. Even if such requests mention a product name or amount, they do not enter this skill's process.
- If both price + buy are matched(e.g., "How much is ECS, help me buy one") → execute price first, and after the user confirms the price, ask whether to proceed to buy.
- If other combinations are matched at the same time → ask the user to split them into multiple intents; do not execute them in parallel.
Customer-facing wording
For products, always use only the Chinese name, and do not include the field names and values of product codes. Use the product name mentioned by the customer to match in the product list; if no match is found, directly ask the customer which product it is—only when the process truly requires the product code as an input parameter. The product code for the unsubscribe process is taken from the return value of the instance query, and the customer must not be asked for it for this purpose.
When configuration and billing items are needed, directly state that the configuration code and billing item code are needed, and do not replace them with business wording. If the customer cannot provide them, degrade according to the process.
The command itself, the original error text, and codes actively used by the customer are displayed as-is without rewriting.
Login and Credentials
Handled by ve itself. When a command returns an authentication error, hand it to the volcengine-cli skill to go through ve login. This skill does not perform pre-checks on login status, consistent with other ve calls such as ECS / VPC.
Dependent skill auto-loading
When the target skill to which this skill hands off is not loaded, uniformly execute the following process:
- Request user authorization: explain to the user "Need to install
<skill-name>to continue processing<商品>, do you allow automatic installation?", and wait for explicit permission. - Automatically install after authorization：
- If the target skill is in the volcengine-skills marketplace: call
volcengine-find-skillsto initiate installation. - The target skill is in an external GitHub repository (such as ark-cli / ve-tls-cli): automatically clone it from the source URL given in the process file / complete the installation according to the README.
- If the target skill is in the volcengine-skills marketplace: call
- Report failures truthfully: any step that fails must be explained to the user, including the blocking point (authorization, network, permissions, missing dependencies, etc.). Do not skip authorization and execute directly, and do not falsely claim that installation has been completed.