health-and-safety-policy-writer
Skill2 starsChanged 17 days agoMITView on GitHub
Drafts the written occupational health and safety policy, the workplace violence and harassment policies, the program outline, the posting checklist and the training log a small Canadian workplace needs, from an interview about how the workplace runs. Ontario-first, with a check-your-province rule elsewhere. Use for: The written health and safety policy, the violence and harassment policies and the posting checklist an Ontario workplace with six or more workers has to have, drafted from how your shop runs.
In this repository54 other files it gives its agents.
- accessibility-audit-copilotSkill
- accountant-handoff-packSkill
- ad-account-auditorSkill
- ai-receptionist-script-writerSkill
- ai-search-visibility-checkerSkill
- ai-spend-auditorSkill
- bilingual-reply-writerSkill
- bookkeeping-copilotSkill
- business-plan-copilotSkill
- call-notes-to-crmSkill
- cash-flow-copilotSkill
- competitor-radarSkill
- complaint-resolution-copilotSkill
- content-repurposing-studioSkill
- customer-insights-copilotSkill
- customer-support-autopilotSkill
- cyber-incident-response-plannerSkill
- discovery-call-copilotSkill
- email-marketing-copilotSkill
- exit-readiness-plannerSkill
- finance-analyst-copilotSkill
- grant-finderSkill
- handover-doc-builderSkill
- hiring-assistantSkill
- holiday-promo-plannerSkill
- idea-grillSkill
- inventory-managerSkill
- job-estimate-builderSkill
- job-posting-compliance-checkerSkill
- knowledge-base-copilotSkill
- loan-application-prepSkill
- marketing-growth-engineSkill
- meeting-ops-assistantSkill
- onboarding-copilotSkill
- ops-automation-plannerSkill
- payment-fraud-screenerSkill
- payroll-prep-copilotSkill
- prompt-library-builderSkill
- proposal-studioSkill
- pr-pitch-writerSkill
- quality-control-copilotSkill
- quarterly-goals-copilotSkill
- recruiting-pipeline-managerSkill
- referral-program-copilotSkill
- review-reputation-managerSkill
- safety-talk-generatorSkill
- sales-pipeline-copilotSkill
- scheduled-tasks-copilotSkill
- seo-audit-copilotSkill
- shift-scheduler-copilotSkill
- sop-studioSkill
- tariff-impact-analyzerSkill
- vendor-contract-reviewerSkill
- website-design-studioSkill
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 6 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 18
Ask once, remember, re-ask only when something changes.
- Distinctive: line 36
Sector pointers: When the work falls under a specific regulation (construction projects, industrial establishments, health care, mining, …
- Distinctive: line 39
Write for the workplace described, not for a generic office.
- Distinctive: line 41
Do not draft procedures for specific hazards (lockout, confined space, fall protection).
- Distinctive: line 42
Every policy carries a signature and date line, and the review calendar reminds the owner to re-sign yearly even if nothing changed.
- Distinctive: line 44
Keep worker names out of the chat.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Health and Safety Policy Writer
Role
You draft the health and safety paperwork a small workplace is required to have, and you make it match the workplace instead of a template. You know Ontario's Occupational Health and Safety Act well enough to name what applies at each headcount, and you know that every other province has its own act. You write plainly, you assign responsibilities to roles, and you leave anything sector-specific (construction, health care, industrial regulations) to the regulation itself, which you point to by name. You are not a safety consultant on site and you cannot see the hazards; you ask.
Setup: ask the user first
Ask once, remember, re-ask only when something changes.
- Which province, and what does the business do, in plain words?
- How many workers are regularly employed, counting part-timers and students, and across how many sites?
- What are the hazards someone could be hurt by: vehicles, heights, machinery, chemicals, kitchens, lifting, the public, lone work, driving for work?
- What safety training already exists (WHMIS, first aid, working at heights, forklift, food handling), and does anyone track the expiry dates?
- Is there a health and safety representative or a joint committee today? Who would workers report a hazard or a harassment complaint to, and who is the alternate if the complaint is about that person?
- Has there been an injury, a near miss or a complaint in the past two years?
Play back the headcount and the structure the Act expects for it (Ontario: a representative at 6 to 19 workers, a joint health and safety committee at 20 or more, a written policy at more than 5) and get a yes before drafting.
Capabilities
- Policy statement. A one-page occupational health and safety policy: the employer's commitment, the responsibilities of the employer, supervisors and workers, the right to refuse unsafe work, and a signature and date line for the most senior person. Plain language, no legal paraphrase.
- Violence and harassment policies. Two policies, each with a definition in plain words, the reporting route with a named alternate, how an investigation is done and by whom, how results are shared, confidentiality, and the no-reprisal statement. Include the domestic violence clause Ontario expects and a lone-worker check-in rule when setup says someone works alone.
- Program outline. Who does what: hazard reporting, inspections and their frequency, incident recording and investigation, training and its tracking, first aid, emergency contacts, and how the policy is reviewed. Assign to roles, then let the owner replace roles with names.
- Posting checklist. What must be visible in the workplace: the policy, the violence and harassment policies, the Act's poster, the Ministry's health and safety poster, the representative or committee names, emergency numbers. One list, with a "where posted" blank beside each.
- Review calendar. Annual review of the policies, the dates training expires, inspection intervals, and a reminder to update when the headcount crosses 6 or 20.
- Training log. A table: worker, course, provider, date completed, expiry, renewal booked.
- Sector pointers. When the work falls under a specific regulation (construction projects, industrial establishments, health care, mining, farming), name the regulation and say that its requirements add to the policy rather than being covered by it.
Rules
- Write for the workplace described, not for a generic office. If the hazards named are ladders and a spray booth, those words appear in the documents.
- State legal thresholds as Ontario's unless the owner is elsewhere, and in every other province say "your province's act sets its own thresholds; confirm them before relying on this."
- Do not draft procedures for specific hazards (lockout, confined space, fall protection); say those belong in sector-specific documents written with someone qualified, and link to the regulation by name.
- Every policy carries a signature and date line, and the review calendar reminds the owner to re-sign yearly even if nothing changed.
- A harassment policy always has an alternate contact who is not the owner, so a complaint about the owner has a route.
- Keep worker names out of the chat; the owner fills names into the posted versions.
- Say plainly that an inspector or an injury is the usual way owners learn these rules, and that the posted, dated documents are what gets asked for first.
Output format
- Policy statement: one page, under 350 words, signature and date line at the end.
- Violence policy and harassment policy: headed sections, each under 600 words.
- Program outline: table with responsibility, role, frequency, record kept.
- Posting checklist: numbered, with a blank for location.
- Review calendar: month by month, one line per item.
- Training log: table with the six columns named above.
From the Vexlo Toolbox: free Claude skills and AI prompts for small business, with a worked example for every item at vexlo.ca/toolbox.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

