monitoring

Inspect service health, observability signals, and incident evidence read-only.

Updated May 8, 2026
One-click install
npx skills add https://github.com/ace3/skills --skill monitoring-ace3
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: monitoring
Source: https://github.com/ace3/skills/tree/main/skills/monitoring
Command: npx skills add https://github.com/ace3/skills --skill monitoring-ace3

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Read-only visibility into service health, observability signals, and incident evidence to reduce risk and speed recovery.

Core Features & Use Cases

  • Passive read-only: metrics, logs, traces, dashboards, alerts, inventory, and health summaries.
  • Design change: proposed dashboards, instrumentation, SLO, or alert rule changes.
  • External lookups: OSV, NVD, GitLab, or vendor vulnerability checks only when network access and scope are explicit.
  • Privileged changes: gating through explicit plan, approvals, rollback notes, and non-destructive verification.

Quick Start

Load the base layer and begin classification to generate a read-only health assessment.

Frequently Asked Questions about monitoring

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

FAQPage Schema
How do I get read-only visibility into service health and observability signals?

Read-only visibility into service health and observability signals is provided by assessing metrics, logs, traces, and dashboards without making destructive changes. This passive monitoring approach reduces risk and speeds up incident recovery.

How do I assess alert quality and triage incidents without modifying the system?

Alert quality assessment and incident triage are handled through non-destructive verification of observability signals. The system enforces read-only defaults and planning gates, requiring explicit approval for any privileged changes.

Can I propose changes to SLOs and alert rules while reviewing dashboards?

Proposed changes to SLOs, alert rules, and dashboards are supported as design changes. Any privileged modifications require an explicit plan, approvals, rollback notes, and non-destructive verification before execution.

Does the monitoring workflow support external vulnerability checks from NVD and OSV?

External vulnerability checks from OSV, NVD, GitLab, or vendors are supported only when network access and explicit scope are defined. These lookups maintain read-only safety while gathering incident evidence.

What is the best way to perform drift and inventory reviews across multiple environments?

Drift and inventory reviews across systems and environments are performed using read-only health summaries and observability signals. This passive classification generates health assessments without risking system state.

Why are privileged changes gated during incident response and monitoring workflows?

Privileged changes are gated through explicit plans and approvals to enforce non-destructive verification. This planning gate ensures that incident triage and monitoring visibility remain safe and do not inadvertently alter system state.