mine-incident-investigation

Investigate DGMS-reportable mining incidents with de-identified ICAM root cause analysis.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Generic AI-generated mining incident documentation fails regulatory review: it uses vague task descriptions, defaults to PPE-only controls, assigns blame to individual miners instead of systemic factors, invents unverified DGMS form numbers, and leaks sensitive personal and health data in widely shared reports. This Skill eliminates those failures by enforcing de-identification-first processing, structured fact elicitation, and strict adherence to verified regulatory anchors.

Core Features & Use Cases

  • De-identification-First Workflow: Scrubs all personal/health identifiers, exact mine locations, and suppresses small (<5) injury/fatality cells before any analysis, with a separate re-identification key kept access-controlled.
  • ICAM-Led Root Cause Analysis: Runs ICAM (default) or other selected RCA methods to identify systemic and organisational contributing factors, never stopping at "miner error", with every cause tied to a numbered evidence item.
  • DGMS Reportability Verification: Resolves the mine's DGMS region/zone first, cites only verified 24-hour accident notice and Form J anchors, and marks all unverified form IDs as [GAP] instead of inventing them.
  • Hierarchy-of-Controls CAPA: Drafts corrective actions ranked by the hierarchy of controls, each tracing to a named root cause with a designated owner and due date.
  • Use Case: For a roof fall at an underground coal mine in the Dhanbad DGMS zone, use this Skill to investigate the incident, run ICAM RCA to identify organisational contributing factors, confirm the 24-hour notice and Form J reporting requirements, and draft a compliant corrective action plan with assigned owners.

Quick Start

Use the mine-incident-investigation skill to investigate your mining incident by providing event details, DGMS region/zone, and available evidence through the structured intake to receive a de-identified, DGMS-compliant report with root cause analysis and corrective actions.

Frequently Asked Questions about mine-incident-investigation

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

FAQPage Schema
How do I investigate a mining accident for DGMS compliance without leaking personal data?

Mining incident investigation enforces de-identification-first processing by scrubbing personal identifiers, exact locations, and suppressing small injury cells before analysis. This ensures your DGMS reportability documentation protects sensitive health data while maintaining structured regulatory compliance.

What is ICAM root cause analysis and when should I use it for mining safety incidents?

ICAM root cause analysis identifies systemic and organisational contributing factors in mining incidents rather than defaulting to individual miner error. Use it for DGMS-reportable accidents, dangerous occurrences, and near-misses to ensure every identified cause is tied to numbered evidence.

How to draft a corrective action plan for a mining incident using the hierarchy of controls?

Draft CAPA by ranking corrective actions according to the hierarchy of controls, ensuring each action traces directly to a named systemic root cause. Assign a designated owner and due date to every corrective action for regulatory accountability.

Can I use this incident investigation process for near-misses in Indian mining jurisdictions?

Yes, this incident investigation process applies to DGMS-reportable dangerous occurrences and near-misses across Indian mining jurisdictions. It resolves the specific DGMS region or zone first to verify reportability requirements for your event.

Why does generic incident documentation fail DGMS regulatory review?

Generic documentation fails DGMS review by using vague task descriptions, defaulting to PPE-only controls, inventing unverified form numbers, and blaming individual miners. Structured fact elicitation prevents this by marking unverified form IDs as [GAP] instead of fabricating regulatory anchors.

Does this mining investigation workflow verify DGMS form numbers automatically?

The workflow verifies DGMS reportability by citing only confirmed 24-hour accident notice and Form J anchors based on your resolved region or zone. Any unverified form IDs are explicitly marked as [GAP] to prevent submitting fabricated regulatory citations.