cc-scout-observability

Audit observability coverage across logging, tracing, metrics, and health endpoints.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/z23cc/cc-code --skill cc-scout-observability
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: cc-scout-observability
Source: https://github.com/z23cc/cc-code/tree/main/skills/cc-scout-observability
Command: npx skills add https://github.com/z23cc/cc-code --skill cc-scout-observability

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Observability gaps across logging, tracing, metrics, and health endpoints are identified and reported to improve system visibility.

Core Features & Use Cases

  • Observability Coverage Audit: scans logs, traces, metrics, and readiness/endpoints to determine coverage and gaps.
  • Actionable Remediation Guidance: provides concrete steps to improve instrumentation and health checks.
  • Use Case: ideal for microservices architectures needing a consolidated view of observability readiness.

Quick Start

Run an observability audit across my services to produce a coverage report of logging, tracing, metrics, and health endpoints.

Frequently Asked Questions about cc-scout-observability

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

FAQPage Schema
How do I audit observability coverage for logging, tracing, metrics, and health endpoints?▼

To audit observability coverage, the Skill scans logs, traces, metrics, and readiness endpoints across microservices to determine instrumentation gaps and produces a standardized report highlighting risks and remediation steps.

What is an observability audit for microservices and distributed systems?▼

An observability audit is a readiness check across microservices environments that evaluates logging, tracing, metrics, and health endpoint instrumentation to identify visibility gaps and output actionable remediation guidance.

How do I identify instrumentation gaps in distributed systems?▼

You can identify instrumentation gaps by running an observability audit that scans distributed systems for missing logging, tracing, metrics, and health endpoint coverage, then outputs a report with concrete remediation steps.

What is the best way to generate remediation steps for observability gaps?▼

The best way to generate remediation steps is to run an observability audit that scans your services for coverage gaps in logging, tracing, and metrics, producing a standardized report with actionable guidance to improve instrumentation.

Can I check health endpoint and readiness checks across multiple microservices?▼

Yes, you can check health endpoint and readiness checks across multiple microservices by applying the observability audit to your distributed systems to evaluate coverage and identify missing instrumentation across environments.