offshore-safety-case

Structure offshore safety case arguments under SI 2015/398 with gap tracking.

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

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 routinely rejected by regulators: it contains vague tasks, controls that default to personal protective equipment (PPE), unowned actions, root causes that stop at "worker error", and leaked personal or health data. This skill eliminates those failures by enforcing a structured, specificity-first intake, hierarchy of controls ranking, mandatory de-identification, and a strict no-fabrication rule for all quantitative data and barrier claims.

Core Features & Use Cases

  • Structured Intake & Gap Tracking: Runs a one-at-a-time branched intake to capture named installation details, applicable regulatory regime, and all SI 2015/398 Schedule 6/7 safety case elements, flagging any unsupplied QRA, SCE performance standard, or barrier-effectiveness claim as [GAP] instead of inventing data.
  • Regulator-Ready Argument Mapping: Assembles a goal-structured claim → argument → evidence map for UK and EU offshore oil and gas duty holders, cross-referencing the sibling marine-emergency-response plan for emergency response elements instead of rebuilding them.
  • Built-In Compliance Guardrails: Enforces mandatory de-identification of personal and health data, hierarchy of controls ranking for all risk-reduction measures, and a pre-output subject matter expert (SME) review to ensure defensibility against regulator challenge.
  • Use Case: An offshore installation manager needs to assemble a safety case argument for a fixed production platform under SI 2015/398. This skill elicits all required inputs, records their external QRA and SCE register data with full provenance, flags gaps, and produces a compliant, de-identified argument map ready for competent person review.

Quick Start

Use the offshore-safety-case skill to structure a compliant safety case argument for your named offshore installation under SI 2015/398, providing your HAZID, QRA, and SCE register inputs as the structured intake prompts.

Frequently Asked Questions about offshore-safety-case

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

FAQPage Schema
How do I structure an offshore safety case for SI 2015/398 compliance?

To structure an offshore safety case for SI 2015/398, assemble a claim, argument, and evidence map covering major-accident hazard identification, SEMS, CMAPP, ALARP demonstration, and SCE registers. This enforces a strict no-fabrication rule, flagging unsupplied QRA or barrier data as [GAP].

What is the best way to demonstrate ALARP for offshore oil and gas installations?

The best way to demonstrate ALARP for offshore installations is by mapping risk-reduction measures through a strict hierarchy of controls ranking. This ensures defensibility by prioritizing elimination and engineering controls over PPE, while recording all external QRA and consequence modelling claims with provenance.

How do you build a safety case argument map without fabricating quantitative risk data?

You build a safety case argument map without fabricating data by using a structured intake process that captures external QRA and barrier-effectiveness claims with provenance. Any unsupplied quantitative data, SCE performance standards, or QRA inputs are explicitly flagged as [GAP].

Does SI 2015/398 safety case preparation require de-identification of personal data?

Yes, SI 2015/398 safety case preparation requires mandatory de-identification of personal and health data. This prevents leaked sensitive information in regulatory submissions and ensures the structured argument map remains compliant and ready for competent person review.

Can I use this structured intake process for mobile drilling rigs and FPSOs?

Yes, you can use this structured intake process for mobile drilling rigs, FPSOs, fixed production platforms, and support installations. It structures defensible safety case arguments for UK and EU oil and gas duty holders across all applicable installation types.

Why are generic AI safety cases rejected by offshore regulators?

Generic AI safety cases are rejected by offshore regulators because they contain vague tasks, default to PPE controls, and lack provenance for QRA data. This skill eliminates those failures by enforcing hierarchy of controls ranking, mandatory de-identification, and pre-output SME review.