skills.rest
ashley-eyekyam
ashley-eyekyamCOMMUNITY
Explore all skills by this author →
GitHub

regulatory-returns

Generate de-identified HSE regulatory returns for OSHA, RIDDOR, and EU jurisdictions.

1|Updated Jun 14, 2026
Search Tags:#de-identification#HSE compliance#safety documentation#regulatory returns#OSHA 1904#RIDDOR#statutory reporting
One-click install
npx skills add https://github.com/ashley-eyekyam/hse-leadership-skills --skill regulatory-returns
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: regulatory-returns
Source: https://github.com/ashley-eyekyam/hse-leadership-skills/tree/main/skills/regulatory-returns
Command: npx skills add https://github.com/ashley-eyekyam/hse-leadership-skills --skill regulatory-returns

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Generic AI-generated safety paperwork is often vague, relies exclusively on low-order controls like PPE, lacks clear action owners, leaks personal health data, and is frequently rejected by regulators. This skill eliminates those failures by enforcing a structured intake process to capture all required incident and jurisdiction details, applying jurisdiction-specific recordability/reportability tests, mandating strict de-identification of sensitive data, and requiring domain-expert review before any output is delivered.

Core Features & Use Cases

  • Jurisdiction-specific compliance testing: Applies the correct recordability/reportability criteria for US OSHA 29 CFR 1904 (Forms 300/300A/301), UK RIDDOR 2013, EU member-state equivalents, and routes India returns to the hse-india skill suite with mandatory state detection.
  • Mandatory de-identification: Scrubs all personal identifiers, health data, and small-cell aggregated data (fewer than 5 individuals) from circulated copies, with separate access-controlled storage for legally required named submissions and re-identification keys.
  • Structured intake guardrails: Refuses to provide a recordable/reportable yes/no answer until all required incident facts, jurisdiction, and return type details are captured, preventing guesswork and non-compliant determinations.
  • Use Case: A safety manager can use this skill to confirm if a first-aid-only workplace laceration is recordable on the OSHA 300 log, prepare a RIDDOR specified injury report with the correct 15-day filing deadline, or generate a de-identified 300A annual summary for their team without exposing employee identifiers.

Quick Start

Ask the regulatory-returns skill to determine if your recent workplace incident is recordable under OSHA 1904 or reportable under UK RIDDOR, and generate a de-identified statutory return with the correct form and exact filing deadline.

Frequently Asked Questions about regulatory-returns

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

FAQPage Schema
How do I generate a compliant RIDDOR specified injury report with the correct filing deadline?▼

To generate a compliant RIDDOR report, apply the RIDDOR 2013 reportability criteria to captured incident facts and identify the exact 15-day filing deadline. The process enforces strict de-identification and requires domain-expert review before delivering the statutory return.

What is the process for de-identifying an OSHA 300A annual summary?▼

De-identifying an OSHA 300A annual summary requires scrubbing all personal identifiers, health data, and small-cell aggregated data with fewer than 5 individuals. The process enforces this mandatory de-identification while maintaining separate access-controlled storage for legally required named submissions.

Does this regulatory returns skill support both US OSHA 1904 and EU member-state equivalents?▼

Yes, this regulatory returns skill supports US OSHA 29 CFR 1904 Forms 300/300A/301, UK RIDDOR 2013, and EU member-state equivalents. It applies jurisdiction-specific recordability and reportability tests to determine compliance and form requirements.

How do I determine if a workplace laceration is recordable on the OSHA 300 log?▼

To determine if a workplace laceration is recordable on the OSHA 300 log, the process applies OSHA 29 CFR 1904 recordability tests to captured incident facts. It refuses to provide a determination until all required incident details and jurisdiction information are captured.

What are the limitations of using AI for statutory reporting without structured intake guardrails?▼

Without structured intake guardrails, AI-generated statutory reporting is often vague, relies on low-order controls, and leaks personal health data. This skill prevents these failures by enforcing a structured intake process and requiring pre-output SME review and quality validation.

When do I need to route India state-level returns to the hse-india skill suite?▼

You need to route India state-level returns to the hse-india skill suite when generating regulatory returns for Indian jurisdictions. This skill mandates this routing with mandatory state detection to ensure accurate statutory reporting and compliance.

Related Skills

Explore More Legal & Compliance Skills→
az9713az9713

worker-classification

Assesses proposed worker engagements using jurisdiction-specific classification tests and gap analysis.

Community
Advanced
ashley-eyekyamashley-eyekyam
1

psm-program-manager

Enforce evidence-based PSM status tracking and hierarchy-of-controls remediation for OSHA 29 CFR 1910.119 programs.

Community
Advanced
ashley-eyekyamashley-eyekyam
1

legal-compliance-register

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

Community
Advanced
ashley-eyekyamashley-eyekyam
1

skill-name

Generate de-identified HSE risk assessments with hierarchy-of-controls alignment.

Community
Advanced