# Hse Incident Tracker > A Claude skill from ttracx/oil-and-gas-claude-skills. - **Type:** Skill - **Install:** `agentstack add skill-ttracx-oil-and-gas-claude-skills-hse-incident-tracker` - **Verified:** Yes — security-reviewed for prompt injection and unsafe behavior - **Seller:** [ttracx](https://agentstack.voostack.com/s/ttracx) - **Installs:** 0 - **Category:** [Agent Skills](https://agentstack.voostack.com/c/agent-skills) - **Latest version:** 0.1.0 - **License:** MIT - **Upstream author:** [ttracx](https://github.com/ttracx) - **Source:** https://github.com/ttracx/oil-and-gas-claude-skills/tree/main/skills/hse_incident_tracker ## Install ```sh agentstack add skill-ttracx-oil-and-gas-claude-skills-hse-incident-tracker ``` Requires the [AgentStack CLI](https://agentstack.voostack.com/docs/cli). Works with Claude Code, Cursor, and any MCP-compatible agent. ## About # HSE Incident Tracker ## What this skill does Scans daily drilling reports, operations summaries, and morning reports for safety incidents, near misses, non-productive time events, reportable events, and environmental occurrences. Produces structured event logs with timestamps, descriptions, severity classifications, and IADC/OSHA category codes. ## When to use - User uploads drilling reports and wants HSE events extracted - User asks for a safety summary or incident log for a well or time period - User needs NPT categorized by cause for end-of-well reporting - User is auditing HSE compliance across a set of daily reports - User wants to identify recurring incident patterns ## Trigger phrases - "Extract HSE events from these drilling reports" - "Find all safety incidents in the past month of DDRs" - "Summarize near misses and recordable incidents" - "What NPT events are related to safety?" - "Generate an HSE incident log from these reports" - "Classify the NPT events by IADC category" - "How many hours of safety-related NPT in this well?" - "Flag all dropped objects and SIF potential events" ## Inputs - Daily drilling reports (PDF, DOCX, TXT) - Morning / operations reports - HSE-specific reports or incident forms (PDF, DOCX) - Safety observation cards (if structured) - Optional: IADC tour report templates ## Outputs - Chronological incident event log - Incident count by severity classification - NPT hours attributed to HSE causes - Category breakdown (IADC classifications) - Recurring incident pattern analysis - Near miss and SIF-potential event list - Environmental incident list - Structured JSON with source references ## Event types tracked ### Safety incidents | Severity | Definition | |---|---| | Fatality | Work-related death | | Lost Time Incident (LTI) | Injury preventing work beyond day of incident | | Restricted Work Case (RWC) | Injured person on modified duty | | Medical Treatment Case (MTC) | Injury requiring treatment beyond first aid | | First Aid Case (FAC) | Minor injury treated on site | | Near Miss | Incident without injury — potential consequence present | | Unsafe Act / Condition | Hazard observed, no incident | | Dangerous Occurrence | Defined reportable event without injury | | SIF Potential | Serious Injury or Fatality potential classification | ### IADC NPT / incident categories - Equipment failure (mechanical) - BHA / downhole tool failure - Wellbore instability (stuck pipe, cavings, tight hole) - Mud-related (losses, gas cut, chemistry) - Cementing issues - Wellhead / tree equipment - Lifting and rigging - Fire / explosion potential - H2S release or potential - Spill / environmental - Personnel safety (struck-by, caught-in, slip/trip/fall) - Weather / environmental conditions - Third-party / service company - Waiting on orders (WOO) — not an HSE event but often grouped - Regulatory hold / inspection ### Environmental incidents - Drilling fluid spill (volume, containment status) - Produced water spill - Chemical spill - Waste disposal non-compliance - Wildlife encounter or impact ## Extraction patterns Keywords and phrases that trigger event extraction: **Injury/incident keywords:** incident, injury, hurt, medical, treatment, hospital, ambulance, LTI, RWC, MTC, FAC, near miss, unsafe, hazard, SIF, dropped object, struck by, caught in, pinch point, slip, trip, fall, burn, laceration, sprain, strain **HSE-NPT keywords:** H2S, gas, kick, influx, blowout, fire, explosion, spill, leak, dropped, falling object, over-pressure, stuck pipe, wellbore instability, loss of well control, pressure test fail, safety stop, safety meeting, safety observation, toolbox talk, JSA, LOTO, energy isolation **Environmental keywords:** spill, release, discharge, contamination, pit overflow, produced water, brine, diesel, oil sheen, wildlife, aquifer, groundwater, containment breach, secondary containment ## Severity classification logic 1. Check for explicit severity labels in text (LTI, RWC, MTC, FAC, near miss) 2. If severity not explicit, infer from: - Presence of "hospital" or "medical center" → MTC or higher - "Unable to work" or "days away" → LTI - "Modified duty" or "light duty" → RWC - "No injury" or "near miss" → Near Miss - Description of hazard only → Unsafe Act/Condition 3. Apply SIF-potential flag when incident involved: - Dropped objects > 2 lbs from height > 6 ft - H2S exposure > TLV - Energy isolation failure - Vehicle/equipment collision - Loss of well control (any severity) ## Output schema ```json { "summary": { "well_name": "string", "reporting_period_start": "string", "reporting_period_end": "string", "total_incidents": 0, "fatalities": 0, "ltis": 0, "rwcs": 0, "mtcs": 0, "facs": 0, "near_misses": 0, "sif_potentials": 0, "environmental_incidents": 0, "total_npt_hrs_hse": 0.0, "trir": 0.0 }, "incidents": [ { "event_id": "string", "date": "string", "time": "string", "severity": "string", "iadc_category": "string", "sif_potential": false, "description": "string", "npt_hrs": 0.0, "source_report": "string", "source_page": "string", "confidence": 0.0 } ], "npt_by_category": [ { "category": "string", "total_hrs": 0.0, "event_count": 0, "percentage": 0.0 } ], "recurring_patterns": [ { "pattern": "string", "occurrence_count": 0, "total_npt_hrs": 0.0, "recommendation": "string" } ], "quality_flags": ["string"] } ``` ## TRIR calculation ``` TRIR = (Recordable incidents × 200,000) / Total manhours worked ``` Recordable incidents = Fatalities + LTIs + RWCs + MTCs If manhours are not available in the reports, flag TRIR as `unable_to_compute` and note what manhour data is needed. ## Recurring pattern detection After extracting all events from multiple reports: 1. Group events by IADC category and keyword similarity 2. Flag any category with ≥ 3 occurrences as a recurring pattern 3. Generate a brief recommendation for each recurring pattern (e.g., "3 pump mechanical failures suggest preventive maintenance schedule review") ## Example response ``` HSE INCIDENT SUMMARY — Wolfcamp B 3H Reporting period: Jan 1 – Mar 15, 2024 (23 DDRs) ══════════════════════════════════════════════ INCIDENT COUNTS ───────────────── Fatalities: 0 Lost Time Injuries: 0 Restricted Work: 1 Medical Treatment: 0 First Aid Cases: 2 Near Misses: 4 SIF-Potential: 1 Total Recordable: 1 TRIR: 0.83 (industry avg: ~1.2 for drilling) HSE-RELATED NPT ──────────────── Total HSE NPT: 8.2 hrs - H2S safety stop (3 events): 4.5 hrs - Personnel injury / evacuation: 1.2 hrs - Safety meeting / inspection stop: 2.5 hrs SIF-POTENTIAL EVENTS ──────────────────── [Feb 12] Dropped 4-lb slip insert from rig floor — 22 ft fall to deck. No injury. Classified SIF-potential (dropped object > 2 lbs, > 6 ft). RECURRING PATTERNS ──────────────────── ⚠ H2S safety stops (3 occurrences): Review H2S monitoring threshold procedures and personal protective equipment compliance for floor crew. ``` ## Source & license This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code. - **Author:** [ttracx](https://github.com/ttracx) - **Source:** [ttracx/oil-and-gas-claude-skills](https://github.com/ttracx/oil-and-gas-claude-skills) - **License:** MIT Install and usage instructions live in the source repository linked above. ## Pricing - **Free** — Free ## Security capabilities Automated source analysis of v0.1.0 — what this tool can access: - **Network access:** no - **Filesystem access:** no - **Shell / process execution:** no - **Environment & secrets:** no - **Dynamic code execution:** no *"Yes" means the capability is present in the source — more access means more to trust, not that it is unsafe.* ## Versions - **0.1.0** — security scan: passed — Imported from the upstream source. ## Links - Listing page: https://agentstack.voostack.com/l/skill-ttracx-oil-and-gas-claude-skills-hse-incident-tracker - Seller: https://agentstack.voostack.com/s/ttracx - Browse the marketplace: https://agentstack.voostack.com/browse --- Listed on AgentStack — the marketplace for AI agent skills and MCP servers. Every listing is security-reviewed. Creators keep 70%.