{
  "markdown": "# VictoriaMetrics skills\n\nA collection of agent skills for interacting with the VictoriaMetrics ecosystem.\nThese skills help AI agents and automation tools understand, operate, and troubleshoot VictoriaMetrics products such as metrics, logs, and traces storage.\n\n## Available Plugins\n\n| Plugin | Skills | Purpose |\n|--------|--------|---------|\n| [query](plugins/query/) | victoriametrics-query, victorialogs-query, victoriatraces-query, alertmanager-query | Query metrics, logs, traces, and alerts |\n| [diagnostics](plugins/diagnostics/) | vm-trace-analyzer, investigating-with-observability, victoriametrics-cardinality-analysis, victoriametrics-unused-metrics-analysis, stream-aggregation-helper | Query trace analysis, multi-signal investigations, cardinality optimization, unused metric detection, stream aggregation design |\n| [vmanomaly](plugins/vmanomaly/) | vmanomaly-query, vmanomaly-config, vmanomaly-review | Operate the vmanomaly API, build and tune anomaly-detection configurations, and review detection quality |\n| [docs](plugins/docs/) | victoriametrics-docs | Look up a command-line flag, an HTTP API path or a query construct in the published documentation |\n\n## Installation\n\n### Via [skills.sh](https://skills.sh)\n\nInstall all skills:\n\n```\nnpx skills add VictoriaMetrics/skills\n```\n\nInstall a specific skill:\n\n```\nnpx skills add VictoriaMetrics/skills --skill victoriametrics-query\nnpx skills add VictoriaMetrics/skills --skill victorialogs-query\nnpx skills add VictoriaMetrics/skills --skill victoriatraces-query\nnpx skills add VictoriaMetrics/skills --skill alertmanager-query\nnpx skills add VictoriaMetrics/skills --skill victoriametrics-docs\nnpx skills add VictoriaMetrics/skills --skill investigating-with-observability\nnpx skills add VictoriaMetrics/skills --skill vm-trace-analyzer\nnpx skills add VictoriaMetrics/skills --skill victoriametrics-cardinality-analysis\nnpx skills add VictoriaMetrics/skills --skill victoriametrics-unused-metrics-analysis\nnpx skills add VictoriaMetrics/skills --skill stream-aggregation-helper\nnpx skills add VictoriaMetrics/skills --skill vmanomaly-query\nnpx skills add VictoriaMetrics/skills --skill vmanomaly-config\nnpx skills add VictoriaMetrics/skills --skill vmanomaly-review\n```\n\n### Via Claude Code plugin marketplace\n\nAdd the marketplace source:\n\n```\n/plugin marketplace add VictoriaMetrics/skills\n```\n\nInstall plugins:\n\n```\n/plugin install query@victoriametrics-tools # Query VictoriaStack components and AlertManager\n/plugin install diagnostics@victoriametrics-tools # Troubleshooting and query trace analysis\n/plugin install vmanomaly@victoriametrics-tools # Configure, operate, tune, and review anomaly detection\n/plugin install docs@victoriametrics-tools # Look up flags, API paths and query constructs in the published docs\n```\n\n## Skills\n\n### Query plugin\n\n| Skill | Purpose |\n|-------|---------|\n| victoriametrics-query | Run PromQL/MetricsQL queries, discover metrics and labels, inspect alerts, rules, TSDB status, and debug configs |\n| victorialogs-query | Search logs with LogsQL, run stats queries, discover fields and streams, analyze log volume |\n| victoriatraces-query | Discover services and operations, search traces by duration/tags, retrieve traces by ID, map dependencies |\n| alertmanager-query | List active/silenced alerts, create and manage silences, check alert inhibition state |\n\n### Diagnostics plugin\n\n| Skill | Purpose |\n|-------|---------|\n| vm-trace-analyzer | Analyze VictoriaMetrics query trace JSON to diagnose slow queries and produce performance reports |\n| investigating-with-observability | Orchestrate multi-signal investigations across metrics, logs, and traces with structured phases |\n| victoriametrics-cardinality-analysis | Analyze time series cardinality to find optimization opportunities — unused metrics, high-cardinality labels, histogram bloat |\n| victoriametrics-unused-metrics-analysis | Find unused and rarely-queried metrics, then suggest drop rules and relabel configs to reduce waste |\n| stream-aggregation-helper | Design vmagent stream aggregation rules — gate, intake, pick interval/output/by-without, generate YAML, plan rollout, verify with `vm_streamaggr_*` |\n\n### Docs plugin\n\n| Skill | Purpose |\n|-------|---------|\n| victoriametrics-docs | Confirm a command-line flag, an HTTP API path or a MetricsQL/LogsQL construct against the published documentation before naming it |\n\n### vmanomaly plugin\n\n| Skill | Purpose |\n|-------|---------|\n| vmanomaly-query | Operate vmanomaly v1.30+ HTTP APIs for health, compatibility, schemas, profiling, shared autotune, validation, and bounded detection tasks |\n| vmanomaly-config | Triage static alerting versus ML, select and tune a model from real time-series characteristics, and produce validated deployment artifacts |\n| vmanomaly-review | Audit an existing configuration against runtime schemas and real data, reproduce detections, and verify proposed fixes |\n\nEach vmanomaly skill is independently installable. When query or diagnostics skills are also\navailable, the vmanomaly workflows can use them for metric/log discovery, cardinality checks,\nexisting-alert review, and multi-signal incident correlation.\n\n## Usage\n\nOnce installed, skills are available as slash commands and are also triggered automatically when Claude detects a matching request:\n\n```\n/query:victoriametrics-query            - query metrics, discover labels, check alerts and rules\n/query:victorialogs-query               - search logs, run stats, discover fields\n/query:victoriatraces-query             - search traces, discover services, map dependencies\n/query:alertmanager-query               - list alerts, manage silences\n/diagnostics:vm-trace-analyzer          - perform an analysis of the query performance based on provided trace\n/diagnostics:investigating-with-observability - structured multi-signal investigation\n/diagnostics:victoriametrics-cardinality-analysis  - cardinality analysis and optimization recommendations\n/diagnostics:victoriametrics-unused-metrics-analysis - find unused metrics and suggest drop rules\n/diagnostics:stream-aggregation-helper             - design and verify stream aggregation rules\n/vmanomaly:vmanomaly-query                         - inspect and operate the vmanomaly API\n/vmanomaly:vmanomaly-config                        - build and tune a validated anomaly configuration\n/vmanomaly:vmanomaly-review                        - audit an existing anomaly configuration\n/docs:victoriametrics-docs                         - check a flag, an API path or a query construct against the docs\n```\n\n**Example prompts that trigger skills:**\n\n- \"What alerts are currently firing?\" → `alertmanager-query`\n- \"Show me error logs for namespace production in the last hour\" → `victorialogs-query`\n- \"Find slow traces for the checkout service\" → `victoriatraces-query`\n- \"What's the request rate for my-api over the last 6 hours?\" → `victoriametrics-query`\n- \"This query is slow, here's the trace JSON — analyze it\" → `vm-trace-analyzer`\n- \"Pod X is crash looping — investigate\" → `investigating-with-observability`\n- \"Which metrics have the highest cardinality?\" → `victoriametrics-cardinality-analysis`\n- \"Find metrics that nobody queries\" → `victoriametrics-unused-metrics-analysis`\n- \"Help me aggregate this high-cardinality metric at vmagent\" → `stream-aggregation-helper`\n- \"Profile this query and choose a vmanomaly model\" → `vmanomaly-config`\n- \"Check whether my persisted vmanomaly state is compatible with v1.30\" → `vmanomaly-query`\n- \"Review why this anomaly model produces too many detections\" → `vmanomaly-review`\n- \"Is there a flag to change the retention period?\" → `victoriametrics-docs`\n\n## Environment Variables\n\nThe query, diagnostics and vmanomaly skills use `curl` and expect these environment variables.\nThe `victoriametrics-docs` skill reads the published documentation over HTTP and needs none of them.\n\n```bash\nVM_METRICS_URL        # VictoriaMetrics query endpoint (e.g., http://localhost:8428)\nVM_LOGS_URL           # VictoriaLogs endpoint (e.g., http://localhost:9428)\nVM_TRACES_URL         # VictoriaTraces with /select/jaeger prefix (e.g., http://localhost:10428/select/jaeger)\nVM_ALERTMANAGER_URL   # AlertManager endpoint (optional)\nVM_ANOMALY_URL        # vmanomaly endpoint, including path prefix if configured (e.g., http://localhost:8490)\nVM_CURL_CONFIG        # Path to a mode-0600 curl config file containing the auth header\n                      # (leave unset for unauthenticated local instances - defaults to /dev/null)\n```\n\n### Authentication setup\n\nSkills pass credentials to `curl` through a [curl config file](https://curl.se/docs/manpage.html#-K)\ninstead of command-line arguments. This keeps tokens out of process listings, shell history, and\nagent transcripts. Every command uses the same pattern:\n\n```bash\ncurl -q --config \"${VM_CURL_CONFIG:-/dev/null}\" -s \"$VM_METRICS_URL/api/v1/query?query=up\"\n```\n\nFor unauthenticated local instances no setup is needed: when `VM_CURL_CONFIG` is unset, curl reads\n`/dev/null` and sends no auth header.\n\nFor authenticated instances, create a config file readable only by you and point `VM_CURL_CONFIG` at it:\n\n```bash\nmkdir -p \"$HOME/.config/victoriametrics\"\ntouch \"$HOME/.config/victoriametrics/curl.conf\"\nchmod 0600 \"$HOME/.config/victoriametrics/curl.conf\"\ncat > \"$HOME/.config/victoriametrics/curl.conf\" <<'EOF'\nheader = \"Authorization: Bearer <token>\"\nEOF\nexport VM_CURL_CONFIG=\"$HOME/.config/victoriametrics/curl.conf\"\n```\n\nFor Basic auth, use `user = \"username:password\"` instead of the `header` line.\n\n### Migrating from VM_AUTH_HEADER\n\nEarlier versions of these skills read the auth header from the `VM_AUTH_HEADER` environment variable\n(`export VM_AUTH_HEADER=\"Authorization: Bearer <token>\"`) and passed it to curl via `-H`. That exposed\nthe token in process listings, shell history, and agent transcripts, so skills now read it from a curl\nconfig file instead. `VM_AUTH_HEADER` is no longer used by any skill.\n\nTo migrate:\n\n1. Move the header line into a mode-0600 curl config file:\n\n   ```bash\n   mkdir -p \"$HOME/.config/victoriametrics\"\n   touch \"$HOME/.config/victoriametrics/curl.conf\"\n   chmod 0600 \"$HOME/.config/victoriametrics/curl.conf\"\n   printf 'header = \"%s\"\\n' \"$VM_AUTH_HEADER\" > \"$HOME/.config/victoriametrics/curl.conf\"\n   ```\n\n2. Replace `VM_AUTH_HEADER` with `VM_CURL_CONFIG` wherever you export it (shell profile, CI secrets,\n   agent configuration):\n\n   ```bash\n   export VM_CURL_CONFIG=\"$HOME/.config/victoriametrics/curl.conf\"\n   unset VM_AUTH_HEADER\n   ```\n\n3. If you never set `VM_AUTH_HEADER` (unauthenticated local instances), no action is needed.\n",
  "bytes": 10644,
  "sha": "74e2ac60f087c99ce6d551aac3f457592d5349d409bcbe099edecfb07920bf35",
  "repo_slug": "victoriametrics/skills",
  "fonte": "repo",
  "truncated": false,
  "api": "https://api.agentalog.com/api/listings/skl_victoriametrics_skills_investigating_wit_e245a49d/readme"
}