メニュー
Use when the user encounters VolcEngine errors or needs local troubleshooting for OpenAPI, Python SDK, CLI, IAM, billing, compute, networking, storage, database, CDN, media, AI, security, or VKE cases.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Create and manage Volcengine cloud resources using the Volcengine CLI (`ve` command). Supports all Volcengine services including ECS, VPC, CLB, RDS, Redis, and more. Trigger this skill whenever the user asks to create, query, modify, or delete cloud resources on Volcengine, mentions the `ve` command, says "volcengine CLI", or describes infrastructure tasks such as "create an ECS instance", "set up a VPC", "list security groups", "allocate an EIP". Also trigger on Chinese prompts mentioning "火山引擎" or "火山" (e.g., "火山引擎上有哪些 ECS"、"查一下我火山的云服务器"、 "火山引擎创建一个 VPC"、"火山的 Redis 实例列一下"). Also trigger when the user encounters errors from `ve` commands and needs troubleshooting help.
Manage Volcengine AI Native BaaS for Supabase (AIDAP) database workspaces as a deployment database provider. Use when the user asks for Volcengine Supabase, AIDAP PostgreSQL, AIDAP database workspace setup, branch management, API keys, endpoint or database connection information, service activation, enterprise real-name verification, SQL execution, migrations, Edge Functions, Storage buckets, TypeScript type generation, or using AIDAP as the database for a Volcengine deployment. Prefer `ve aidap` for control-plane operations; use bundled scripts only for Supabase data-plane APIs missing from the current `ve` CLI.
Deploy a local project directory or Git repository to Volcengine as a running, reachable cloud service. USE WHEN: deploy to Volcengine, deploy to 火山引擎/火山, deploy this repo/project, publish current code, launch the app, run it in the cloud, expose it as a service, deploy to ECS/VKE/veFaaS, run on ECS, push to VKE, deploy as serverless/FaaS, or the user wants the agent to choose a Volcengine hosting target. If the user only asks which Volcengine deployment target to choose, use `volcengine-prepare` skill first. Not for creating a single standalone resource — use `volcengine-cli` skill for that.
Use Terraform/IaC for Volcengine resources only when the user explicitly chooses Terraform/IaC, already has a Terraform workflow/state, or confirms they need plan/diff/drift/destroy safety for VKE, managed databases/cache/storage, load balancers, domains/certificates, logging/monitoring, or team-managed infrastructure.
火山引擎官方文档检索与全文获取技能：对火山引擎官方文档站（www.volcengine.com/docs）做语义检索并抓取正文。Use when 用户咨询火山引擎产品的概念、用法、计费规则、部署步骤、最佳实践、服务条款/协议等可在官方文档中找到解释的问题，或用户直接给出火山引擎官方文档链接（www.volcengine.com/docs/...）需要取全文时。
Use when the user wants to deploy a local directory or GitHub repository to Volcengine and needs the project analyzed, the app shape understood, and a ranked recommendation across ECS, VKE, and veFaaS before choosing an execution path. Also trigger when the user asks "what deploy mode should I use", "is this repo ready for Volcengine", or "check my repo before deploying". This skill prepares the decision; `volcengine-deploy` skill performs the chosen deployment, and `volcengine-iac` skill is used only when the user chooses Terraform/IaC or the task already has an IaC workflow.
| name | volcengine-troubleshooting |
| description | Use when the user encounters VolcEngine errors or needs local troubleshooting for OpenAPI, Python SDK, CLI, IAM, billing, compute, networking, storage, database, CDN, media, AI, security, or VKE cases. |
| license | MIT |
| metadata | {"openclaw":{"envVars":[{"name":"VOLCENGINE_ACCESS_KEY","required":false,"description":"AccessKey for AK/SK auth path (alternative to `ve login`)"},{"name":"VOLCENGINE_SECRET_KEY","required":false,"description":"SecretKey for AK/SK auth path"},{"name":"VOLCENGINE_SESSION_TOKEN","required":false,"description":"Optional STS session token for temporary credentials"},{"name":"VOLCENGINE_REGION","required":false,"description":"Default region; falls back to cn-beijing if unset"}]}} |
本 skill 面向用户本地环境使用，目标是在不修改云上资源的前提下，帮助定位 VolcEngine 产品、OpenAPI、Python SDK、ve/tosutil CLI 和控制台操作失败的原因。主入口只保留必要的启动规则、场景路由和安全边界；本地工具检查与完整领域索引放在 references/getting-started.md，OpenAPI 报错、签名、鉴权、参数、限流以及 ve/tosutil/Python SDK 调用链路的快速检查放在 references/openapi-quick-check.md，具体产品域手册放在 references/domain-guides/。
先读取 references/getting-started.md，确认本地工具、环境变量、场景依赖和领域路由。
如用户允许执行本地体检，运行通用检查：
bash skills/volcengine-troubleshooting/scripts/common_check.sh
优先用 ve sts GetCallerIdentity 验证当前身份链路，只报告是否可用和必要的身份摘要，不输出 SecretKey、SessionToken、完整 AccessKeyId、完整手机号、账单明细或对象内容。
不要运行 ve configure、登录/SSO 初始化、安装依赖、写入配置文件或修改云资源，除非用户明确要求并确认影响。
若不确定归属，按 references/getting-started.md 中的“场景路由”定位领域；遇到 OpenAPI 报错、签名/鉴权失败、参数校验、限流、服务端错误，或由 ve/tosutil/Python SDK 暴露出的 OpenAPI 调用失败，先读 references/openapi-quick-check.md 收敛 RequestId、Action、Region、错误码和最小复现上下文。
根据下方路由打开对应 references/domain-guides/<domain>/README.md，再按领域手册的“先读这些”读取 query-cli-catalog.md、章节 README、api-coverage-matrix.md 和脚本 README。
先从用户报错中提取 RequestId、ErrorCode、Action、Service、Region、资源 ID、发生时间和调用方式。如果缺失，先问最少必要问题。
领域判断优先读 references/getting-started.md。确定领域后，再进入对应 references/domain-guides/<domain>/README.md：
openapi-sdk-cli：OpenAPI、ve CLI、Python SDK、签名、API 网关。account-permission：账号、AK/SK、STS、IAM、角色、权限不足。billing-quota：账单、余额、欠费、订单、配额、资源包。compute-container-network：ECS、VKE、CLB/ALB、VPC、NAT、EIP、路由、安全组。storage-database：TOS、EBS、文件存储、云备份、RDS、Redis、数据库连接。domain-cdn-ingress：DNS、域名、证书、CDN/DCDN、入口回源。communication-media：SMS、RTC、VOD、Live、CV/OCR、veImageX。llm-ecosystem：Ark、豆包、VikingDB、AgentKit、ArkClaw、Coze、机器学习平台。security-kms-encryption：KMS、Secret、云加密机、WAF、DDoS、Cloud Firewall、安全中心。仍无法分类时，完成 scripts/common_check.sh 后，按报错中的服务名查 ve SERVICE --help 和 ve SERVICE ACTION --help。
ve 和 tosutil 两类 CLI。只有分页聚合、跨资源拓扑、日志归并或 CLI 未覆盖时，才建议 volc-sdk-python 或 volcengine-python-sdk 脚本。