incident-rate-calculator

Compute OSHA-standard TRIR, DART, and LTIFR with validated exposure bases.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Generic AI tools produce unsafe, regulator-rejectable safety rate calculations: they fabricate missing exposure denominators, perform non-reproducible in-prompt arithmetic, omit full audit trails, and leak sensitive worker incident data. This Skill eliminates those risks by delivering deterministic, fully auditable OSHA-standard incident rates.

Core Features & Use Cases

  • Deterministic Rate Calculation: Computes TRIR, DART, and LTIFR via a tested shared engine with no in-prompt arithmetic, ensuring every result is fully reproducible for audit purposes.
  • Mandatory Input Validation: Runs a structured intake that refuses to proceed without a real, non-zero hours worked denominator, never fabricates default values, and never annualizes partial period data.
  • Built-In De-Identification: Automatically scrubs pasted incident case logs to aggregate counts only, applies small-cell suppression for groups with fewer than 5 individuals, and separates re-identification keys from circulated outputs to protect sensitive worker data.
  • Sourced Benchmarking: Supports optional comparison of computed rates against industry benchmarks, with full citation of the publishing body, year, and sector for every comparator.
  • Use Case: A safety manager can input 3 recordable cases, 2 DART cases, 1 lost-time injury, and 290,000 hours worked for Plant 2 Q1 2026 to get a fully auditable TRIR of 2.07, DART of 1.38, and LTIFR of 3.45, complete with the exact formula and inputs used to generate each figure.

Quick Start

Ask the incident-rate-calculator skill to compute TRIR, DART, and LTIFR for your named site and period, providing the required recordable counts, hours worked, and recordability standard when prompted.

Frequently Asked Questions about incident-rate-calculator

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

FAQPage Schema
How do I calculate OSHA incident rates like TRIR and DART for audit defensibility?

To calculate OSHA incident rates for audit defensibility, you must use deterministic computation with exact formulas, validated non-zero hours worked denominators, and full disclosure of inputs to ensure reproducibility for regulators.

What is the best way to ensure worker data de-identification during safety reporting?

Worker data de-identification during safety reporting requires scrubbing pasted incident case logs to aggregate counts only, applying small-cell suppression for groups under five individuals, and separating re-identification keys from outputs.

Can I compute LTIFR if I only have partial period hours worked data?

No, you cannot compute LTIFR with partial period hours worked data because mandatory input validation refuses to proceed without a real, non-zero denominator and never annualizes partial period data to prevent regulator rejection.

How do I benchmark TRIR results against industry standards?

To benchmark TRIR results against industry standards, you compare computed rates against published sector benchmarks while ensuring full citation of the publishing body, year, and sector for every comparator used.

Why do generic AI tools fail at OSHA compliance rate calculations?

Generic AI tools fail at OSHA compliance rate calculations because they fabricate missing exposure denominators, perform non-reproducible in-prompt arithmetic, omit full audit trails, and risk leaking sensitive worker incident data.