Unified entry point for Volcengine product transactions, orchestrating buy (subscribe/purchase) / price (price inquiry) / unsubscribe three actions. The customer's complete transaction flow is price inquiry → purchase → unsubscribe, and any 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 the steps in it.
Intent Routing
| Action | Keywords (Chinese and English, case-insensitive) | Process File |
|---|---|---|
| price price inquiry | How much, price, quotation, fee, charge, how are charges applied, how is billing calculated, 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 | Unsubscribe, refund, cancel subscription, don't want it anymore, cancel it, won't renew, unsubscribe, cancel subscription, refund | references/unsubscribe/README.md |
| buy subscribe/purchase | Activate, purchase, place an order, buy, sell, want to buy, order, buy, purchase, subscribe, provision | references/buy/README.md |
Only handle requests that match the table above. If no row is matched, the request does not fall within the scope of this skill. State that this skill only handles the three transaction execution scenarios of price inquiry, purchase, and unsubscribe, return it to the upper-level agent,and do not call any transaction API and do not provide fallback answers。
Common unmatched scenarios: issued bills 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.
- Matching both price + buy(e.g., "How much is ECS? Help me buy one") → execute price first, then after the user confirms the price, ask whether to proceed to buy.
- Other combinations matching simultaneously → 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; do not include the field names or values of product codes. Match the product name the customer said against the product list; if no match is found, directly ask the customer which product it is—only when the process truly requires a product code as an input parameter. The product code for the unsubscribe process is taken from the return value of the instance query; do not ask the customer for it.
When configuration and billing items are needed, directly state that configuration codes and billing item codes are required; do not substitute business terminology. 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.
Dependency 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<商品>. Allow automatic installation?", and wait for explicit permission. - Automatic installation 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 installation according to the README.
- If the target skill is in the volcengine-skills marketplace: call
- Report failures truthfully: If any step fails, you must explain the blocker to the user (authorization, network, permissions, missing dependencies, etc.). Do not skip authorization and execute directly, and do not falsely claim that installation has been completed.