CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

auditing-uefi-firmware-with-chipsec

Use Intel CHIPSEC to assess platform firmware configuration, SPI flash write protection, BIOS lock, SMM/SMRR, and Secure Boot variable state, dump SPI flash, and triage UEFI variables for firmware-level threats.

Quality

77%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/auditing-uefi-firmware-with-chipsec/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

71%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is highly actionable with a clear, well-sequenced workflow and strong safety guards around destructive operations. It is held back by some redundant explanatory/contextual padding and by failing to route to the existing bundle files, inlining reference material instead.

Suggestions

Replace the inline 'Core Module Reference' table (and the command-flag detail it duplicates) with a one-line pointer to references/api-reference.md, and add a pointer to scripts/agent.py for automated baselining and to references/standards.md for the MITRE/NIST mappings.

Trim the Overview's threat-context paragraph ('Firmware implants persist across OS reinstall... invisible to most EDR') down to the essential T1542.001 framing, since Claude already knows this background.

Move the inline validation checklist into the workflow at the points where each result is interpreted, so checkpoints are inline rather than only at the end.

DimensionReasoningScore

Conciseness

Mostly efficient with abundant executable commands, but the Overview spends paragraphs explaining threat context Claude largely knows ('Firmware implants persist across OS reinstall and disk replacement and are invisible to most EDR') and the 'Core Module Reference' table duplicates detail already embedded in the workflow steps.

3 / 5

Actionability

Provides copy-paste-ready, fully executable commands for every common case — e.g. 'sudo chipsec_main -m common.bios_wp', 'sudo chipsec_util spi dump rom.bin', 'sudo chipsec_util uefi var-list' — with flags and expected outputs clearly shown.

5 / 5

Workflow Clarity

An 8-step numbered workflow is clearly sequenced with interpretation guidance and a closing Validation Criteria checklist, plus explicit guards on the destructive write/modify action ('test hardware ONLY'); validation is present but lives in an end-of-process checklist rather than inline checkpoints, leaving a minor gap.

4 / 5

Progressive Disclosure

The body is well sectioned, but the three bundle files (references/api-reference.md, references/standards.md, scripts/agent.py) are never referenced from the body, and an inline 'Core Module Reference' table plus command details duplicate what api-reference.md already holds — content that belongs in the references is inlined and the references are not signaled.

3 / 5

Total

15

/

20

Passed

Description

75%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is specific, tool-scoped, and highly distinct, clearly communicating what the skill does. Its main weakness is the absence of an explicit 'Use when...' trigger clause, which caps completeness.

Suggestions

Append an explicit trigger clause, e.g. 'Use when auditing platform firmware security, verifying BIOS/SPI write protection, or hunting UEFI firmware implants on x86 systems you own or are authorized to assess.'

Add a few natural synonyms users might say ('firmware assessment', 'BIOS write protection', 'SPI flash dump') to broaden trigger coverage.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'assess platform firmware configuration, SPI flash write protection, BIOS lock, SMM/SMRR, and Secure Boot variable state, dump SPI flash, and triage UEFI variables' — giving comprehensive coverage of the skill's capabilities.

5 / 5

Completeness

The 'what' is clear and detailed, but there is no 'Use when...' clause or equivalent explicit trigger guidance — only the weakly implied purpose 'for firmware-level threats' — so completeness is capped at 3 per the rubric guideline.

3 / 5

Trigger Term Quality

Includes strong domain keywords a practitioner would say ('CHIPSEC', 'SPI flash', 'BIOS', 'SMM/SMRR', 'Secure Boot', 'UEFI variables'), but misses common synonyms/variants and lacks file-extension-style triggers, so it is not fully comprehensive.

4 / 5

Distinctiveness Conflict Risk

Names a specific tool and a narrow niche ('Use Intel CHIPSEC to assess platform firmware...'), giving it distinct triggers with minimal overlap risk against other skills.

5 / 5

Total

17

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

mukul975/Anthropic-Cybersecurity-Skills

Path

skills/auditing-uefi-firmware-with-chipsec/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.