sota-privacy-compliance SKILL.md skillA
sota-privacy-compliance 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-privacy-compliance@git:20261028.da12e08Pins git:20261028.da12e08 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-privacy-compliance/SKILL.md- Versions recorded
- 6
- Latest version
- git:20261028.da12e08, committed Oct 28, 2026
- First version recorded
- Jun 17, 2026
- Size
- 10,878 bytes
- Repository stars
- 26
- License
- CC-BY-4.0
State-of-the-art privacy and compliance engineering guidance for building privacy-respecting systems and auditing existing code for privacy/compliance gaps. Use when work involves privacy, GDPR, PII, personal data, consent, data retention, deletion, DSAR (data subject access requests), SOC 2, ISO 27001, HIPAA, PCI DSS, compliance evidence, data residency/sovereignty, data classification, anonymization/pseudonymization, breach notification, or EU AI Act obligations — whether designing new data…
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 Privacy & Compliance Engineering ## Purpose Engineering-facing privacy and compliance architecture: how to design, build, and audit systems so that data protection is a property of the code and infrastructure, not a binder of policy documents. Compliance that lives in schemas, TTLs, IAM policies, and CI checks survives staff turnover and audit scrutiny; compliance that lives in wiki pages does not. > **This is engineering guidance, not legal advice.** Regulations change, vary by > jurisdiction, and turn on facts about your business that code review cannot see. > Regulatory facts below were verified against primary sources as of June 2026 — > re-verify deadlines and statuses before relying on them, and route legal > interpretation (lawful basis selection, contract terms, breach reportability > decisions) to qualified counsel or your DPO. This skill tells you how to build > the machinery those decisions require. **Related skills — reference, don't duplicate:** - [`sota-databases` rules/06](../sota-databases/rules/06-security-and-compliance.md) — DB-level PII mechanics (column encryption, row-level security, GDPR-friendly schema design) …
Read the whole file at its exact version.
How to install
mdr add martinholovsky/sota-skills/sota-privacy-compliance@sha256:3abc6925a837ec1bThe line at the top of this page pins the label git:20261028.da12e08, 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_yhhjdzwwn6p6j2eb)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 6 versions of this file, between Jun 17, 2026 and Oct 28, 2026, about one every 27 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261028.da12e08 latest | 2026-10-28 | da12e08 | 10,878 B | A | view · diff |
| git:20261026.808c340 | 2026-10-26 | 808c340 | 10,866 B | A | view · diff |
| git:20261024.8dd2b0a | 2026-10-24 | 8dd2b0a | 10,816 B | A | view · diff |
| git:20261012.ae1b29b | 2026-10-12 | ae1b29b | 10,575 B | A | view · diff |
| git:20260925.2b21d93 | 2026-09-25 | 2b21d93 | 9,915 B | A | view · diff |
| git:20260617.c5d2c7b | 2026-06-17 | c5d2c7b | 9,803 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 (10878 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 · 26 stars · license CC-BY-4.0 · pushed 2026-11-05 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_yhhjdzwwn6p6j2eb GET https://markdownregistry.com/api/v1/resolve?ref=martinholovsky/sota-skills/sota-privacy-compliance GET https://markdownregistry.com/api/v1/blob/3abc6925a837ec1b447a51644f33ac83ee07232da4e5e41d070973433d875260
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.