idrac
Monitor and manage Dell PowerEdge servers via iDRAC Redfish API (iDRAC 8/9). Use when asked to: - Check server hardware status, health, or temperatures - Query CPU, memory, storage/RAID details - Monitor system sensors (fans, voltage, thermal) - Perform power operations (status, on, off, graceful shutdown, force restart) - Check BIOS/firmware versions or system inventory - View system event logs (SEL) or lifecycle controller logs - Get hardware inventory or serial numbers Requires: curl, jq. Optional: 1Password CLI (op) for credential hydration. Writes: ~/.config/idrac-skill/config (user-created), ~/.idrac-credentials (cached credentials, mode 600). Network: connects to user-configured iDRAC IP only (HTTPS, TLS verification disabled for self-signed certs). Helper script: scripts/idrac.sh (relative to this skill) Configuration: ~/.config/idrac-skill/config
Why use this skill?
Monitor and manage Dell PowerEdge hardware using the OpenClaw iDRAC skill. Perform health checks, view system logs, and manage power via the Redfish API.
Install via CLI (Recommended)
clawhub install openclaw/skills/skills/eddygk/idracWhat This Skill Does
The iDRAC skill provides a bridge between OpenClaw and Dell PowerEdge server hardware via the Redfish API. It allows administrators to monitor and manage server infrastructure without needing to log into the web interface manually. The skill enables real-time health checks, comprehensive hardware reporting, and power management operations. It is designed to work seamlessly with both iDRAC 8 and iDRAC 9, covering a wide range of hardware from 13th-gen PowerEdge servers to the latest models. By utilizing standard HTTP methods and the Redfish RESTful API, it provides a structured, automated way to track system events, thermal data, and inventory details directly through the agent interface.
Installation
To install this skill, run clawhub install openclaw/skills/skills/eddygk/idrac. Once installed, you must configure your local connection by creating the configuration directory and file at ~/.config/idrac-skill/config. In this file, define your IDRAC_IP and choose your preferred CREDS_SOURCE (1password, file, or environment variables). If choosing file, you must manually create ~/.idrac-credentials containing the username and password in user:pass format and ensure strict security with chmod 600. This ensures that your sensitive credentials remain protected while allowing the helper script to authenticate securely against your infrastructure.
Use Cases
- Proactive Monitoring: Regularly poll thermal, fan, and power status to prevent overheating or hardware failure.
- Inventory Management: Quickly retrieve serial numbers, firmware versions, and BIOS levels across a fleet of servers for compliance audits.
- Remote Power Control: Perform graceful shutdowns, power-on commands, or hardware restarts when a server becomes unresponsive.
- Incident Response: Fetch the latest entries from the System Event Log (SEL) when troubleshooting unexpected power cycles or hardware alerts.
Example Prompts
- "OpenClaw, check the health of the Dell server and tell me if any fans are reporting errors."
- "Get the current power state of the server and let me know if it needs a hard reset."
- "List all hardware components and their serial numbers for my R730 server."
Tips & Limitations
- Safety First: Destructive operations like 'power off' or 'restart' are inherently dangerous; the agent is designed to request manual confirmation before executing these commands.
- Security: The skill disables TLS verification (
-k) because most iDRAC deployments use self-signed certificates. Use this only in secured, isolated management networks. - Dependency: Ensure
curlandjqare installed on your host, as they are mandatory for parsing the Redfish JSON responses. - Performance: While reads are fast, avoid flooding the iDRAC API with high-frequency polling requests to prevent saturation of the management controller's resources.
Metadata
Not sure this is the right skill?
Describe what you want to build — we'll match you to the best skill from 16,000+ options.
Find the right skillPaste this into your clawhub.json to enable this plugin.
{
"plugins": {
"official-eddygk-idrac": {
"enabled": true,
"auto_update": true
}
}
}Tags(AI)
Flags: network-access, file-write, file-read, external-api
Related Skills
proxmox-ops
Ops-focused Proxmox VE management via REST API — monitor, control, provision, and troubleshoot VMs and LXC containers with battle-tested operational patterns. Use when asked to: - List, start, stop, restart VMs or LXC containers - Check node status, cluster health, or resource usage - Create, clone, or delete VMs and containers - Manage snapshots, backups, storage, or templates - Resize disks (API + in-guest filesystem steps) - Query guest agent for IP addresses - View tasks or system event logs Includes helper script (pve.sh) with auto node discovery from VMID, operational safety gates (read-only vs reversible vs destructive), vmstate snapshot warnings, post-resize guest filesystem steps, and a separate provisioning reference. Requires: curl, jq. Credentials: PROXMOX_HOST, PROXMOX_TOKEN_ID, PROXMOX_TOKEN_SECRET — set as env vars or stored in ~/.proxmox-credentials (sourced at runtime, user-created, mode 600). Writes: ~/.proxmox-credentials (user-created, API token, mode 600). Network: connects to user-configured Proxmox host only (HTTPS, TLS verification disabled for self-signed certs). Helper script: scripts/pve.sh (relative to this skill) Configuration: ~/.proxmox-credentials
skill-vetting
Vet ClawHub skills for security and utility before installation. Use when considering installing a ClawHub skill, evaluating third-party code, or assessing whether a skill adds value over existing tools.