skills.rest
ashley-eyekyam
ashley-eyekyamCOMMUNITY
Explore all skills by this author →
GitHub

level-crossing-track-worker-safety

Generate regulator-aligned safe-system-of-work artifacts for rail level crossings and track work.

1|Updated Jun 14, 2026
Search Tags:#risk assessment#de-identification#hierarchy of controls#rail safety#level crossing#track worker#safe system of work
One-click install
npx skills add https://github.com/ashley-eyekyam/hse-leadership-skills --skill level-crossing-track-worker-safety
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: level-crossing-track-worker-safety
Source: https://github.com/ashley-eyekyam/hse-leadership-skills/tree/main/skills/level-crossing-track-worker-safety
Command: npx skills add https://github.com/ashley-eyekyam/hse-leadership-skills --skill level-crossing-track-worker-safety

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Generic AI-generated rail safety paperwork is often rejected by regulators: it defaults to low-order controls like signage or lone lookouts when higher-order options are practicable, invents ALCRM risk bands, leaks personal data from safety-critical role holders, and lacks site-specific detail. This skill eliminates those failures by enforcing domain-specific control hierarchies, mandatory de-identification, and a structured intake that forces specificity before any drafting.

Core Features & Use Cases

  • Hierarchy-enforced control ranking: Applies the level-crossing remedial hierarchy (closure → grade separation → engineering → signage last) and track-worker protection hierarchy (separation → SSOW → warning → lookout last) to ensure lead controls are the highest reasonably practicable order, rejecting indefensible signage-only or lookout-only treatments.
  • ALCRM compliance: Records user-supplied All Level Crossing Risk Model (ALCRM) bands from licensed model output (never invents, recomputes, or hard-codes band thresholds) to prioritize crossing remediation.
  • Mandatory de-identification: Scrubs COSS, lookout, PICOP, engineering supervisor, and Sentinel number identifiers to role labels, with small incident cell suppression, before any output is circulated.
  • Structured intake workflow: Forces users to provide a named crossing/work site, activity, line status, jurisdiction, and existing controls before drafting, refusing vague or generic requests.
  • Regulator-aligned output: Generates DOCX/PDF safe-system-of-work artifacts with 5x5 residual risk scoring, SMART corrective actions with named role owners and due dates, and mandatory SME review sign-off.
  • Use Case: A rail safety manager needs a defensible safe system of work for a user-worked footpath crossing and adjacent track renewal. This skill produces a compliant artifact that prioritizes grade separation for the crossing and a planned possession for the track work, with all safety roles de-identified to role labels.

Quick Start

Use the level-crossing-track-worker-safety skill to generate a safe system of work for your named level crossing and adjacent track renewal, providing the ALCRM band from your licensed model, the planned possession details, and the safety roles for the site.

Frequently Asked Questions about level-crossing-track-worker-safety

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

FAQPage Schema
How do I create a safe system of work for a level crossing that prioritizes higher-order controls over signage?▼

To create a safe system of work for a level crossing, enforce the remedial hierarchy ranking from closure to grade separation, engineering, and signage last. This ensures lead controls are the highest practicable order and rejects signage-only treatments.

How does ALCRM risk band compliance work when generating rail safety documentation?▼

ALCRM risk band compliance requires recording user-supplied All Level Crossing Risk Model bands from licensed model output. The system never invents, recomputes, or hard-codes band thresholds, ensuring crossing remediation prioritization relies entirely on accurate licensed data.

How do I de-identify safety-critical role holders like COSS and PICOP in a track worker risk assessment?▼

To de-identify safety-critical role holders in a track worker risk assessment, scrub COSS, lookout, PICOP, engineering supervisor, and Sentinel number identifiers down to role labels. This mandatory process includes small incident cell suppression before any output is circulated.

Can I use this system to generate compliant track worker safety documents for both GB and Indian rail jurisdictions?▼

Yes, you can generate regulator-aligned safe-system-of-work artifacts for both GB and Indian rail jurisdictions. The system requires you to specify the jurisdiction alongside named work sites, activities, and line status before drafting compliant safety documentation.

What information do I need to provide before drafting a track worker protection hierarchy plan?▼

Before drafting a track worker protection hierarchy plan, you must provide a named crossing or work site, activity details, line status, jurisdiction, existing controls, and safety role accountabilities. The structured intake refuses vague or generic requests until this specificity is met.

Why does my generic rail safety paperwork get rejected by regulators?▼

Generic rail safety paperwork gets rejected by regulators because it defaults to low-order controls, invents ALCRM risk bands, leaks personal data from safety-critical role holders, and lacks site-specific detail. Enforcing domain-specific control hierarchies and mandatory de-identification eliminates these failures.

Related Skills

Explore More Legal & Compliance Skills→
ashley-eyekyamashley-eyekyam
1

risk-assessment

Generate site-specific hazard identification and risk assessments with hierarchy of controls and expert review.

Community
Advanced
ashley-eyekyamashley-eyekyam
1

psychosocial-risk-assessment

Generate ISO 45003-aligned psychosocial risk assessments with 5x5 scoring and SMART action plans.

Community
Advanced
Happy-Technologies-LLCHappy-Technologies-LLC
34

suggest-remediation-tasks

Generate remediation task recommendations from GRC issues with risk prioritization.

Official
Advanced
ashley-eyekyamashley-eyekyam
1

bowtie-builder

Builds Bowtie diagrams and CCM plans for named process safety hazards and events.

Community
Advanced