compliance-evidence

Use when the user needs compliance and privacy evidence.

compliance-evidence

Use source-first, evidence-led execution. Separate facts, assumptions, recommendations, unknowns, blockers, not-run, failed, and validated. Do not claim validation or mutate external systems unless explicitly authorized. Produce named artifacts and cite source paths when possible.

Added: September 23, 2026 · Last updated: September 24, 2026

Files (1)

Jurisdiction
General
Practice area
Data protection
License
MIT
Author
cembasaranoglu
Source
general/data-protection/skills/compliance-evidence-cembasaranoglu

Test compliance-evidence

Ask a legal question — get an answer generated live from this skill’s instructions.

Sign in to test this skill.