Skip to content
Get packs

Auditing UEFI Firmware with CHIPSEC

Check whether a computer's low-level firmware locks and Secure Boot protections are actually enabled

Source Download skill
Repository
mukul975/Anthropic-Cybersecurity-Skills
Stars
35,430
Licence
Apache-2.0
Files
4 files

What it does

This skill teaches the agent to run Intel's open-source CHIPSEC framework, which inspects the firmware layer below the operating system (BIOS/UEFI on the SPI flash chip) to see whether protections against firmware tampering are switched on. The agent can run the test suite, interpret PASS/FAIL results, dump the firmware image for offline comparison, and list UEFI variables. A bundled helper script wraps the CHIPSEC command-line tools to run a baseline and parse the output.

Great for

  • Security engineers doing a firmware-posture baseline on new laptops or server images
  • Forensic analysts who need to dump and compare SPI flash against a known-good image
  • Students learning how UEFI write protection and Secure Boot variable protection are verified

Skip it if

  • Machines you do not own or lack written authorization to test: CHIPSEC loads a kernel driver and reads low-level hardware, and the skill itself warns against unauthorized use
  • Production systems when write or modify modules are used: the skill notes these can brick a machine
  • Non-x86 platforms or anyone without root/Administrator access, since the tooling needs both to load its driver

Try asking

  • “Run a full CHIPSEC platform-security baseline on this test laptop and summarize any FAILED checks”
  • “Check whether BIOS write protection and the SPI flash descriptor lock are enabled on this server”
  • “Dump the SPI flash to rom.bin and decode it so I can compare it with the vendor's firmware image”
  • “List the Secure Boot UEFI variables and flag anything unexpected”
Step-by-step guide: how to use Auditing UEFI Firmware with CHIPSECInstall, first run, examples, tips and FAQs

Install in 3 steps

  1. 1

    Download the skill

    The ZIP contains the 4 original files, the Apache-2.0 licence and an attribution note.

    auditing-uefi-firmware-with-chipsec.zip
  2. 2

    Add it to your agent

    Claude Code (all projects)

    mkdir -p ~/.claude/skills && unzip auditing-uefi-firmware-with-chipsec.zip -d ~/.claude/skills/

    Claude Code / Agent SDK (this project only)

    mkdir -p .claude/skills && unzip auditing-uefi-firmware-with-chipsec.zip -d .claude/skills/

    Claude apps (web/desktop): Settings → Capabilities → Skills → Upload skill, and choose the ZIP.

  3. 3

    Ask for the task

    No special command needed — the agent reads the skill's description and loads it when your request matches. Try one of the prompts above.

Get better results

  • Use the read-only checks first and only use the -a modify or write-capable options on dedicated test hardware, never production machines
  • If Secure Boot blocks the CHIPSEC driver, ask the agent to use the limited no-driver checks instead of forcing the driver load
  • Save results as JSON or XML (for example with -j and -x) so you can diff baselines over time

What's inside

  • references/api-reference.md
  • references/standards.md
  • scripts/agent.py
  • SKILL.md

Redistributed unmodified from mukul975/Anthropic-Cybersecurity-Skills under the Apache-2.0 licence. The assessment was drafted with AI from the skill's files on 2026-10-29. Skills can instruct your agent to run code — read SKILL.md and any scripts before installing.