Agent skill

Prometheus Monitoring

by automateyournetwork in automateyournetwork/netclaw

Prometheus monitoring — PromQL instant/range queries, metric discovery, metadata, scrape target health, system health checks (6 tools).

Apache-2.0Auto-check: notesDevOps & Cloud

Install Prometheus Monitoring

skills CLI

$ npx skills add automateyournetwork/netclaw --skill prometheus-monitoring -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install automateyournetwork/netclaw prometheus-monitoring --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/automateyournetwork/netclaw.git skills-src && mkdir -p .claude/skills && cp -r skills-src/workspace/skills/prometheus-monitoring .claude/skills/prometheus-monitoring && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "prometheus-monitoring" agent skill from https://github.com/automateyournetwork/netclaw/tree/main/workspace/skills/prometheus-monitoring into .claude/skills/prometheus-monitoring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "prometheus-monitoring", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/automateyournetwork/netclaw/tree/main/workspace/skills/prometheus-monitoring

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add automateyournetwork/netclaw --skill prometheus-monitoring -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install automateyournetwork/netclaw prometheus-monitoring --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/automateyournetwork/netclaw.git skills-src && mkdir -p .agents/skills && cp -r skills-src/workspace/skills/prometheus-monitoring .agents/skills/prometheus-monitoring && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "prometheus-monitoring" agent skill from https://github.com/automateyournetwork/netclaw/tree/main/workspace/skills/prometheus-monitoring into .agents/skills/prometheus-monitoring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "prometheus-monitoring", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add automateyournetwork/netclaw --skill prometheus-monitoring -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install automateyournetwork/netclaw prometheus-monitoring --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/automateyournetwork/netclaw.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/workspace/skills/prometheus-monitoring .cursor/skills/prometheus-monitoring && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "prometheus-monitoring" agent skill from https://github.com/automateyournetwork/netclaw/tree/main/workspace/skills/prometheus-monitoring into .cursor/skills/prometheus-monitoring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "prometheus-monitoring", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/automateyournetwork/netclaw.git --path workspace/skills/prometheus-monitoring

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add automateyournetwork/netclaw --skill prometheus-monitoring -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install automateyournetwork/netclaw prometheus-monitoring --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/automateyournetwork/netclaw.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/workspace/skills/prometheus-monitoring .gemini/skills/prometheus-monitoring && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "prometheus-monitoring" agent skill from https://github.com/automateyournetwork/netclaw/tree/main/workspace/skills/prometheus-monitoring into .gemini/skills/prometheus-monitoring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "prometheus-monitoring", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install automateyournetwork/netclaw prometheus-monitoring

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add automateyournetwork/netclaw --skill prometheus-monitoring -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/automateyournetwork/netclaw.git skills-src && mkdir -p .github/skills && cp -r skills-src/workspace/skills/prometheus-monitoring .github/skills/prometheus-monitoring && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "prometheus-monitoring" agent skill from https://github.com/automateyournetwork/netclaw/tree/main/workspace/skills/prometheus-monitoring into .github/skills/prometheus-monitoring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "prometheus-monitoring", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add automateyournetwork/netclaw --skill prometheus-monitoring -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install automateyournetwork/netclaw prometheus-monitoring --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/automateyournetwork/netclaw.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/workspace/skills/prometheus-monitoring .opencode/skills/prometheus-monitoring && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "prometheus-monitoring" agent skill from https://github.com/automateyournetwork/netclaw/tree/main/workspace/skills/prometheus-monitoring into .opencode/skills/prometheus-monitoring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "prometheus-monitoring", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: prometheus-monitoring
GitHub stars: 676
Token cost: ~2k tokens
SKILL.md length: 658 words
Files: 1
Skills in repo: 120
Repo updated: Oct 9, 2026
First seen: Oct 7, 2026
Licence: Apache-2.0

At a glance

Prometheus monitoring — PromQL instant/range queries, metric discovery, metadata, scrape target health, system health checks (6 tools).

Works in 7 steps: Health check: health_check — verify… → Discover metrics: list_metrics — find… → Metric metadata:… → …
Lightweight Prometheus query with no Grafana dashboard involved: querying Prometheus metrics
SKILL.md covers MCP Server, How to Run, Environment Variables and Tools, plus 6 more sections
Calls pip3; needs PROMETHEUS_PASSWORD and PROMETHEUS_TOKEN

What it does

Prometheus Monitoring is an agent skill from automateyournetwork/netclaw. Prometheus monitoring — PromQL instant/range queries, metric discovery, metadata, scrape target health, system health checks (6 tools). Use for a direct, lightweight Prometheus query with no Grafana dashboard involved: querying Prometheus metrics, checking scrape targets, investigating alert thresholds, or analyzing network device utilization trends. If the task also needs Grafana dashboards, Loki logs, alerting/OnCall, or panel rendering, use grafana-observability instead.

Its SKILL.md is about 2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in DevOps & Cloud, covering Monitoring and alerting. It works with Prometheus, Grafana and Model Context Protocol. The repository describes itself as: An AI agent that claws through your network. The licence is Apache-2.0.

When your agent uses it

Lightweight Prometheus query with no Grafana dashboard involved: querying Prometheus metrics
Checking scrape targets
Investigating alert thresholds
Analyzing network device utilization trends

Example prompts

“/prometheus-monitoring”

Requirements

Python 3
A credential in PROMETHEUS_TOKEN

Workflow steps

7 steps, taken from the first numbered list in SKILL.md.

Health check: health_check — verify Prometheus is reachable
Discover metrics: list_metrics — find available SNMP/device metrics
Metric metadata: get_metric_metadata(metric="ifHCInOctets") — check type and description
Instant query: execute_query(query="up{job='snmp'}") — check which targets are up
Range query: execute_range_query — trend analysis over time
Scrape targets: get_targets — verify SNMP exporters and device scrape health
GAIT: Record all queries in audit trail

What it can do on your machine

Read from SKILL.md and the folder at commit aa90e7d. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
- pip3
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
- github.com
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names these keys or tokens, usually read from environment variables:
- PROMETHEUS_PASSWORD
- PROMETHEUS_TOKEN
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Prometheus Monitoring loads about 2k tokens when it runs. Until then it costs about 126 tokens; SKILL.md has 658 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~126
When it runs · the whole SKILL.md, loaded when a task matches: ~2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

NoteMentions a .env fileSKILL.md:145

`, or `PROMETHEUS_TOKEN` in `~/.openclaw/.env`. Verify Prometheus allows the configured auth method.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from automateyournetwork/netclaw at commit aa90e7d, republished under its Apache-2.0 licence (© automateyournetwork). 658 words, ~2,029 tokens.

Download SKILL.mdSave it as .claude/skills/prometheus-monitoring/SKILL.md (or your agent's skills folder).

name: prometheus-monitoring
description: Prometheus monitoring — PromQL instant/range queries, metric discovery, metadata, scrape target health, system health checks (6 tools). Use for a direct, lightweight Prometheus query with no Grafana dashboard involved: querying Prometheus metrics, checking scrape targets, investigating alert thresholds, or analyzing network device utilization trends. If the task also needs Grafana dashboards, Loki logs, alerting/OnCall, or panel rendering, use `grafana-observability` instead.
license: Apache-2.0
user-invocable: true

Prometheus Monitoring

MCP Server

Property	Value
Source	pab1it0/prometheus-mcp-server
Transport	stdio (default), SSE, or HTTP
Language	Python 3.10+
Tools	6 (query, range query, list metrics, metadata, targets, health check)
Auth	Basic auth (username/password), bearer token, or unauthenticated
Install	`pip3 install prometheus-mcp-server` (PyPI)
Run	`prometheus-mcp-server` (stdio)

How to Run

bash

# stdio mode (default — used by NetClaw)
PROMETHEUS_URL=http://prometheus:9090 prometheus-mcp-server

# HTTP transport mode
PROMETHEUS_MCP_SERVER_TRANSPORT=http PROMETHEUS_URL=http://prometheus:9090 prometheus-mcp-server

# With basic auth
PROMETHEUS_URL=http://prometheus:9090 PROMETHEUS_USERNAME=admin PROMETHEUS_PASSWORD=secret prometheus-mcp-server

# With bearer token (Grafana Cloud, Thanos, etc.)
PROMETHEUS_URL=https://prom.example.com PROMETHEUS_TOKEN=your_bearer_token prometheus-mcp-server

Environment Variables

Variable	Required	Example	Description
`PROMETHEUS_URL`	Yes	`http://prometheus:9090`	Prometheus server endpoint
`PROMETHEUS_USERNAME`	No	`admin`	Basic auth username
`PROMETHEUS_PASSWORD`	No	`changeme`	Basic auth password
`PROMETHEUS_TOKEN`	No	`eyJhbG...`	Bearer token (Grafana Cloud, Thanos, Cortex)
`PROMETHEUS_URL_SSL_VERIFY`	No	`false`	Disable SSL certificate verification
`PROMETHEUS_REQUEST_TIMEOUT`	No	`30`	Request timeout in seconds (default: 30)
`PROMETHEUS_DISABLE_LINKS`	No	`true`	Disable Prometheus UI links in responses (saves context)
`ORG_ID`	No	`1`	Multi-tenant organization ID (Cortex/Mimir)
`PROMETHEUS_CUSTOM_HEADERS`	No	`{"X-Custom":"val"}`	Additional HTTP headers as JSON
`PROMETHEUS_MCP_SERVER_TRANSPORT`	No	`stdio`	Transport: stdio (default), http, or sse

Tools

Tool	Parameters	What It Does
`execute_query`	`query`, `timeout?`	Execute instant PromQL query at current time
`execute_range_query`	`query`, `start`, `end`, `step`, `timeout?`	Execute PromQL range query over time interval
`list_metrics`	`page?`, `page_size?`	Browse available metric names with pagination
`get_metric_metadata`	`metric?`, `limit?`	Retrieve metric type, help text, and unit info
`get_targets`	none	View scrape target details (up/down, labels, last scrape)
`health_check`	none	Check Prometheus server availability and readiness

Workflow: Network Device Metric Monitoring

When checking Prometheus for network device metrics:

Health check: health_check — verify Prometheus is reachable
Discover metrics: list_metrics — find available SNMP/device metrics
Metric metadata: get_metric_metadata(metric="ifHCInOctets") — check type and description
Instant query: execute_query(query="up{job='snmp'}") — check which targets are up
Range query: execute_range_query — trend analysis over time:
- Interface traffic: rate(ifHCInOctets{instance="router1"}[5m]) * 8
- CPU utilization: device_cpu_utilization{device="core-rtr-01"}
- Interface errors: increase(ifInErrors{device=~".*"}[1h])
- BGP peer state: bgp_peer_state{peer="10.1.1.2"}
Scrape targets: get_targets — verify SNMP exporters and device scrape health
GAIT: Record all queries in audit trail

Example: Interface Utilization Check

health_check()
list_metrics(page=1, page_size=50)
execute_query(query="rate(ifHCInOctets{device='core-rtr-01'}[5m]) * 8")
execute_range_query(query="rate(ifHCOutOctets{device='core-rtr-01'}[5m]) * 8", start="2024-01-01T00:00:00Z", end="2024-01-01T01:00:00Z", step="60s")
get_targets()

Workflow: Alert Threshold Investigation

When investigating whether metrics are crossing alert thresholds:

Discover metrics: list_metrics — find the metric name
Check metadata: get_metric_metadata — understand metric type (counter, gauge, histogram)
Current value: execute_query — get current metric value
Historical trend: execute_range_query — check trend over past 1h/6h/24h
Compare targets: get_targets — check if specific exporters are down
Report: Metric analysis with current value, trend direction, and recommendation

Workflow: Capacity Planning

When analyzing capacity trends for network infrastructure:

Discover metrics: list_metrics — find bandwidth/utilization metrics
Peak analysis: execute_range_query with max_over_time():
- max_over_time(rate(ifHCInOctets{device="core-rtr-01",ifName="Gi0/0"}[5m])[7d:1h]) * 8
95th percentile: execute_range_query with quantile_over_time():
- quantile_over_time(0.95, rate(ifHCInOctets{device="core-rtr-01"}[5m])[30d:1h]) * 8
Growth rate: Compare weekly/monthly averages
Report: Utilization summary with capacity headroom and growth projection

Show full SKILL.md (252 more words)Show less

Integration with Other Skills

Skill	Integration
grafana-observability	Grafana dashboards visualize Prometheus data; use Prometheus skill for direct PromQL when Grafana isn't available or for ad-hoc queries
pyats-health-check	Cross-reference pyATS device health with Prometheus time-series metrics
pyats-routing	Correlate OSPF/BGP state changes with Prometheus metric timelines
gait-session-tracking	Record all Prometheus queries and findings in GAIT audit trail
te-network-monitoring	Pair ThousandEyes path data with Prometheus infrastructure metrics
sdwan-ops	Correlate SD-WAN vManage alarms with Prometheus device metrics
servicenow-change-workflow	Reference Prometheus metrics as evidence in change requests

Important Rules

Prefer read-only operations — all 6 tools are read-only; no Prometheus configuration changes
Use pagination for metric lists — list_metrics supports page and page_size to avoid large responses
Specify time ranges carefully — overly broad execute_range_query time ranges return large result sets
Disable links for context efficiency — set PROMETHEUS_DISABLE_LINKS=true to reduce response size
GAIT audit mandatory — record all Prometheus queries and metric analysis in audit trail
No secrets in queries — never embed credentials or sensitive data in PromQL expressions
Verify connectivity first — use health_check before running queries to confirm Prometheus is reachable

Error Handling

Auth fails (401/403): Check PROMETHEUS_URL, PROMETHEUS_USERNAME/PROMETHEUS_PASSWORD, or PROMETHEUS_TOKEN in ~/.openclaw/.env. Verify Prometheus allows the configured auth method.
Connection refused: Verify PROMETHEUS_URL is reachable. Use health_check to diagnose connectivity.
PromQL syntax errors: Use list_metrics and get_metric_metadata to discover valid metric names before querying.
Empty results: Check get_targets to verify scrape targets are up and the expected labels exist.
Timeout errors: Increase PROMETHEUS_REQUEST_TIMEOUT for slow queries or large result sets.
SSL errors: Set PROMETHEUS_URL_SSL_VERIFY=false for self-signed certificates (development only).

Files

Just SKILL.md in workspace/skills/prometheus-monitoring of automateyournetwork/netclaw.

Open the folder on GitHubat commit aa90e7d

Compare with similar skills

Prometheus Monitoring next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Prometheus Monitoring compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Prometheus Monitoring this skillautomateyournetwork/netclaw	676	—	~2k	Automated safety check: Notes	Apache-2.0	yesterday
Syncmetapawurb/hotpath-rs	1.9k	—	~1.2k	Automated safety check: Notes	MIT	today
Archestra Dev Observabilityarchestra-ai/archestra	4.4k	—	~1.2k	Automated safety check: Pass	Custom licence	today
Frontmcp Observabilityagentfront/frontmcp	146	—	~4.6k	Automated safety check: Pass	Apache-2.0	today
Live Debugmacro-inc/macro	4.6k	—	~2.4k	Automated safety check: Notes	AGPL-3.0	today
Analyzing Experiment Precompute CanaryPostHog/posthog	40k	—	~3.5k	Automated safety check: Pass	Custom licence	yesterday

Similar skills

Syncmeta
pawurb/hotpath-rs
Sync changes from the hotpath, hotpath-macros and hotpath-drain crates to their meta counterparts (hotpath-meta, hotpath-macros-meta and hotpath-drain-meta).
1.9k GitHub stars~1.2k tokensUpdated today
DevOps & CloudAuto-check: notes
Archestra Dev Observability
archestra-ai/archestra
A skill your agent uses when changing Archestra tracing, metrics, OpenTelemetry, Tempo, Grafana, Prometheus, LLM/MCP spans, observability labels, or local observability setup.
4.4k GitHub stars~1.2k tokensUpdated today
DevOps & CloudAuto-check passed
Frontmcp Observability
agentfront/frontmcp
A skill your agent uses when adding tracing, structured logging, metrics, or monitoring to a FrontMCP server.
146 GitHub stars~4.6k tokensUpdated today
DevOps & CloudAuto-check passed
Live Debug
macro-inc/macro
Debug the running local stack with traces, logs, and a shared headless browser.
4.6k GitHub stars~2.4k tokensUpdated today
DevOps & CloudAuto-check: notes
Analyzing Experiment Precompute Canary
PostHog/posthog
Official
Analyze the experiment precompute result-consistency canary across prod-US and prod-EU, deep-dive any issues, and produce an actionable report.
40k GitHub stars~3.5k tokensUpdated yesterday
DevOps & CloudAuto-check passed
Ops Report
haacked/dotfiles
Generate a 24-hour operational health report for a PostHog service by querying Grafana dashboards and Prometheus metrics.
134 GitHub stars~8k tokensUpdated yesterday
DevOps & CloudAuto-check: notes

Questions about Prometheus Monitoring

What does Prometheus Monitoring do?

Prometheus monitoring — PromQL instant/range queries, metric discovery, metadata, scrape target health, system health checks (6 tools). Prometheus Monitoring is an agent skill from automateyournetwork/netclaw. Prometheus monitoring — PromQL instant/range queries, metric discovery, metadata, scrape target health, system health checks (6 tools).

When should I use Prometheus Monitoring?

Prometheus Monitoring fits situations like: lightweight Prometheus query with no Grafana dashboard involved: querying Prometheus metrics; checking scrape targets; investigating alert thresholds; analyzing network device utilization trends.

How do I install Prometheus Monitoring in Claude Code?

Run `npx skills add automateyournetwork/netclaw --skill prometheus-monitoring -a claude-code`. Or copy the skill folder (workspace/skills/prometheus-monitoring in automateyournetwork/netclaw) into .claude/skills/prometheus-monitoring in your project. Claude Code loads it when a task matches its description.

How do I install Prometheus Monitoring in Codex?

Run `npx skills add automateyournetwork/netclaw --skill prometheus-monitoring -a codex`. Or copy the skill folder (workspace/skills/prometheus-monitoring in automateyournetwork/netclaw) into .agents/skills/prometheus-monitoring in your project. Codex loads it when a task matches its description.

Can I use Prometheus Monitoring in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add automateyournetwork/netclaw --skill prometheus-monitoring -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/prometheus-monitoring, .gemini/skills/prometheus-monitoring, .github/skills/prometheus-monitoring and .opencode/skills/prometheus-monitoring in your project.

What does Prometheus Monitoring need to run?

Going by SKILL.md and its folder, Prometheus Monitoring needs the command-line tools its instructions call (pip3) and credentials named PROMETHEUS_PASSWORD and PROMETHEUS_TOKEN. Our summary lists: Python 3; A credential in PROMETHEUS_TOKEN.

Does Prometheus Monitoring access the network?

SKILL.md names 1 domain. As links in the text: github.com. This is read from the text; nothing was executed.

Is Prometheus Monitoring safe to install?

Our automated static check of SKILL.md found notes only (mentions a .env file), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Prometheus Monitoring use?

Prometheus Monitoring is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Prometheus Monitoring use?

About 2k tokens (SKILL.md is roughly 8.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Prometheus Monitoring?

Skills that share tags, products or a category with Prometheus Monitoring: Syncmeta (pawurb/hotpath-rs, 1.9k stars), Archestra Dev Observability (archestra-ai/archestra, 4.4k stars), Frontmcp Observability (agentfront/frontmcp, 146 stars) and Live Debug (macro-inc/macro, 4.6k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Prometheus Monitoring?

automateyournetwork (a GitHub user) maintains it in automateyournetwork/netclaw, which has 676 GitHub stars. The repository holds 120 skills in this directory. The repository was last updated on October 9, 2026.

Source: automateyournetwork/netclaw on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Prometheus Monitoring

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Prometheus Monitoring

MCP Server

How to Run

Environment Variables

Tools

Workflow: Network Device Metric Monitoring

Example: Interface Utilization Check

Workflow: Alert Threshold Investigation

Workflow: Capacity Planning

Integration with Other Skills

Important Rules

Error Handling

Files

Compare with similar skills

Similar skills

More from automateyournetwork/netclaw

Related

Questions about Prometheus Monitoring