← 返回 Skills 市场
volc-sdk-team

Volcengine Troubleshooting

作者 sdk-team · GitHub ↗ · v1.0.0 · MIT-0
cross-platform ⚠ suspicious
35
总下载
0
收藏
0
当前安装
1
版本数
在 OpenClaw 中安装
/install volcengine-troubleshooting
功能描述
Use when the user encounters VolcEngine errors or needs local troubleshooting for OpenAPI, Python SDK, CLI, IAM, billing, compute, networking, storage, datab...
使用说明 (SKILL.md)

VolcEngine Troubleshooting

本 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/。

开始前

  1. 先读取 references/getting-started.md，确认本地工具、环境变量、场景依赖和领域路由。

  2. 如用户允许执行本地体检，运行通用检查：

    bash skills/volcengine-troubleshooting/scripts/common_check.sh

  3. 优先用 ve sts GetCallerIdentity 验证当前身份链路，只报告是否可用和必要的身份摘要，不输出 SecretKey、SessionToken、完整 AccessKeyId、完整手机号、账单明细或对象内容。

  4. 不要运行 ve configure、登录/SSO 初始化、安装依赖、写入配置文件或修改云资源，除非用户明确要求并确认影响。

  5. 若不确定归属，按 references/getting-started.md 中的“场景路由”定位领域；遇到 OpenAPI 报错、签名/鉴权失败、参数校验、限流、服务端错误，或由 ve/tosutil/Python SDK 暴露出的 OpenAPI 调用失败，先读 references/openapi-quick-check.md 收敛 RequestId、Action、Region、错误码和最小复现上下文。

  6. 根据下方路由打开对应 references/domain-guides/\x3Cdomain>/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/\x3Cdomain>/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。

核心原则

  • 只读优先：默认只执行 Describe/List/Get/Query/Lookup/Check 类命令。Create/Update/Delete/Attach/Detach/Put/Set/Start/Stop/Run/Invoke/Pay/Renew/Refresh/Preload 等写操作必须先解释影响并等待用户确认。
  • CLI 优先，SDK 辅助：只支持 ve 和 tosutil 两类 CLI。只有分页聚合、跨资源拓扑、日志归并或 CLI 未覆盖时，才建议 volc-sdk-python 或 volcengine-python-sdk 脚本。
  • 凭证安全：只从环境变量读取 AK/SK/Token；不要要求用户把凭证写入文件；不要打印 SecretKey、SessionToken 或完整 AccessKeyId；展示 AK 时至少遮蔽中间部分。
  • 最小上下文：每次排障只收集当前问题所需的服务、地域、资源和时间窗口。不要批量枚举无关账号资源。
  • 解释判据：每个检查都说明为什么查、期望看到什么、异常意味着什么，以及下一步该收集哪一项证据。
安全使用建议
Install only if you are comfortable with a troubleshooting assistant using VolcEngine credentials. Use a least-privilege, temporary account where possible, do not grant secret-value or token-minting permissions unless explicitly needed, and require manual approval before any command that could reveal API keys, role credentials, workload tokens, SecretValue, user data, or full console output.
能力标签
cryptorequires-oauth-tokenrequires-sensitive-credentials
能力评估
⚠ Purpose & Capability
The stated purpose is coherent cloud troubleshooting, and most guidance is read-only, but API matrices include actions such as GetSecretValue, GetResourceApiKey, GetRoleCredentials, GetUserCredential, and workload access token retrieval as troubleshooting candidates.
⚠ Instruction Scope
Top-level instructions warn not to print credentials and some domain guides require confirmation for sensitive reads, but the coverage matrices repeatedly classify secret-returning calls under read-only or diagnostic scope, which can confuse agent behavior.
✓ Install Mechanism
No risky install behavior was found; the artifact is mostly markdown plus local scripts, with no automatic package install, persistence setup, or configuration writing.
ℹ Credentials
VolcEngine credentials and CLI/API access are expected for this troubleshooting purpose, but users should restrict them to least-privilege diagnostic permissions because the skill covers many cloud product areas.
✓ Persistence & Privilege
The skill instructs agents not to run ve configure/login/SSO or write credentials, and inspected scripts read credentials from environment variables without creating persistence or modifying cloud resources.
如何使用
  1. 确保已安装 OpenClaw（本地或 Docker 部署）
  2. 在对话框中输入安装命令：/install volcengine-troubleshooting
  3. 安装完成后，直接呼叫该 Skill 的名称或使用 /volcengine-troubleshooting 触发
  4. 根据 Skill 的参数说明提供必要输入，即可获得结构化输出
版本历史
v1.0.0
Initial release of volcengine-troubleshooting. - Assists with VolcEngine error troubleshooting across OpenAPI, Python SDK, CLI, IAM, billing, compute, networking, storage, database, CDN, media, AI, security, and VKE scenarios. - Focuses strictly on local, non-destructive checks—does not modify cloud resources by default. - Provides domain-specific routing, quick OpenAPI and authentication checks, and clear safety boundaries for credential handling. - CLI-based and read-only operations are prioritized; write operations require explicit user confirmation. - Guidance and references are organized for fast issue identification and resolution, with domain handbooks for detailed troubleshooting steps.
元数据
Slug volcengine-troubleshooting
版本 1.0.0
许可证 MIT-0
累计安装 0
当前安装数 0
历史版本数 1
常见问题

Volcengine Troubleshooting 是什么？

Use when the user encounters VolcEngine errors or needs local troubleshooting for OpenAPI, Python SDK, CLI, IAM, billing, compute, networking, storage, datab... 它是一个面向 Claude Code / OpenClaw 的 AI Agent Skill 插件，目前累计下载 35 次。

如何安装 Volcengine Troubleshooting？

在 OpenClaw 或 Claude Code 对话框中运行命令「/install volcengine-troubleshooting」即可一键安装，无需额外配置。

Volcengine Troubleshooting 是免费的吗？

是的，Volcengine Troubleshooting 完全免费，采用 MIT-0 许可证，可自由下载、安装和使用。

Volcengine Troubleshooting 支持哪些平台？

Volcengine Troubleshooting 跨平台运行，可在任意部署了 OpenClaw / Claude Code 的环境中使用（cross-platform）。

谁开发了 Volcengine Troubleshooting？

由 sdk-team（@volc-sdk-team）开发并维护，当前版本 v1.0.0。

推荐 Skills
self-improving agent
Captures learnings, errors, and corrections to enable continuous improvement. Use when: (1) A command or operation fails unexpectedly, (2) User corrects Clau...
⬇ 463283 · by pskoett
Skill Vetter
Security-first skill vetting for AI agents. Use before installing any skill from ClawdHub, GitHub, or other sources. Checks for red flags, permission scope, and suspicious patterns.
⬇ 259410 · by spclaudehome
Polymarket
Query Polymarket prediction markets. Check odds, find trending markets, search events, track price movements.
⬇ 232503 · by joelchance
Self-Improving + Proactive Agent
Self-reflection + Self-criticism + Self-learning + Self-organizing memory. Agent evaluates its own work, catches mistakes, and improves permanently. Use when...
⬇ 200423 · by ivangdavila
Github
Interact with GitHub using the `gh` CLI. Use `gh issue`, `gh pr`, `gh run`, and `gh api` for issues, PRs, CI runs, and advanced queries.
⬇ 191113 · by steipete
ontology
Typed knowledge graph for structured agent memory and composable skills. Use when creating/querying entities (Person, Project, Task, Event, Document), linkin...
⬇ 190156 · by oswalpalash

💬 留言讨论