sev-attestation

Perform AMD SEV-SNP remote attestation to cryptographically verify VM identity and integrity. Use when proving a VM is running in a genuine AMD SEV-SNP confidential computing environment, verifying VM integrity before trusting it with secrets, checking SEV-SNP availability, generating attestation reports, validating AMD certificate chains (ARK/ASK/VCEK), or debugging attestation failures.

This skill appears to do exactly what it says: local SEV‑SNP attestation using /dev/sev-guest, snpguest or OpenSSL, and AMD's KDS. Before running it: 1) review the scripts (they are included) and confirm you are comfortable running them as root; 2) expect the fetch step to send chip identifiers and TCB fields to AMD's KDS (this is required to obtain the VCEK and may reveal hardware identifiers); 3) installing snpguest via cargo will pull code from crates.io—inspect that package if you have supply-chain concerns; 4) run in a trusted environment (attestation involves hardware identifiers and privileged device access) and, if using cloud VMs, check provider policies. If you want stricter assurance, run the manual OpenSSL verification path included so you can audit each step and avoid installing extra tooling.

Type: OpenClaw Skill Name: sev-attestation Version: 1.0.2 The skill bundle is designed to perform AMD SEV-SNP remote attestation, which inherently requires privileged access to `/dev/sev-guest` and network communication with AMD's Key Distribution Service (`kdsintf.amd.com`). All scripts and documentation (including `SKILL.md` and `README.md`) clearly state these requirements and their purpose. There is no evidence of data exfiltration, malicious execution, persistence mechanisms, obfuscation to hide intent, or prompt injection attempts against the agent. The use of `sudo` and interaction with privileged kernel devices are necessary for the stated functionality and are transparently documented in `SKILL.md` and `references/error-codes.md`.