This skill is intended for use in users' local environments. Its goal is to help identify the causes of failures involving VolcEngine products, OpenAPI, the Python SDK, the
/
CLI, and console operations, without modifying cloud resources. The main entry point contains only the essential startup rules, scenario routing, and safety boundaries. Local tool checks and the complete domain index are located in
references/getting-started.md
; quick checks for OpenAPI errors, signatures, authentication, parameters, rate limiting, and
/
/Python SDK call chains are located in
references/openapi-quick-check.md
; and detailed product-domain manuals are located in
references/domain-guides/
.
First, resolve
to the absolute directory containing this
. All scripts and references must be resolved from
, without relying on the repository layout or the current working directory.
-
First read
references/getting-started.md
to confirm the local tools, environment variables, scenario dependencies, and domain routing.
-
If the user permits local diagnostics, run the general checks:
bash
bash "${SKILL_ROOT}/scripts/common_check.sh"
-
Prefer
to verify the current identity chain. Only report whether it is available and the necessary identity summary. Do not output SecretKey, SessionToken, full AccessKeyId, full phone numbers, billing details, or object contents.
-
Do not run
, login/SSO initialization, dependency installation, configuration file writes, or cloud resource modifications unless the user explicitly requests them and confirms the impact.
-
If the domain is uncertain, use the “Scenario Routing” section in
references/getting-started.md
to identify it. For OpenAPI errors, signature or authentication failures, parameter validation issues, rate limiting, server-side errors, or OpenAPI call failures exposed through
/
/Python SDK, first read
references/openapi-quick-check.md
to narrow down the RequestId, Action, Region, error code, and minimal reproduction context.
-
Following the routing below, open the corresponding
references/domain-guides/<domain>/README.md
, and then follow the domain manual's “Read These First” instructions to read
, the chapter README,
, and the script README.
First extract the
,
,
,
,
, resource ID, occurrence time, and invocation method from the user's error. If any required information is missing, ask only the minimum necessary questions.
For domain identification, read
references/getting-started.md
first. Once the domain has been determined, enter the corresponding
references/domain-guides/<domain>/README.md
:
If the issue still cannot be classified, complete
, then use the service name from the error to inspect
and
.
When existing evidence indicates that the skill guidance is incorrect, CLI behavior is abnormal, a required capability is missing, or the user's goal has not been fully resolved, first continue the authorized troubleshooting, recovery, and primary task. At a natural summary point, you may briefly invite the user to share their real-world scenario. Clearly distinguish confirmed issues from causes that have not yet been verified. Feedback does not replace troubleshooting and is not a prerequisite for continuing the task or ending troubleshooting.
For example: “If you wish to report a capability gap discovered in this session, you can describe the use case and improvement suggestions through the
feedback form. Feedback is optional and does not affect the continuation of the current task.”