โ† All skills
Tencent SkillHub ยท Developer Tools

LibreNMS

Monitor LibreNMS network devices and alerts via API to get status, health sensors, port stats, and unresolved active alerts in read-only mode.

skill openclawclawhub Free
0 Downloads
0 Stars
0 Installs
0 Score
High Signal

Monitor LibreNMS network devices and alerts via API to get status, health sensors, port stats, and unresolved active alerts in read-only mode.

โฌ‡ 0 downloads โ˜… 0 stars Unverified but indexed

Install for OpenClaw

Quick setup
  1. Download the package from Yavira.
  2. Extract the archive and review SKILL.md first.
  3. Import or place the package into your OpenClaw setup.

Requirements

Target platform
OpenClaw
Install method
Manual import
Extraction
Extract archive
Prerequisites
OpenClaw
Primary doc
SKILL.md

Package facts

Download mode
Yavira redirect
Package format
ZIP package
Source platform
Tencent SkillHub
What's included
README.md, SKILL.md, config.example.json, scripts/librenms.sh, skill.json

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.

  1. Download the package from Yavira.
  2. Extract it into a folder your agent can access.
  3. 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. Then review README.md for any prerequisites, environment setup, or post-install checks. 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. Then review README.md for any prerequisites, environment setup, or post-install checks. Summarize what changed and any follow-up checks I should run.

Trust & source

Release facts

Source
Tencent SkillHub
Verification
Indexed source record
Version
1.0.0

Documentation

ClawHub primary doc Primary doc: SKILL.md 12 sections Open source page

LibreNMS Skill

Monitor network infrastructure via LibreNMS REST API. Read-only monitoring skill for device status, health sensors, port statistics, and alerts.

Configuration

Create ~/.openclaw/credentials/librenms/config.json: { "url": "https://librenms.example.com", "api_token": "your-api-token-here" } Or set environment variables: LIBRENMS_URL โ€” Base URL of your LibreNMS instance LIBRENMS_TOKEN โ€” API authentication token

Quick Overview

librenms summary Dashboard view showing total devices, how many are up/down, and active alert count. Use this first to get a quick status overview.

Device Management

librenms devices # List all devices with status, IP, OS, uptime librenms down # Show ONLY devices that are down (critical for alerting) librenms device <hostname> # Detailed info: hardware, serial, location, OS version

Health Monitoring

librenms health <hostname> # Temperature, CPU, memory, disk usage sensors librenms ports <hostname> # Network interfaces with traffic stats

Alerts

librenms alerts # Show active/unresolved alerts with severity and timestamps

Usage Patterns

Daily health check: librenms summary && librenms down && librenms alerts Investigate specific device: librenms device switch-core-01 librenms health switch-core-01 librenms ports switch-core-01 Quick down-device triage: librenms down | grep -v "UP"

Important Notes

All operations are read-only โ€” no device modifications possible The script accepts self-signed certificates (-sk flag for curl) Status indicators: โ— green = up, โ— red = down Uptime is formatted as human-readable (days/hours instead of seconds) Traffic stats are formatted as KB/MB/GB per second

Heartbeat Integration

Check infrastructure health periodically: # In heartbeat script if librenms down | grep -q "Devices Down"; then # Alert on down devices librenms down fi # Check for active alerts if librenms alerts | grep -q "Active Alerts"; then librenms alerts fi

Dependencies

curl โ€” API calls jq โ€” JSON parsing bc โ€” Numeric formatting (optional, for bytes conversion)

API Coverage

Wrapped endpoints: /api/v0/devices โ€” All devices /api/v0/devices/{hostname} โ€” Single device details /api/v0/devices/{hostname}/health โ€” Health sensors /api/v0/devices/{hostname}/ports โ€” Network ports /api/v0/alerts?state=1 โ€” Unresolved alerts Full API docs: https://docs.librenms.org/API/

Troubleshooting

"Config file not found" Create ~/.openclaw/credentials/librenms/config.json or set env vars. "API returned HTTP 401" Check your API token. Generate a new one in LibreNMS under Settings โ†’ API. "Failed to connect" Verify the URL is correct and the LibreNMS instance is reachable. Check firewall rules. Self-signed cert warnings The script uses -sk to ignore cert validation (common in LibreNMS setups). If you need strict validation, edit the script and remove the -k flag.

Category context

Code helpers, APIs, CLIs, browser automation, testing, and developer operations.

Source: Tencent SkillHub

Largest current source with strong distribution and engagement signals.

Package contents

Included in package
2 Docs2 Config1 Scripts
  • SKILL.md Primary doc
  • README.md Docs
  • scripts/librenms.sh Scripts
  • config.example.json Config
  • skill.json Config