victoria-metrics

Routes VictoriaMetrics tasks to the correct sub-skill for operators, queries, logs, and traces.

4|2|Updated Jun 1, 2026
One-click install
npx skills add https://github.com/Aidas-dev/k8s-agent-skills --skill victoria-metrics-aidas-dev
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: victoria-metrics
Source: https://github.com/Aidas-dev/k8s-agent-skills/tree/main/skills/victoria-metrics
Command: npx skills add https://github.com/Aidas-dev/k8s-agent-skills --skill victoria-metrics-aidas-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? VictoriaMetrics spans many distinct workflows — operator CRDs, PromQL/MetricsQL queries, cardinality analysis, log search, and trace inspection — and picking the wrong approach wastes time. This Skill acts as a router that maps your request to the correct specialized VictoriaMetrics sub-skill. ## Core Features & Use Cases - Task-to-Skill Routing: Directs requests to one of seven sub-skills covering operator CRDs, querying, cardinality analysis, unused metrics detection, log search, trace queries, and trace analysis. - Quick Reference Tables: Provides lookup tables mapping common requests like "Create a VMAgent" or "Find metrics with too many labels" to the right skill. - Use Case: You ask to set up a VMServiceScrape for your application; the router identifies victoriametrics-operator as the correct skill so the agent loads the right operational instructions. ## Quick Start Ask the agent to help with any VictoriaMetrics task, such as writing a PromQL query or configuring a VMAlert, and it will route you to the appropriate sub-skill.

Frequently Asked Questions about victoria-metrics

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

FAQPage Schema
How do I choose the right VictoriaMetrics skill for my task?▼

Match your goal to the routing table: operator CRD work goes to victoriametrics-operator, PromQL/MetricsQL queries to victoriametrics-query, log searches to victorialogs-query, and trace work to victoriatraces-query or vm-trace-analyzer.

Which VictoriaMetrics skill handles VMAgent and VMServiceScrape configuration?▼

The victoriametrics-operator skill covers all VM Operator CRDs, including VMAgent, VMServiceScrape, VMSingle, VMAlert, and VLogs. Use it whenever you create or configure operator-managed resources.

Can I analyze high cardinality metrics with VictoriaMetrics?▼

Yes, the victoriametrics-cardinality-analysis skill handles high-cardinality investigation and optimization. For finding metrics that are never queried, use victoriametrics-unused-metrics-analysis instead.

Does this skill query VictoriaMetrics logs and traces directly?▼

No, it is a router only. Log searches with LogsQL are delegated to victorialogs-query, and trace queries via the Jaeger-compatible API go to victoriatraces-query.

Why is my PromQL query slow on VictoriaMetrics?▼

Slow queries are diagnosed with the vm-trace-analyzer skill, which analyzes VM query trace JSON output. Route requests about slow query performance there rather than to the general query skill.