Skip to content
Back to skills

Compliance Policy

ASecurity

Apply regulatory and compliance requirements (e.g. GDPR, SOC 2, PCI DSS, HIPAA, sector rules). Use when a change stores, moves, exports or deletes personal or regulated data, changes retention, adds a data processor or third party, or touches audit trails and consent.

  • 4 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added October 16, 2026
ai-agentsgorails

Security analysis

A100/100

Scanned October 16, 2026

npx -y skills add OBaruch/ai-native-sdlc-template --skill compliance-policy --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Compliance Policy?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Compliance Policy
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/obaruch-compliance-policy/badge)](https://www.skillsdirectory.com/skills/obaruch-compliance-policy)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: compliance-policy
description: Apply regulatory and compliance requirements (e.g. GDPR, SOC 2, PCI DSS, HIPAA, sector rules). Use when a change stores, moves, exports or deletes personal or regulated data, changes retention, adds a data processor or third party, or touches audit trails and consent.
---

# Compliance requirements

Owner: `<compliance officer>` · Source of truth: `<link to the compliance register>` · Version: `<x.y>`

<!-- TEMPLATE: keep only the regimes that apply to you and replace the placeholders. -->

## Applicable regimes
- `<Regime A, e.g. GDPR>` — scope: `<which products / data>`
- `<Regime B>` — scope: `<...>`

## Requirements to check
1. **Lawful basis and purpose**: every new personal-data field states its purpose and basis.
2. **Data minimisation**: collect only what the stated outcome needs.
3. **Retention**: define how long the data lives and how it is deleted (`<retention schedule>`).
4. **Residency**: data stays in `<regions>`; no new cross-border transfer without approval.
5. **Third parties**: a new processor or SaaS needs a DPA / vendor review (`<process link>`).
6. **Audit trail**: regulated actions are logged immutably with actor and timestamp.
7. **Data subject rights**: the change keeps export and deletion working for `<systems>`.

## Output
In `spec.md`, add a **Compliance** subsection listing each requirement touched and how it is met.
Anything unclear or conflicting goes under **Areas of concern**, addressed to this policy's owner.
Never mark a requirement "not applicable" without saying why.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.