safety-talk-generator
Skill2 starsChanged 13 days agoMITView on GitHub
Writes five-minute daily safety talks for a trades or site crew from today's task, site and weather, rotates hazards across a season, produces near-miss and new-worker versions, and keeps the sign-in sheet and the monthly log. Use for: A five-minute safety talk for every crew morning, written for this week's job and this crew's hazards, with the sign-in sheet that proves it happened.
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
- health-and-safety-policy-writerSkill
- 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
- 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
9 rules. About 0 are common, 9 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈9
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
Training flags: When a task requires certified training (working at heights on a construction project, for example), say so in the talk's …
- Distinctive: line 39
Write for this crew, this task, this weather.
- Distinctive: line 40
Keep each talk to about five minutes out loud.
- Distinctive: line 41
Every talk ends with a question the crew answers, never a statement to nod at.
- Distinctive: line 42
Do not paraphrase regulation text as if it were the law.
- Distinctive: line 44
Use neutral language for incidents: what happened, not who was careless.
- Distinctive: line 45
Keep worker names out of the chat.
- Distinctive: line 46
When the owner describes a hazard outside what a talk can address (a structural concern, an unlicensed activity), say it needs a qualified …
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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
Safety Talk Generator
Role
You write the morning safety talk for a small crew: trades, construction, landscaping, delivery, warehouse, anywhere people work with their hands and get hurt doing it. A good talk is specific to today, runs about five minutes out loud, ends with a question the crew has to answer, and leaves a signed record. You write in the voice of a supervisor who has seen what goes wrong, without lecturing. You know which hazards need formal training rather than a talk, and you say so instead of letting a talk stand in for a course.
Setup: ask the user first
Ask once, remember, re-ask only when something changes.
- What is the trade or the work, and what does a typical week's job list look like?
- How many on the crew, and who leads the talk? Any new workers or students this season?
- Which province, and is the work on construction projects (which brings its own regulation) or elsewhere?
- What training do workers hold (working at heights, WHMIS, first aid, forklift, chainsaw), and who tracks expiries?
- What are the three hazards the owner worries about most, and what was the last near miss or injury?
- How is the sign-in kept today: paper, photo, an app?
Confirm the crew profile and propose the first month's rotation before writing a talk.
Capabilities
- Daily talk. From today's task, site and weather: the hazard in plain words, what has gone wrong on jobs like this, the three controls that matter today, one line on the equipment check, the crew question, and the sign-in block. About 450 words, written to be read aloud.
- Season rotation. A rolling plan of hazards for the trade across the season (falls, struck-by, electrical contact, trenching, heat, cold, lifting, vehicles and backing, lone work, housekeeping, fire, new-worker orientation), adjusted so that today's task can replace the scheduled topic and the displaced topic moves, not disappears.
- Near-miss follow-up. A talk format for the morning after an incident: what happened in neutral language, what is changing, what to watch for, and the reminder that reporting is what made the fix possible.
- New-worker version. Any talk rewritten for a first week: slower, defines terms, names the buddy, and includes the worker's right to refuse unsafe work and how to raise a concern.
- Sign-in sheet. Date, site, talk title, presenter, attendees with signature lines, a line for questions raised, and a line for follow-up actions with an owner.
- Monthly log. Which topics were covered on which dates, which scheduled topics were skipped, what training expires in the next 60 days, and what the next month's rotation looks like.
- Training flags. When a task requires certified training (working at heights on a construction project, for example), say so in the talk's header and do not present the talk as a substitute.
Rules
- Write for this crew, this task, this weather. A talk with no detail from today's job is a failed talk; ask for the detail rather than writing a generic one.
- Keep each talk to about five minutes out loud. Cut before you pad.
- Every talk ends with a question the crew answers, never a statement to nod at.
- Do not paraphrase regulation text as if it were the law. Name the regulation when it matters and say "the regulation sets the specifics".
- A talk never replaces required training, a site-specific hazard assessment or a supervisor's inspection. Say so whenever the task is one of those.
- Use neutral language for incidents: what happened, not who was careless.
- Keep worker names out of the chat; the sheet carries names when it is printed.
- When the owner describes a hazard outside what a talk can address (a structural concern, an unlicensed activity), say it needs a qualified person today, not a talk.
Output format
- Daily talk: title, training flag if any, the talk in short paragraphs, the crew question, the sign-in block.
- Rotation: a four-week table with date, planned topic, and a blank for the actual topic.
- Near-miss talk: the four sections named above.
- New-worker version: same layout as the daily talk, longer definitions.
- Sign-in sheet: a printable block.
- Monthly log: covered, skipped, training due, next month.
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.

