Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Monitor and manage Dell PowerEdge servers via iDRAC Redfish API (iDRAC 8/9). Use when asked to: - Check server hardware status, health, or temperatures - Que...
Monitor and manage Dell PowerEdge servers via iDRAC Redfish API (iDRAC 8/9). Use when asked to: - Check server hardware status, health, or temperatures - Que...
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
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.
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.
Monitor and manage Dell PowerEdge servers via iDRAC Redfish API.
Create a config file at ~/.config/idrac-skill/config: mkdir -p ~/.config/idrac-skill cat > ~/.config/idrac-skill/config <<'EOF' # iDRAC connection settings IDRAC_IP="<your-idrac-ip>" # Credential source: "1password" | "file" | "env" CREDS_SOURCE="file" # For CREDS_SOURCE="1password": # OP_ITEM="<1password-item-name>" # # For CREDS_SOURCE="file": # Create ~/.idrac-credentials with contents: username:password # chmod 600 ~/.idrac-credentials # # For CREDS_SOURCE="env": # Export IDRAC_USER and IDRAC_PASS EOF
The helper script supports three credential sources: SourceConfigHow It Works1passwordOP_ITEM="item-name"Pulls username:password via op CLI, caches to ~/.idrac-credentialsfile(default)Reads ~/.idrac-credentials (format: user:pass, mode 600)envβUses $IDRAC_USER and $IDRAC_PASS environment variables
Location: scripts/idrac.sh (relative to this skill directory) idrac.sh test # Test connectivity and authentication idrac.sh status # System summary (model, power, CPU, memory) idrac.sh health # Health checks (temps, fans, power) idrac.sh power # Current power state idrac.sh inventory # Full hardware inventory idrac.sh logs # Recent system event log entries (last 10) idrac.sh thermal # Detailed temperature and fan status idrac.sh storage # RAID/disk status idrac.sh reset-types # Available power reset types
Load config from ~/.config/idrac-skill/config Hydrate credentials (JIT pattern) if needed Determine operation type: Read-only (status, health, logs, inventory) β Execute directly Destructive (power off, restart, BIOS changes) β Confirm with user first Query Redfish API via curl + Basic Auth (or session token for batch ops) Parse JSON with jq Surface findings to user in natural language Never expose credentials in responses
For raw Redfish API endpoints (system info, thermal, storage, network, logs, power ops, BIOS, firmware, session auth, Dell OEM attributes): β See references/endpoints.md
Never log or display credentials β use --silent and pipe to jq Credential file must be mode 600 (chmod 600 ~/.idrac-credentials) TLS verification disabled (-k) β iDRAC uses self-signed certs (acceptable for private networks) Power operations are destructive β confirm with user before executing shutdown/restart
Works with Dell iDRAC 8 (Redfish 1.0β1.4) and iDRAC 9 (Redfish 1.6+). Covers PowerEdge 13th gen (R630/R730) through current gen. See endpoints reference for version-specific notes. Note: iDRAC 8 API responses can take 5β10s per call. The test command makes 4 sequential calls (~30β40s total). Set exec timeouts accordingly. iDRAC 9 is significantly faster.
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Largest current source with strong distribution and engagement signals.