agentsclimarketplace

Jurisdiction analysis

Skill bromso/metapowers/plugins/legal/skills/jurisdiction-analysis

Analyze legal requirements across jurisdictions (multi-country/state)From its SKILL.md

Install
npx -y skills add bromso/metapowers --skill jurisdiction-analysis

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.

SKILL.md

2.9 KB, 565 tokens by cl100k_base, as published. Nobody here has run it

Jurisdiction Analysis

Analyze legal requirements across all relevant jurisdictions for "$ARGUMENTS". Compare obligations, identify conflicts, and recommend a baseline standard.

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

Prerequisites

None — this is a Phase 0 Assess skill.

Process

  1. Identify all relevant jurisdictions:

    • Where the business has offices or physical presence
    • Where customers or users are located
    • Where data is stored or processed
    • Where employees or contractors are based
    • Where partners or vendors operate
  2. For each jurisdiction, document:

    • Key legal requirements — primary laws governing business operations
    • Registration and filing obligations — business registration, tax filings, annual reports
    • Data protection laws — privacy regulations, data localization requirements, breach notification rules
    • Employment laws — hiring requirements, worker classification, benefits mandates, termination rules
    • Consumer protection laws — disclosure requirements, refund policies, advertising standards
  3. Compare requirements across jurisdictions:

    • Create a comparison matrix (jurisdiction x requirement area)
    • Identify where requirements align across jurisdictions
    • Identify where requirements diverge or conflict
  4. Identify conflicts:

    • Stricter vs. more permissive requirements for the same obligation
    • Mutually exclusive requirements (where complying with one violates another)
    • Data localization conflicts (data must stay in country A but also be accessible in country B)
    • Employment law conflicts across remote-work jurisdictions
  5. Recommend baseline standard:

    • Typically adopt the strictest jurisdiction's standard as the baseline
    • Document where jurisdiction-specific exceptions or adaptations are needed
    • Identify cost and operational implications of the recommended baseline
    • Flag areas where legal counsel must resolve genuine conflicts
  6. Write the artifact to .metapowers/legal/$ARGUMENTS/00-assess.md with heading:

    Jurisdiction Analysis

    Include sections:

    • Jurisdiction Inventory — all jurisdictions with basis for inclusion
    • Requirements by Jurisdiction — legal obligations per jurisdiction
    • Comparison Matrix — side-by-side comparison of key requirements
    • Conflicts and Tensions — where requirements diverge or conflict
    • Recommended Baseline — proposed standard with rationale
    • Jurisdiction-Specific Exceptions — where the baseline needs adaptation

Output

The jurisdiction analysis written to .metapowers/legal/$ARGUMENTS/00-assess.md. Present a summary to the user highlighting:

  • Total jurisdictions analyzed
  • Key conflicts or tensions identified
  • Recommended baseline jurisdiction and rationale

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Keep looking

Skills are one crate of 326,758. 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.