process-safety-kpi

Compute API RP 754-aligned Tier-1 and Tier-2 process safety event rates.

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

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 rejected by regulators: it uses vague tasks, collapses controls to PPE, leaves actions without owners, attributes incidents to generic "worker error", and leaks personal data into widely shared documents. This skill eliminates those failures by enforcing structured intake to capture exact site, activity, and event details, strict API RP 754 compliance for process safety metrics, fail-loud rate discipline to avoid fabricated figures, and mandatory de-identification of all sensitive data before drafting any output.

Core Features & Use Cases

  • API RP 754-Aligned KPI Computation: Accurately counts Tier-1 and Tier-2 Process Safety Events (PSEs) from user-provided event facts (never invented) and calculates normalized rates with strict fail-loud denominator discipline (missing or zero work hours results in a [GAP] rate marker, no fabricated figures).
  • Leading & Lagging Indicator Framing: Frames Tier-3 (safety system challenges) and Tier-4 (operating discipline) leading indicators alongside lagging PSE counts, with clear distinction from occupational TRIR/LTIFR/DART injury rate metrics.
  • Mandatory Compliance Guardrails: Runs structured multi-step intake to enforce input specificity, mandatory de-identification of all personal/health data before drafting, and domain-expert SME review before any output is presented to ensure regulator-defensible results.
  • Use Case: A process safety manager at an O&G facility needs to generate a Q2 process safety KPI report for leadership, including Tier-1 PSE counts, normalized rates, and leading indicator performance, with all personal data removed and all figures traceable to source evidence.

Quick Start

Use the process-safety-kpi skill to compute the Tier-1 and Tier-2 process safety event rates for your refinery's Q2 reporting period, providing the total work hours denominator to avoid a [GAP] rate marker.

Frequently Asked Questions about process-safety-kpi

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

FAQPage Schema
How do I compute API RP 754 process safety KPIs for my facility?

To compute API RP 754 process safety KPIs, you need exact Tier-1 and Tier-2 process safety event counts alongside total work hours. The skill enforces structured intake to capture these facts and calculates normalized rates with strict fail-loud discipline.

What happens if I don't provide total work hours for process safety event rates?

If total work hours are missing or zero for process safety event rates, the computation enforces fail-loud discipline by inserting a [GAP] rate marker rather than fabricating figures, ensuring your safety metrics remain traceable and regulator-defensible.

How are Tier-3 and Tier-4 leading indicators handled in process safety reporting?

Tier-3 and Tier-4 leading indicators frame safety system challenges and operating discipline alongside lagging Tier-1/Tier-2 process safety event counts. They are computed distinctly from occupational TRIR, LTIFR, and DART injury rate metrics.

Does this tool calculate occupational safety metrics like TRIR and LTIFR?

No, this tool explicitly separates process safety KPIs from occupational TRIR, LTIFR, and DART metric workflows. It focuses strictly on API RP 754 aligned process safety events and leading indicators to prevent collapsing distinct safety reporting domains.

How is personal data protected when generating process safety reports?

Personal data is protected by mandatory de-identification of all sensitive health and personal details before any process safety report is drafted. This eliminates regulator-rejectable safety paperwork and prevents data leaks in widely shared documents.

Can I use this for a single oil and gas facility's quarterly KPI report?

Yes, you can use this for a named oil and gas facility over a defined reporting period. It requires multi-step intake for site-specific event facts and mandates pre-output SME review to ensure leadership receives structured, evidence-backed results.