agentleFS
nisarthnisarth/claude-skills-store/skills/legal/compliance-check/SKILL.md

compliance-check

Skill1 starsChanged 7 months agoMITView on GitHub

Run a compliance check on a proposed action, product feature, or business initiative, surfacing applicable regulations, required approvals, and risk areas. Use when launching a feature touching personal data, entering a new market, or evaluating regulatory exposure. Trigger with "compliance check", "is this compliant", "regulatory review", or "check regulations for".

9 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 7 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Action: Check CCPA/CPRA opt-out requirements, GDPR legitimate interest, FTC standards, and contractual data use limitations.

    line 80
  2. Distinctive:

    Always identify all applicable jurisdictions before beginning the analysis.

    line 87
  3. Distinctive:

    When regulations conflict, apply the most restrictive standard unless there is a specific legal basis to deviate.

    line 88

“Common” is measured: kept by at least 6 in 10 of the 7 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Compliance Check

Evaluate a proposed action against applicable regulatory frameworks. Identify required approvals, flag risk areas, and provide a go/no-go recommendation with conditions.

Workflow

Step 1: Scope the Proposed Action

Define what, where, who, what data, and when. Identify all jurisdictions and data types involved.

Step 2: Identify Applicable Regulations

Map the action to frameworks: GDPR, CCPA/CPRA, HIPAA, COPPA, SOX, PCI-DSS, FTC Act, CAN-SPAM, TCPA, EU AI Act, and industry-specific rules (FDA, FCC, SEC). Include international data localization and transfer restrictions.

Step 3: Assess Compliance Gaps

For each regulation evaluate: current compliance status, specific gaps, remediation effort (low/medium/high), approvals needed, and whether remediation fits the timeline.

Step 4: Classify Risk

  • GREEN: Compliant or minor gaps. Proceed with standard approvals.
  • YELLOW: Material gaps requiring remediation before launch. Proceed with conditions.
  • RED: Significant regulatory exposure. Do not proceed without legal counsel review.

Output Format

## Compliance Check Report
**Subject**: [Action] | **Date**: [YYYY-MM-DD]
**Overall Status**: [GREEN / YELLOW / RED]

### Applicable Regulations
| Regulation | Domain | Jurisdiction | Relevance | Status |
|-----------|--------|-------------|-----------|--------|
| GDPR Art. 6 | Privacy | EU | HIGH | YELLOW |

### Gap Analysis
| # | Gap | Regulation | Severity | Remediation |
|---|-----|-----------|----------|-------------|
| 1 | No DPIA completed | GDPR | HIGH | Complete DPIA |

### Required Approvals
- [ ] [Approval type] -- Approver: [Name] -- By: [Date]

### Recommendation
**[PROCEED / PROCEED WITH CONDITIONS / DO NOT PROCEED]**
Conditions: [List any required conditions]

Examples

User: "We want to add AI-powered chat to our customer portal" Action: Identify applicable AI regulations (EU AI Act, state AI laws), data privacy requirements, consumer protection obligations, and accessibility requirements.

User: "Can we use customer purchase data for targeted advertising?" Action: Check CCPA/CPRA opt-out requirements, GDPR legitimate interest, FTC standards, and contractual data use limitations.

User: "We're expanding our SaaS product to Germany" Action: Assess GDPR compliance including data transfers, ePrivacy, BDSG specifics, Impressum, and VAT obligations.

Best Practices

  • Always identify all applicable jurisdictions before beginning the analysis.
  • When regulations conflict, apply the most restrictive standard unless there is a specific legal basis to deviate.
  • Distinguish between hard legal requirements and industry best practices.
  • Include the specific statutory section when citing a regulation.
  • Flag regulations with upcoming effective dates that could change the analysis.
  • Re-run the check whenever the scope materially changes.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.