vigil-check

Audit project observability posture and produce a monitoring gaps report.

69|8|Updated Mar 16, 2026

Search Tags:#monitoring #logging #observability #tracing #alerts #sre

Ready to run

npx skills add https://github.com/tonone-ai/tonone --skill vigil-check

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: vigil-check
Source: https://github.com/tonone-ai/tonone/tree/main/team/vigil/skills/vigil-check
Command: npx skills add https://github.com/tonone-ai/tonone --skill vigil-check

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Audit teams struggle to verify complete observability coverage across services, leading to blind spots in metrics, traces, logs, and alerts.

Core Features & Use Cases

Automated discovery of monitoring stacks across services (metrics, tracing, logging, alerting)
Gap analysis for RED metrics, SLOs, and runbooks
Guidance on improving monitoring posture with concrete, implementable steps

Quick Start

Run Vigil on the project to audit services and produce a monitoring coverage report.

Frequently Asked Questions about vigil-check

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

FAQPage Schema

How do I audit my project's observability posture for monitoring gaps?▼

You can audit your observability posture by running an automated discovery process against your services to identify missing metrics, traces, logs, and alerts. This generates a comprehensive gaps report highlighting blind spots in your monitoring coverage.

What is observability gap analysis and why do I need it before launch?▼

Observability gap analysis is the process of verifying complete monitoring coverage across services to prevent blind spots. You need it for pre-launch reviews to ensure metrics, traces, logging configurations, and alert coverage are fully enforced before deployment.

Does observability auditing check for RED metrics and SLO coverage?▼

Yes, observability auditing includes gap analysis specifically for RED metrics, SLOs, and runbooks. It enforces the detection of these critical reliability components to ensure your monitoring posture meets ongoing service reliability standards.

What is the best way to close monitoring blind spots across multiple services?▼

The best way to close monitoring blind spots is through automated service-by-service coverage checks that produce a gaps report. This approach provides concrete, implementable steps to improve your monitoring posture systematically across the entire stack.

Can I use this for ongoing reliability assessments or only pre-launch reviews?▼

You can use observability auditing for both pre-launch reviews and ongoing reliability assessments. It applies to continuous service-by-service coverage checks to maintain monitoring standards throughout the service lifecycle.