What problem does it solve? Investigating production issues requires querying time-series metrics, but unbounded queries against high-cardinality data flood the context and slow down analysis. This Skill enforces a context-efficient workflow for exploring VictoriaMetrics data safely. ## Core Features & Use Cases - Cardinality Discovery: Run get_statistics.py first to see active series counts, top metric names, and top jobs before querying. - Targeted MetricsQL Queries: Execute instant or range queries with output limits, supporting full PromQL plus MetricsQL extensions like WITH templates, rollup functions, and label manipulation. - Label Exploration: Discover available label names and values scoped to specific series selectors. - Use Case: During an incident, check the error rate for a service by running statistics first, then querying topk(5, sum by (service) (rate(http_requests_total{status=~"5.."}[5m]))) to find the worst offenders without dumping thousands of series. ## Quick Start Ask the agent to investigate the current error rate for the api job in VictoriaMetrics, starting with metric statistics.