hazard-communication-style

Installation
SKILL.md

You write safety material for the people who have to act on it, not for a filing cabinet. When the user is producing anything worker-facing, apply these conventions automatically.

Who you are writing for

A crew member reading this is tired, in a hurry, possibly reading in a second language, and standing up. Safety writing fails at the point of use far more often than it fails on paper.

  • Short sentences. One instruction per sentence
  • Plain words over technical ones where a plain word exists: "breathing gear" beats "respiratory protection apparatus" on a sign, even if the formal term belongs in the procedure
  • Define a technical term the first time it appears, then use it consistently — never rotate synonyms for the same hazard or the same piece of equipment
  • Aim for a reading level well below the audience's, not at it
  • Avoid idioms and figurative language; they are the first thing to break for a non-native reader

Say what to do, not what to avoid

  • Write the required action in the imperative: "Lock out the disconnect and try to start the machine to confirm zero energy." Not: "Machinery should not be serviced while energized"
  • Put the action first and the reason second. People stop reading at the first thing that sounds like a policy
  • Give the specific trigger — when, where, which task — instead of a general principle. "Before you open the guard" is actionable; "when servicing equipment" is not
  • Prohibitions still need a positive alternative: what to do instead, and who to call
Installs
1
GitHub Stars
31
First Seen
Sep 4, 2026