ops-inspector

Inspects CloudBase resources and aggregates error logs for health diagnosis.

Updated May 14, 2026
One-click install
npx skills add https://github.com/study-yang/Vieb-Coding-- --skill ops-inspector-study-yang
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ops-inspector
Source: https://github.com/study-yang/Vieb-Coding--/tree/main/%E5%BE%AE%E4%BF%A1%E5%B0%8F%E7%A8%8B%E5%BA%8F-%E5%BF%AB%E8%AE%B0/.codebuddy/skills/ops-inspector
Command: npx skills add https://github.com/study-yang/Vieb-Coding-- --skill ops-inspector-study-yang

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Diagnosing issues across CloudBase resources like cloud functions, CloudRun services, and databases requires manually checking logs and statuses in multiple places, making root cause analysis slow and error-prone. ## Core Features & Use Cases - Full Environment Inspection: Runs a step-by-step health check covering environment binding, CLS log service status, cloud functions, and CloudRun services, producing a structured severity-rated report. - Targeted Diagnosis: Investigates a specific failing function, CloudRun service, or database using focused log queries and resource detail lookups. - AIOps-Style Root Cause Analysis: Correlates error patterns across services to hypothesize root causes and recommend prioritized remediation steps with console links. - Use Case: A user reports their mini-program backend is failing. The skill checks recent function logs, searches CLS for ERROR entries in the last 24 hours, identifies a database timeout pattern, and recommends the relevant fix skill. ## Quick Start Run a full health inspection of my CloudBase environment and summarize any errors found in the last 24 hours.

Frequently Asked Questions about ops-inspector

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run a health check on CloudBase resources?

Start with envQuery to confirm the environment is bound, then check CLS log service status, list cloud functions and CloudRun services, and search recent error logs. The skill produces a structured report with severity levels and recommendations.

How to search CloudBase error logs with CLS?

Use queryLogs with action searchLogs, a queryString like ERROR or functionName:<name> AND level:ERROR, and a service of tcb or tcbr. Always specify a startTime and endTime to scope results to a relevant window.

Why does queryLogs fail during CloudBase inspection?

Log queries fail when the CLS log service is not enabled for the environment. Check first with queryLogs action checkLogService, and enable CLS in the CloudBase console if it is disabled.

Can this skill fix CloudBase errors automatically?

No, it is read-only and diagnostic. It identifies issues, hypothesizes root causes, and recommends remediation, but actual fixes should be applied through implementation skills like cloud-functions or cloudrun-development.

What time range should I use for CloudBase log searches?

Use the last hour for a quick check, the last 24 hours for a standard inspection, and up to 7 days for trend analysis. For a specific incident, narrow the window to the reported time using ISO 8601 timestamps.