← Back to Skills Marketplace
VictoriaMetrics
by
James.Yang
· GitHub ↗
· v1.1.0
· MIT-0
168
Downloads
0
Stars
1
Active Installs
3
Versions
Install in OpenClaw
/install victoriametrics
Description
Query and manage VictoriaMetrics time-series database instances. Supports both single-node and cluster deployments with multi-tenancy. Use when the user asks...
Usage Guidance
This skill implements a local CLI that reads/writes a config file in your OpenClaw workspace and makes HTTP(S) requests to the VictoriaMetrics endpoints you configure. Before installing: (1) Be sure you have Node.js available (the SKILL.md uses `node scripts/cli.js`) — the skill metadata does not declare this dependency. (2) Store only credentials you trust in the config file; the CLI will save any username/password you enter to ~/.openclaw/workspace/victoriametrics.json by default. (3) Network calls go to the URLs you configure — do not point them to untrusted external endpoints. (4) If you need least privilege, consider running the tool in an environment with restricted network access or using instance-scoped credentials rather than exposing broad secrets. Overall the files and instructions are coherent with the stated purpose.
Capability Analysis
Type: OpenClaw Skill
Name: victoriametrics
Version: 1.1.0
The victoriametrics skill is a legitimate tool for querying and managing VictoriaMetrics time-series database instances. The core logic in scripts/cli.js uses standard Node.js modules (http, https, fs) to perform PromQL queries and manage local configuration files within the OpenClaw workspace. The requested permissions for file system and network access are necessary for its stated functionality, and no evidence of malicious intent, data exfiltration, or prompt injection was found.
Capability Assessment
Purpose & Capability
The skill's name, description, SKILL.md, reference docs, and included CLI implementation all align: this is a CLI for querying/managing VictoriaMetrics. Minor gap: the runtime instructions assume Node (invoke via `node scripts/cli.js`) but the registry metadata lists no required binaries/dependencies. Declaring Node.js as a required binary would be expected.
Instruction Scope
Runtime instructions and the CLI implementation stay within scope: they read a local config file, prompt for credentials, and make HTTP(S) requests to the user-provided VictoriaMetrics endpoints. There are no instructions to read unrelated system files, enumerate other services, or transmit data to unexpected external endpoints.
Install Mechanism
No install spec is provided (instruction-only with an included script). The code is shipped in the skill and will run when the user invokes the CLI with Node. There are no downloads from external URLs or archive extraction steps in the install metadata.
Credentials
The skill does not require any declared environment variables or secrets in registry metadata. It documents optional legacy env vars (VICTORIAMETRICS_URL, _USER, _PASSWORD) and supports per-instance credentials stored in the local config. The variables and file access it requests are proportional to its purpose.
Persistence & Privilege
always:false and the skill does not request permanent platform-wide privileges. It writes its own config file under the user's workspace (~/.openclaw/workspace/victoriametrics.json) which is expected behavior for a CLI; it does not attempt to modify other skills or global agent settings.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install victoriametrics - After installation, invoke the skill by name or use
/victoriametrics - Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.1.0
Initial public release: support single-node and cluster deployments, node_exporter and categraf collectors, GPU monitoring, comprehensive documentation
v1.0.1
Add security notice, fix missing files
v1.0.0
VictoriaMetrics Skill 1.0.0 – Initial Release
- Query and manage VictoriaMetrics instances, supporting both single-node and cluster deployments (multi-tenancy included)
- Interactive setup wizard and flexible config file support (with environment variable fallback)
- Run PromQL queries across multiple instances at once; includes commands for common monitoring tasks (CPU, memory, disk, GPU, service health)
- Output results per instance; individual errors do not prevent aggregated results
- Supports metrics from node_exporter, categraf, NVIDIA DCGM, and Prometheus-compatible exporters
- Includes commands for instance management, metric listing, alert checks, and health status
Metadata
Frequently Asked Questions
What is VictoriaMetrics?
Query and manage VictoriaMetrics time-series database instances. Supports both single-node and cluster deployments with multi-tenancy. Use when the user asks... It is an AI Agent Skill for Claude Code / OpenClaw, with 168 downloads so far.
How do I install VictoriaMetrics?
Run "/install victoriametrics" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is VictoriaMetrics free?
Yes, VictoriaMetrics is completely free, licensed under MIT-0. You can download, install and use it at no cost.
Which platforms does VictoriaMetrics support?
VictoriaMetrics is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created VictoriaMetrics?
It is built and maintained by James.Yang (@yangjinzhao); the current version is v1.1.0.
More Skills