BC 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.
As a process C 54/100 · Has gaps — weak spots: result and completion, when it triggers, failures and branches
What is at stake
The skill contains fragments that, in the wrong hands, cost money or data. Below: what the installer risks and what the author should do.
The skill contains commands that delete files, rewrite disks or execute code fetched from the network. The agent may run them without asking if it believes the instructions require it.
Replace destructive commands with safe equivalents that ask for confirmation, scope them to one folder, and stop piping curl into a shell: pin a version and a checksum.
How to improve
- Address the high-severity findings: each costs 18 safety points. If one is a false positive, add the rule id to guard.allow in spec.yaml.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 4
-
high Dangerous commands
cmd-pipe-to-shellreferences/error-codes.md:135Downloads and executes remote code from an unrecognised host (pipe to shell)curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh
Medium and low: 3
-
medium Dangerous commands
cmd-privilegereferences/error-codes.md:59Privilege escalation / world-writable permissionsecho "sev-guest" | sudo tee /etc/modules-load.d/sev-guest.conf
-
medium Dangerous commands
cmd-privilegereferences/error-codes.md:110Privilege escalation / world-writable permissionssudo chmod 660 /dev/sev-guest
-
medium Dangerous commands
cmd-privilegereferences/error-codes.md:111Privilege escalation / world-writable permissionssudo chown root:sev /dev/sev-guest
Files scanned: 12. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 54/100
- 0Result and completion. Does not say what the result is
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 60Tools and files. Uses tools (web) that frontmatter does not declare
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 17 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1056 tokens
- 100Running it twice. No mutating operations
- low The response is described with custom markup (6 tags): a typed call is more reliable
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +3Description length 391: enough signal without eating the budget
- +4Structure: 10 headings
- +3Step-by-step instructions: 17 items
- +4Has examples (4 code blocks)
- +4Reference files are cited in the instructions (3 of 3)
- +3All 6 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 91.