What problem does it solve? Observing a running system from the terminal requires knowing each observability backend's CLI, authentication flow, and query syntax, which differ across Grafana, Datadog, Dynatrace, Azure Monitor, and AWS CloudWatch. This Skill centralizes per-stack references and ready-made query scripts so an agent can authenticate, discover what a service emits, and query it without memorizing each platform. ## Core Features & Use Cases - Per-stack references: One reference file per backend covering CLI setup, discovery-then-query commands per signal, configuration display, and what stack_config persists. - Query scripts: Deterministic Python scripts (grafana-.py, azure-monitor-.py, cloudwatch-*.py) for discovery, metrics, logs, traces, and connection proofs, each with --json output and the exact CLI commands recorded. - Custom stack support: A documented contract (references/CONTRACT.md) and a checker script for authoring guides for backends the package does not ship. - Use Case: While observing a load-test run against Azure Container Apps, use the azure-monitor-discover.py script to list what each service emits, then query traces and logs by operation_Id to diagnose a failing request. ## Quick Start Ask the agent to observe the current run against your configured observability stack, for example by requesting the slowest requests and their traces from Azure Monitor for the last 30 minutes.