compliance-check

Summarize applicable laws, approvals, and artifacts for pre-launch regulatory go/no-go checks.

Updated Apr 25, 2026
One-click install
npx skills add https://github.com/nmoralescyber/claude-skill-optimization --skill compliance-check-nmoralescyber
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: compliance-check
Source: https://github.com/nmoralescyber/claude-skill-optimization/tree/main/skills/legal/compliance-check
Command: npx skills add https://github.com/nmoralescyber/claude-skill-optimization --skill compliance-check-nmoralescyber

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Pre-launch regulatory go/no-go checks surface required approvals, notifications, and artifacts across jurisdictions to ensure compliant launches for proposed actions, features, or campaigns.

Core Features & Use Cases

  • Regulatory scoping by jurisdiction: identifies applicable privacy, consumer-protection, AI, cybersecurity, and industry-specific laws.
  • Internal and external approvals: catalogs required legal, privacy/DPO, security, finance, brand, and executive sign-offs with target dates.
  • Artifact and notification planning: outlines necessary DPAs, DPIAs, updated privacy disclosures, consent flows, and regulator filings.
  • Governance and risk framing: provides decision criteria, exemptions, and re-check triggers to prevent non-compliant launches.

Quick Start

Run a pre-launch compliance check for a proposed initiative in EU and Puerto Rico scope.

Frequently Asked Questions about compliance-check

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run a pre-launch regulatory go/no-go check for a new product feature?

A pre-launch regulatory go/no-go check summarizes applicable laws, required internal and external approvals, and necessary artifacts like DPAs and filings to validate compliance before launch.

What is included in a regulatory scoping assessment for privacy and AI laws?

Regulatory scoping identifies applicable privacy, consumer-protection, AI, cybersecurity, and industry-specific laws across jurisdictions to map required notifications and compliance criteria.

How do I identify which internal approvals and sign-offs are required before launch?

To identify required approvals, catalog necessary legal, privacy/DPO, security, finance, brand, and executive sign-offs alongside target dates and decision criteria for the proposed initiative.

What pre-launch compliance artifacts and notifications do I need to prepare?

Pre-launch compliance artifacts include DPAs, DPIAs, updated privacy disclosures, consent flows, and regulator filings, ensuring all required notifications and documentation are ready before launch.

Can I use this compliance check for multi-jurisdictional initiatives spanning different regions?

Yes, the compliance check maps jurisdictional scope across regions, validating regulatory requirements and required notifications for proposed actions across varying legal frameworks.

When should I trigger a re-check of my pre-launch compliance governance and risk framing?

Re-check triggers should be activated when governance risk framing identifies exemptions, updated decision criteria, or changes to regulatory requirements that affect the compliant launch status.