dgms-statutory-pack

Draft DGMS statutory forms with verified citations and de-identified miner data.

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

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 for Indian mines is often rejected by DGMS regulators due to vague obligations, incorrect form citations, leaked sensitive miner data, and missing required context. Manually drafting compliant DGMS statutory forms is time-consuming and requires specialized knowledge of regional zone requirements and the India Mines Act 1952.

Core Features & Use Cases

  • Structured Obligation Resolution: Enforces a mandatory multi-step intake to capture mine-specific context (region/zone, obligation type, event details) before drafting, refusing to proceed on vague requests to avoid incorrect filings.
  • Verified Form Drafting: Drafts only the five verified DGMS statutory forms (24-hour accident/dangerous occurrence notice, Form J accident register, Form B employee register, annual return, statutory Manager appointment letters) and marks all unverified form IDs as [GAP] to never invent incorrect form numbers.
  • Mandatory Data Protection: Runs a full de-identification pass before drafting any output, pseudonymizing miner identifiers, aggregating small injury/illness cells, and separating re-identification keys from circulated documents to protect sensitive worker data.
  • Regulatory Defensibility: Appends OSH-Code transition notes, includes mandatory SME review by a DGMS statutory-compliance specialist, and runs pre-output quality checks to ensure drafts are ready for DGMS-qualified review.
  • Use Case: A mine safety manager in the Dhanbad zone needs to file a 24-hour dangerous occurrence notice after a site accident. The skill captures the event details, resolves the correct form for the zone, de-identifies injured worker information, and produces a draft compliant with DGMS requirements for final review.

Quick Start

Use the dgms-statutory-pack skill to draft a compliant DGMS statutory form for your Indian mine by providing the mine's region/zone, the required obligation type, and relevant event or personnel details.

Frequently Asked Questions about dgms-statutory-pack

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

FAQPage Schema
How do I draft DGMS statutory forms for Indian mining accidents without leaking sensitive miner data?

To draft DGMS statutory forms without leaking sensitive miner data, the skill enforces mandatory de-identification by pseudonymizing miner identifiers and aggregating small injury cells before generating any output.

What is the process for filing a 24-hour dangerous occurrence notice under the Mines Act 1952?

Filing a 24-hour dangerous occurrence notice under the Mines Act 1952 requires capturing structured mine-specific context including region, zone, and event details to resolve the correct verified DGMS form for drafting.

Can I use this to generate Form B employee registers and Form J accident registers for DGMS compliance?

Yes, you can generate Form B employee registers and Form J accident registers for DGMS compliance, as the skill explicitly supports drafting these verified statutory forms alongside annual returns and statutory Manager appointment letters.

Why does generic AI-generated safety paperwork get rejected by DGMS regulators?

Generic AI-generated safety paperwork gets rejected by DGMS regulators due to vague obligations, incorrect form citations, leaked sensitive miner data, and missing required context, which this skill resolves through structured intake and verified form citation.

What are the limitations of using automated tools for DGMS statutory documentation?

A key limitation is that the skill marks unverified form IDs as [GAP] to prevent inventing incorrect form numbers, and it mandates a final SME review by a DGMS statutory-compliance specialist before delivering any drafted output.