agentsclimarketplace

Regulatory landscape

Skill bromso/metapowers/plugins/compliance/skills/regulatory-landscape

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 regulatory-landscape

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

Map all applicable regulations based on jurisdiction, industry, data types, and customer requirements

SKILL.md

2.6 KB, as published. Nobody here has run it

Regulatory Landscape

Map the full regulatory landscape for "$ARGUMENTS". Identify every applicable regulation based on where the business operates, what data it processes, what industries its customers serve, and what certifications those customers require.

Prerequisites

None — this is a Phase 0 (Scope) skill.

Process

  1. Read context files:

    • Read plugins/compliance/shared/grc-lifecycle-guide.md for GRC methodology reference

  2. Jurisdiction mapping:

    • Identify all jurisdictions where the business operates (headquarters, offices, data centers, customers)
    • Map each jurisdiction to its regulatory requirements (EU, US federal, US state, UK, APAC, etc.)
    • Note cross-border data transfer implications

  3. Data classification:

    • Identify data types processed (PII, PHI, PCI, financial data, children's data, biometric data, etc.)
    • Map each data type to regulations that govern it
    • Note data residency and sovereignty requirements

  4. Industry and customer analysis:

    • Identify industries the business serves (healthcare, finance, government, education, etc.)
    • Map industry-specific regulations (HIPAA, PCI DSS, FedRAMP, FERPA, etc.)
    • Document certifications customers require or request in sales cycles

  5. Regulation inventory:

    • Create a comprehensive regulation inventory table with columns: regulation name, jurisdiction, data types covered, industry applicability, mandatory vs. customer-driven, enforcement status
    • Map each regulation to applicability criteria specific to "$ARGUMENTS"
    • Flag regulations with upcoming enforcement dates or recent changes

  6. Write the artifact to .metapowers/compliance/$ARGUMENTS/00-scope.md with sections:

    • Jurisdiction Map — where the business operates and applicable jurisdictions
    • Data Type Inventory — data types processed and governing regulations
    • Industry Requirements — sector-specific regulations and customer demands
    • Regulation Inventory Table — full list of applicable regulations with applicability criteria
    • Cross-Border Considerations — data transfer and sovereignty requirements

Output

The regulatory landscape analysis written to .metapowers/compliance/$ARGUMENTS/00-scope.md. Present a summary to the user highlighting:

  • Total number of applicable regulations identified
  • Top regulations by business impact
  • Any surprising applicability findings
  • Recommended next step: run /compliance:compliance-priorities $ARGUMENTS

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.