vigil-recon

Inventory observability coverage across metrics, traces, logs, and alerts.

69|8|Updated Mar 16, 2026
One-click install
npx skills add https://github.com/tonone-ai/tonone --skill vigil-recon
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vigil-recon
Source: https://github.com/tonone-ai/tonone/tree/main/team/vigil/skills/vigil-recon
Command: npx skills add https://github.com/tonone-ai/tonone --skill vigil-recon

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Inventory what monitoring exists, map coverage, and highlight blind spots across a project to improve reliability and response readiness.

Core Features & Use Cases

  • Discover environment and identify the languages, frameworks, and deployment configs in use to scope observability work.
  • Inventory monitoring platforms across Metrics, Tracing, Logging, Alerting, and Error Tracking to produce a coverage map.
  • Highlight blind spots and provide concrete use cases for improving monitoring and alerting coverage.

Quick Start

Ask Vigil to inventory your observability stack across all services.

Frequently Asked Questions about vigil-recon

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

FAQPage Schema
How do I inventory observability coverage across my software services?

To inventory observability coverage, you scan your environment and deployment configs to map metrics, traces, logs, and alerts. This identifies your current monitoring scope and highlights blind spots across all services without modifying anything.

Can I discover Prometheus and Grafana configurations without modifying my project?

Yes, you can discover monitoring platforms like Prometheus and Grafana without modifying your project. The discovery process performs read-only environment scanning of package managers and deployment configs to inventory existing observability artifacts safely.

How do I check if my OpenTelemetry tracing and logging setup has complete coverage?

To check OpenTelemetry tracing and logging coverage, you inventory your monitoring platforms across all services. This generates a coverage map that identifies which services have active tracing and logging, exposing any gaps in your observability stack.

Does observability reconnaissance work with different package managers and deployment configs?

Observability reconnaissance works across various package managers and deployment configs by performing environment scanning. It identifies the languages, frameworks, and deployment configurations in use to accurately scope your monitoring coverage map.

Why do I need to inventory metrics, traces, logs, and alerts separately?

You inventory metrics, traces, logs, and alerts separately to produce a precise coverage map across distinct observability pillars. This targeted inventorying highlights specific blind spots in error tracking and alerting, improving overall system reliability and response readiness.