$npx -y skills add TencentCloudBase/cloudbase-skills --skill ops-inspectorAIOps-style one-click inspection skill for CloudBase resources. Use this skill when users need to diagnose errors, check resource health, inspect logs, or run a comprehensive health check across cloud functions, CloudRun services, databases, and other CloudBase resources.
| 1 | ## Standalone Install Note |
| 2 | |
| 3 | If this environment only installed the current skill, start from the CloudBase main entry and use the published `cloudbase/references/...` paths for sibling skills. |
| 4 | |
| 5 | - CloudBase main entry: `https://cnb.cool/tencent/cloud/cloudbase/cloudbase-skills/-/git/raw/main/skills/cloudbase/SKILL.md` |
| 6 | - Current skill raw source: `https://cnb.cool/tencent/cloud/cloudbase/cloudbase-skills/-/git/raw/main/skills/cloudbase/references/ops-inspector/SKILL.md` |
| 7 | |
| 8 | Keep local `references/...` paths for files that ship with the current skill directory. When this file points to a sibling skill such as `cloud-functions` or `cloudrun-development`, use the standalone fallback URL shown next to that reference. |
| 9 | |
| 10 | ## Activation Contract |
| 11 | |
| 12 | ### Use this first when |
| 13 | |
| 14 | - The user wants to check the health or status of CloudBase resources (cloud functions, CloudRun, databases, storage, etc.). |
| 15 | - The user reports errors, failures, or abnormal behavior and wants a quick diagnosis. |
| 16 | - The user asks for an "inspection", "health check", "巡检", "诊断", or "troubleshooting" of their CloudBase environment. |
| 17 | - The user wants to review recent error logs across services. |
| 18 | |
| 19 | ### Read before writing code if |
| 20 | |
| 21 | - The inspection reveals code-level issues in cloud functions or CloudRun services — then read the relevant implementation skill before suggesting fixes. |
| 22 | - The user wants to fix a problem found during inspection rather than just diagnose it. |
| 23 | |
| 24 | ### Then also read |
| 25 | |
| 26 | - Cloud function issues -> `../cloud-functions/SKILL.md` (standalone fallback: `https://cnb.cool/tencent/cloud/cloudbase/cloudbase-skills/-/git/raw/main/skills/cloudbase/references/cloud-functions/SKILL.md`) |
| 27 | - CloudRun issues -> `../cloudrun-development/SKILL.md` (standalone fallback: `https://cnb.cool/tencent/cloud/cloudbase/cloudbase-skills/-/git/raw/main/skills/cloudbase/references/cloudrun-development/SKILL.md`) |
| 28 | - Database issues -> `../postgresql-development/SKILL.md` for CloudBase PG / PostgreSQL (standalone fallback: `https://cnb.cool/tencent/cloud/cloudbase/cloudbase-skills/-/git/raw/main/skills/cloudbase/references/postgresql-development/SKILL.md`), `../relational-database-tool/SKILL.md` for MySQL (standalone fallback: `https://cnb.cool/tencent/cloud/cloudbase/cloudbase-skills/-/git/raw/main/skills/cloudbase/references/relational-database-tool/SKILL.md`), or `../no-sql-web-sdk/SKILL.md` for NoSQL (standalone fallback: `https://cnb.cool/tencent/cloud/cloudbase/cloudbase-skills/-/git/raw/main/skills/cloudbase/references/no-sql-web-sdk/SKILL.md`) |
| 29 | - Platform overview -> `../cloudbase-platform/SKILL.md` (standalone fallback: `https://cnb.cool/tencent/cloud/cloudbase/cloudbase-skills/-/git/raw/main/skills/cloudbase/references/cloudbase-platform/SKILL.md`) |
| 30 | |
| 31 | ### Do NOT use for |
| 32 | |
| 33 | - Deploying new resources or writing application code. This skill is read-only and diagnostic. |
| 34 | - Replacing proper monitoring/alerting infrastructure. It provides point-in-time inspection, not continuous monitoring. |
| 35 | - Directly fixing problems — it diagnoses and recommends; actual fixes should use the appropriate implementation skill. |
| 36 | |
| 37 | ### Common mistakes / gotchas |
| 38 | |
| 39 | - Running a full inspection without first confirming the environment is bound (`auth` tool must show logged-in and env-bound state). |
| 40 | - Ignoring CLS log service status — if CLS is not enabled, `queryLogs` will fail; always check first with `queryLogs(action="checkLogService")`. |
| 41 | - Searching logs without a time range — this can return excessive or irrelevant results. Always scope searches to a relevant time window. |
| 42 | - Treating a single error log as the root cause without correlating across resources. A function error may stem from a database or config issue. |
| 43 | |
| 44 | ### Minimal checklist |
| 45 | |
| 46 | - [ ] Environment is bound and accessible (`envQuery(action="info")`) |
| 47 | - [ ] CLS log service is enabled (`queryLogs(action="checkLogService")`) |
| 48 | - [ ] All target resources are listed before diving into details |
| 49 | - [ ] Time range is specified for any log searches |
| 50 | - [ ] Findings are summarized with severity levels and actionable recommendations |
| 51 | |
| 52 | --- |
| 53 | |
| 54 | ## How to use this skill (for a coding agent) |
| 55 | |
| 56 | ### Inspection Modes |
| 57 | |
| 58 | The skill supports two modes based on user intent: |
| 59 | |
| 60 | | Mode | When to use | Scope | |
| 61 | |------|-------------|-------| |
| 62 | | **Full inspection** | User asks for a general health check / 巡检 / 全面检查 | All resource types in the environment | |
| 63 | | **Targeted inspection** | User reports a specific error or asks about a specific resource | One resource type or a specific resource | |
| 64 | |
| 65 | ### Full Inspection Workflow |
| 66 | |
| 67 | Follow these steps in order for a comprehensive environment health check: |
| 68 | |
| 69 | **Step 1 — Environment Check** |
| 70 | |
| 71 | ``` |
| 72 | envQuery(action=" |