Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Tencent SkillHub · Data Analysis
Prometheus
Query Prometheus monitoring data to check server metrics, resource usage, and system health. Use when the user asks about server status, disk space, CPU/memory usage, network stats, or any metrics collected by Prometheus. Supports HTTP Basic Auth via environment variables.
skill openclawclawhub Free
Query Prometheus monitoring data to check server metrics, resource usage, and system health. Use when the user asks about server status, disk space, CPU/memory usage, network stats, or any metrics collected by Prometheus. Supports HTTP Basic Auth via environment variables.
⬇ 0 downloads ★ 0 stars Unverified but indexed
Install for OpenClaw
Quick setup
- Download the package from Yavira.
- Extract the archive and review SKILL.md first.
- Import or place the package into your OpenClaw setup.
Package facts
- Download mode
- Yavira redirect
- Package format
- ZIP package
- Source platform
- Tencent SkillHub
- What's included
- SKILL.md, package.json, scripts/cli.js, scripts/common.js, scripts/query.js
Validation
- Use the Yavira download entry.
- Review SKILL.md after the package is downloaded.
- Confirm the extracted package contains the expected setup assets.
Install with your agent
Agent handoff
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
- Download the package from Yavira.
- Extract it into a folder your agent can access.
- Paste one of the prompts below and point your agent at the extracted folder.
New install
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
Upgrade existing
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
Trust & source
Release facts
- Source
- Tencent SkillHub
- Verification
- Indexed source record
- Version
- 1.1.0
Provenance
- Publisher
- Akellacom
- Source page
- View original listing
- Canonical URL
- Open canonical page
Documentation
Prometheus Skill
Query Prometheus monitoring data from one or multiple instances. Supports federation across multiple Prometheus servers with a single command.
1. Initial Setup
Run the interactive configuration wizard: cd ~/.openclaw/workspace/skills/prometheus node scripts/cli.js init This will create a prometheus.json config file in your OpenClaw workspace (~/.openclaw/workspace/prometheus.json).
2. Start Querying
# Query default instance node scripts/cli.js query 'up' # Query all instances at once node scripts/cli.js query 'up' --all # List configured instances node scripts/cli.js instances
Config File Location
By default, the skill looks for config in your OpenClaw workspace: ~/.openclaw/workspace/prometheus.json Priority order: Path from PROMETHEUS_CONFIG environment variable ~/.openclaw/workspace/prometheus.json ~/.openclaw/workspace/config/prometheus.json ./prometheus.json (current directory) ~/.config/prometheus/config.json
Config Format
Create prometheus.json in your workspace (or use node cli.js init): { "instances": [ { "name": "production", "url": "https://prometheus.example.com", "user": "admin", "password": "secret" }, { "name": "staging", "url": "http://prometheus-staging:9090" } ], "default": "production" } Fields: name — unique identifier for the instance url — Prometheus server URL user / password — optional HTTP Basic Auth credentials default — which instance to use when none specified
Environment Variables (Legacy)
For single-instance setups, you can use environment variables: export PROMETHEUS_URL=https://prometheus.example.com export PROMETHEUS_USER=admin # optional export PROMETHEUS_PASSWORD=secret # optional
Global Flags
FlagDescription-c, --config <path>Path to config file-i, --instance <name>Target specific instance-a, --allQuery all configured instances
Commands
Setup # Interactive configuration wizard node scripts/cli.js init Query Metrics cd ~/.openclaw/workspace/skills/prometheus # Query default instance node scripts/cli.js query 'up' # Query specific instance node scripts/cli.js query 'up' -i staging # Query ALL instances at once node scripts/cli.js query 'up' --all # Custom config file node scripts/cli.js query 'up' -c /path/to/config.json Common Queries Disk space usage: node scripts/cli.js query '100 - (node_filesystem_avail_bytes / node_filesystem_size_bytes * 100)' --all CPU usage: node scripts/cli.js query '100 - (avg by (instance) (irate(node_cpu_seconds_total{mode="idle"}[5m])) * 100)' --all Memory usage: node scripts/cli.js query '(node_memory_MemTotal_bytes - node_memory_MemAvailable_bytes) / node_memory_MemTotal_bytes * 100' --all Load average: node scripts/cli.js query 'node_load1' --all
List Configured Instances
node scripts/cli.js instances Output: { "default": "production", "instances": [ { "name": "production", "url": "https://prometheus.example.com", "hasAuth": true }, { "name": "staging", "url": "http://prometheus-staging:9090", "hasAuth": false } ] }
Other Commands
# List all metrics matching pattern node scripts/cli.js metrics 'node_memory_*' # Get label names node scripts/cli.js labels --all # Get values for a label node scripts/cli.js label-values instance --all # Find time series node scripts/cli.js series '{__name__=~"node_cpu_.*", instance=~".*:9100"}' --all # Get active alerts node scripts/cli.js alerts --all # Get scrape targets node scripts/cli.js targets --all
Multi-Instance Output Format
When using --all, results include data from all instances: { "resultType": "vector", "results": [ { "instance": "production", "status": "success", "resultType": "vector", "result": [...] }, { "instance": "staging", "status": "success", "resultType": "vector", "result": [...] } ] } Errors on individual instances don't fail the entire query — they appear with "status": "error" in the results array.
Common Queries Reference
MetricPromQL QueryDisk free %node_filesystem_avail_bytes / node_filesystem_size_bytes * 100Disk used %100 - (node_filesystem_avail_bytes / node_filesystem_size_bytes * 100)CPU idle %avg by (instance) (irate(node_cpu_seconds_total{mode="idle"}[5m])) * 100Memory used %(node_memory_MemTotal_bytes - node_memory_MemAvailable_bytes) / node_memory_MemTotal_bytes * 100Network RXrate(node_network_receive_bytes_total[5m])Network TXrate(node_network_transmit_bytes_total[5m])Uptimenode_time_seconds - node_boot_time_secondsService upup
Notes
Time range defaults to last 1 hour for instant queries Use range queries [5m] for rate calculations All queries return JSON with data.result containing the results Instance labels typically show host:port format When using --all, queries run in parallel for faster results Config is stored outside the skill directory so it persists across skill updates
Category context
Data access, storage, extraction, analysis, reporting, and insight generation.
Source: Tencent SkillHub
Largest current source with strong distribution and engagement signals.
Package contents
Included in package
3 Scripts1 Docs1 Config
- SKILL.md
- scripts/cli.js
- scripts/common.js
- scripts/query.js
- package.json