agentsclimarketplace

Compliance review

Skill bromso/metapowers/plugins/legal/skills/compliance-review

A Claude Code plugin that adds an agentic skills framework, with MCP's and a meta prompting processes. Inspired by "Superpowers" & "Figma Console MCP", but not just for development or design; but for all aspect within the digital production cycle.

Install
npx -y skills add bromso/metapowers --skill compliance-review

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Review document for regulatory compliance (GDPR, CCPA, SOC2, etc.)

SKILL.md

5.1 KB, as published. Nobody here has run it

Compliance Review

Review the document for "$ARGUMENTS" against applicable regulatory frameworks. Check compliance with GDPR, CCPA, SOC2, and other relevant regulations, scoring compliance level and identifying specific gaps.

Note: AI-generated legal content does not constitute legal advice. Consult a qualified attorney.

Prerequisites

Check that .metapowers/legal/$ARGUMENTS/00-assess.md exists. If it does not exist, stop and tell the user:

"Run an Assess skill first (e.g. /legal:risk-assessment $ARGUMENTS) to generate the prerequisite assessment artifact."

If the user passes --skip-checks, bypass this check and log the skip to .metapowers/legal/$ARGUMENTS/skip-log.md with a timestamp and the reason "Prerequisite check skipped for compliance-review".

Process

  1. Read inputs:

    • Read .metapowers/legal/$ARGUMENTS/00-assess.md for risk and jurisdiction context
    • Read plugins/legal/shared/compliance-checklist.md for reference requirements
    • Read the document from the source provided by the user

  2. Determine applicable regulations:

    • Based on jurisdiction, industry, and data types identified in the assessment
    • Prioritize regulations by relevance and enforcement risk

  3. Check GDPR compliance (if applicable):

    • Lawful basis — is a lawful basis for processing identified (consent, legitimate interest, contract, etc.)?
    • Data processing provisions — are controller/processor roles defined with adequate DPA terms?
    • Data subject rights — are rights addressed (access, rectification, erasure, portability, objection)?
    • International transfers — are transfer mechanisms in place (SCCs, adequacy decisions, BCRs)?
    • Breach notification — are notification obligations defined (72-hour timeline, authority and data subject notification)?
    • Data Protection Impact Assessment — is a DPIA referenced or required for high-risk processing?
    • Records of processing — are record-keeping obligations addressed?

  4. Check CCPA/CPRA compliance (if applicable):

    • Notice at collection — are categories of personal information and purposes disclosed?
    • Opt-out rights — is the right to opt out of sale/sharing of personal information addressed?
    • Deletion rights — are consumer deletion request procedures defined?
    • Non-discrimination — is there a commitment not to discriminate against consumers exercising rights?
    • Service provider obligations — are contractual restrictions on use of personal information included?
    • Sensitive personal information — are additional protections for sensitive categories addressed?

  5. Check SOC2 compliance (if applicable):

    • Security controls — are security measures documented (encryption, access controls, monitoring)?
    • Availability commitments — are uptime and recovery commitments defined?
    • Incident response — is an incident response plan referenced or required?
    • Change management — are change control procedures addressed?
    • Vendor management — are sub-processor or subcontractor controls defined?

  6. Check accessibility compliance (if applicable):

    • WCAG 2.1 AA compliance commitments
    • Accessibility testing obligations
    • Remediation timelines for accessibility issues

  7. Score compliance level per regulation:

    • Compliant — all material requirements addressed with adequate provisions
    • Partially Compliant — some requirements addressed but with notable gaps
    • Non-Compliant — critical requirements missing or inadequately addressed

  8. Identify specific gaps and suggest compliant alternatives:

    • For each gap, reference the specific regulatory requirement
    • Provide draft language or provisions that would close the gap
    • Prioritize gaps by enforcement risk and potential penalty exposure

  9. Write the artifact to .metapowers/legal/$ARGUMENTS/02-review.md with frontmatter:

    ---
description: Compliance review for $ARGUMENTS
---

    Include sections:

    • Applicable Regulations — list of regulations checked and rationale for inclusion
    • GDPR Assessment — item-by-item compliance check (if applicable)
    • CCPA/CPRA Assessment — item-by-item compliance check (if applicable)
    • SOC2 Assessment — item-by-item compliance check (if applicable)
    • Accessibility Assessment — item-by-item compliance check (if applicable)
    • Compliance Scorecard — Compliant/Partially Compliant/Non-Compliant per regulation
    • Gap Analysis — specific gaps with regulatory reference and risk level
    • Remediation Recommendations — suggested language or provisions per gap

Output

The compliance review written to .metapowers/legal/$ARGUMENTS/02-review.md. Present a summary to the user highlighting:

  • Compliance scorecard across all applicable regulations
  • Critical gaps (Non-Compliant items) requiring immediate attention
  • Number of gaps per regulation and overall compliance posture
  • Top 3 remediation priorities

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.