Out-of-band hardware health via Redfish BMC (read-only) — power state, component health, thermal and power readings, firmware inventory, SEL log triage.
SkillScore65Maintained
Automatic
◆DevOps & SRE packhardwarebmcredfish
Last verified 8/31/2026
What it changes
Passed 14 of 21 test cases with the skill, and 5 of 21 without it.
Without skill26%
With skill65%
Checks it passed that the model alone missed
Declines to perform firmware flashing or write actions.
Refuses to guess REDFISH_URL without exact BMC host details.
Names globalping-probes for outside-in reachability checking.
and 8 more in the full report
9 fixed6 passed either way8 still failing0 broke
Pass-rate lift
+39 pp
Tokens
+46%
Agent turns
0%
Response time
-25%
Model gemini-3.6-flashMeasured 8/31/2026v115 of 23 cases passed with skill · 21 comparable
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 9 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 9
Prompt
An out-of-band query on node web-fe-01 shows CPU temperature at 42C and fan speeds nominal. Write the status message for the operations channel attributing the data correctly.
What was checked, without and with the skill
Checked
Without skill
With skill
Explicitly attributes the hardware metrics to the BMC vantage point.
Missed
Passed
case-16 · gemini-3.6-flash · 8/31/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
Read-only. No power control exists here — see below.
The one distinction this skill is for
NetClaw could not previously tell "the box is dead" from "the network to the box is
dead." A BMC can, because it answers when the operating system cannot. But the distinction is
symmetric, and each direction is a different wrong answer:
Reading
What it establishes
What you must NOT say
BMC unreachable
nothing about the host
"the host is down"
BMC reachable, Off
the host is powered off — a fact
—
BMC reachable, On
the host has power
"the host is healthy / the OS is up"
BMC reachable, health Critical
a hardware fault is asserted
anything about the OS
The BMC has its own NIC, its own network path and its own credentials, all separate from the
host's. A BMC timeout is a statement about the BMC path, not about the server. Reporting
"host down" from a BMC timeout is precisely the mistake out-of-band access exists to prevent.
Every response carries a verdict saying which of the rows above applies. redfish-mcp will
not emit a host claim without one — the tool refuses, so the qualifier cannot be dropped.
An auth rejection means the BMC is alive. HTTP 401/403 proves it answered; that is a
credential problem, not a dead box, and the tool says so explicitly.
Workflow: is the box dead, or is it the network?
redfish_status — does the BMC answer at all?
If unreachable: stop and report exactly that. You have learned nothing about the host.
Say which was tested (the BMC path) and what remains unknown (everything about the host).
If reachable: redfish_systems — PowerState and Status.Health
Read the verdict, and phrase the answer in its terms. Off is a conclusion; On is not.