legal-compliance-register

Generate multi-jurisdiction HSE legal compliance registers with applicability confirmation and gap tracking.

1|Updated Jun 14, 2026
One-click install
npx skills add https://github.com/ashley-eyekyam/hse-leadership-skills --skill legal-compliance-register
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: legal-compliance-register
Source: https://github.com/ashley-eyekyam/hse-leadership-skills/tree/main/skills/legal-compliance-register
Command: npx skills add https://github.com/ashley-eyekyam/hse-leadership-skills --skill legal-compliance-register

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

Generic AI-generated HSE compliance paperwork is often vague, relies on weak controls like PPE-only, lacks clear ownership and review dates, and leaks sensitive personal or operational data — leading to regulator rejections and unactionable documents that fail ISO 45001 audits.

Core Features & Use Cases

  • Structured specificity intake: Forces capture of jurisdiction, named organisation/site, and activity profile before drafting, refusing to list obligations for vague or out-of-scope requests.
  • Multi-jurisdiction compliance mapping: Supports UK, US, EU, and India (with mandatory state detection) obligations, grounded in ISO 45001 clauses 6.1.3 and 9.1.2, with applicability confirmed per named activity to exclude irrelevant laws.
  • Built-in data protection: Mandatory de-identification of all sensitive identifiers, with pseudonymised role labels for compliance owners and aggregated small data cells to prevent data leaks.
  • India statutory deferral: Routes Indian obligations to the hse-india engine for state-specific form resolution, never minting unverified national form numbers.
  • Auditable output: Generates branded, compliant registers with applicability rationales, compliance evidence, gap tracking, SMART actions, and role-label owners with review dates.
  • Use case: For a manufacturing plant in Maharashtra, India, this skill produces a UK + India legal register that excludes inapplicable construction regulations, maps each obligation to compliance evidence, and flags gaps with owned, dated actions.

Quick Start

Use the legal-compliance-register skill to build a multi-jurisdiction legal compliance register for your UK manufacturing site covering general workplace and chemical handling activities, aligned to ISO 45001 6.1.3 requirements.

Frequently Asked Questions about legal-compliance-register

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

FAQPage Schema
How do I build an ISO 45001 legal register for multi-jurisdiction operations?

Building an ISO 45001 multi-jurisdiction legal register requires structured intake of your organisation, site locations, and activity profiles to generate defensible compliance registers mapping obligations across UK, US, EU, and India with mandatory applicability confirmation.

What is the best way to ensure an HSE compliance register passes ISO 45001 audits?

The best way to ensure an HSE compliance register passes ISO 45001 audits is to enforce applicability confirmation per named activity, include gap tracking with SMART actions, and assign role-label owners with review dates to eliminate generic regulator-rejectable paperwork.

Can I generate a legal compliance register for a manufacturing site in India?

Yes, you can generate a legal compliance register for an Indian manufacturing site, but the process requires mandatory state detection, such as identifying Maharashtra, and defers obligation resolution to the hse-india engine for state-specific form verification.

How does de-identification work when creating HSE legal registers?

De-identification works in HSE legal registers by applying mandatory pseudonymised role labels for compliance owners and aggregating small data cells, preventing sensitive personal or operational data leaks in the final auditable output.

Why does my generic AI-generated legal register fail regulator compliance evaluations?

Generic AI-generated legal registers fail compliance evaluations because they rely on weak PPE-only controls, lack clear ownership and review dates, and list obligations without confirming applicability to your specific named activities.

What limitations exist when mapping statutory compliance across multiple jurisdictions?

A key limitation when mapping statutory compliance is that Indian obligations are not resolved directly; the system defers to the hse-india engine for state-specific form resolution to prevent minting unverified national form numbers.