sota-confidential-computing SKILL.md skillA
sota-confidential-computing from martinholovsky/sota-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add martinholovsky/sota-skills/sota-confidential-computing@git:20261012.ae1b29bPins git:20261012.ae1b29b in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- martinholovsky/sota-skills
- Path
skills/sota-confidential-computing/SKILL.md- Versions recorded
- 2
- Latest version
- git:20261012.ae1b29b, committed Oct 12, 2026
- First version recorded
- Jul 9, 2026
- Size
- 10,002 bytes
- Repository stars
- 23
- License
- CC-BY-4.0
State-of-the-art confidential computing and cryptographic PETs (2026) for BUILDING and AUDITING systems that protect workloads and data in use from the infrastructure they run on — the inverse of sandboxing. Covers TEE selection (AMD SEV-SNP, Intel TDX, ARM CCA realms, SGX enclaves, AWS Nitro Enclaves, NVIDIA confidential GPUs), memory encryption vs attested isolation (TME/TME-MK/MKTME), remote attestation (RATS RFC 9334, evidence appraisal, attest-then-release, RA-TLS, TCB recovery)…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# SOTA Confidential Computing & PETs ## Purpose Engineer and audit systems where the *infrastructure itself* is the adversary: the cloud operator, the hypervisor, the node admin, a co-tenant, or anyone with physical access to memory. Two tool families, one skill: hardware TEEs with remote attestation (trust silicon + verify it), and cryptographic PETs that compute on encrypted data (trust only math, pay orders of magnitude for it). The boundary with [`sota-sandboxing`](../sota-sandboxing/SKILL.md) is direction: sandboxing protects the host from the workload; this skill protects the workload from the host. Both can apply to the same system. Two modes. Pick one explicitly at the start of the task. --- ## BUILD mode Use when designing or implementing confidentiality-in-use for new or changed systems. 1. **Name the adversary first** ([`rules/01`](rules/01-threat-model-and-selection.md) §2, §7): operator, hypervisor, co-tenant, physical, or "the other party in a joint computation". If no adversary survives scrutiny, stop — TLS + at-rest encryption + KMS custody ([`sota-secrets-management`](../sota-secrets-management/SKILL.md)) already covers you. …
Read the whole file at its exact version.
How to install
mdr add martinholovsky/sota-skills/sota-confidential-computing@sha256:7f33703532c4dc13The line at the top of this page pins the label git:20261012.ae1b29b, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_iapekmyhtvsf5thl)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, between Jul 9, 2026 and Oct 12, 2026, about one every 95 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261012.ae1b29b latest | 2026-10-12 | ae1b29b | 10,002 B | A | view · diff |
| git:20260709.795db22 | 2026-07-09 | 795db22 | 9,293 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (10002 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
martinholovsky/sota-skills · 23 stars · license CC-BY-4.0 · pushed 2026-10-21 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_iapekmyhtvsf5thl GET https://markdownregistry.com/api/v1/resolve?ref=martinholovsky/sota-skills/sota-confidential-computing GET https://markdownregistry.com/api/v1/blob/7f33703532c4dc13e3661a4f02c19371bb52eb6a0806a2379ceb7e3e2485f260
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.