Brief
alirezarezvani/claude-skills
/cs:brief <topic — Generate a one-page strategy brief from an office-hours intake.
Produce a toolbox talk or pre-task safety briefing from the day's planned construction work.
MITAuto-check passed
Install Site Safety Briefing
$ npx skills add mohitagw15856/pm-claude-skills --skill site-safety-briefing -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mohitagw15856/pm-claude-skills site-safety-briefing --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/site-safety-briefing .claude/skills/site-safety-briefing && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "site-safety-briefing" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/site-safety-briefing into .claude/skills/site-safety-briefing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "site-safety-briefing", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/site-safety-briefingType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add mohitagw15856/pm-claude-skills --skill site-safety-briefing -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mohitagw15856/pm-claude-skills site-safety-briefing --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/site-safety-briefing .agents/skills/site-safety-briefing && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "site-safety-briefing" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/site-safety-briefing into .agents/skills/site-safety-briefing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "site-safety-briefing", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mohitagw15856/pm-claude-skills --skill site-safety-briefing -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mohitagw15856/pm-claude-skills site-safety-briefing --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/site-safety-briefing .cursor/skills/site-safety-briefing && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "site-safety-briefing" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/site-safety-briefing into .cursor/skills/site-safety-briefing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "site-safety-briefing", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/mohitagw15856/pm-claude-skills.git --path skills/site-safety-briefing--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add mohitagw15856/pm-claude-skills --skill site-safety-briefing -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mohitagw15856/pm-claude-skills site-safety-briefing --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/site-safety-briefing .gemini/skills/site-safety-briefing && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "site-safety-briefing" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/site-safety-briefing into .gemini/skills/site-safety-briefing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "site-safety-briefing", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install mohitagw15856/pm-claude-skills site-safety-briefingInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add mohitagw15856/pm-claude-skills --skill site-safety-briefing -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/site-safety-briefing .github/skills/site-safety-briefing && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "site-safety-briefing" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/site-safety-briefing into .github/skills/site-safety-briefing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "site-safety-briefing", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mohitagw15856/pm-claude-skills --skill site-safety-briefing -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install mohitagw15856/pm-claude-skills site-safety-briefing --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/site-safety-briefing .opencode/skills/site-safety-briefing && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "site-safety-briefing" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/site-safety-briefing into .opencode/skills/site-safety-briefing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "site-safety-briefing", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
site-safety-briefing- GitHub stars
- 1.4k
- Token cost
- ~1.4k tokens
- SKILL.md length
- 695 words
- Files
- 1
- Skills in repo
- 1,348
- Repo updated
- First seen
- Licence
- MIT
At a glance
Produce a toolbox talk or pre-task safety briefing from the day's planned construction work.
- Asked to write a toolbox talk
- SKILL.md covers What This Skill Produces, Required Inputs, Hazard & Controls Framework and Output Format, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Prepare a pre-task plan
What it does
Site Safety Briefing is an agent skill from mohitagw15856/pm-claude-skills. Produce a toolbox talk or pre-task safety briefing from the day's planned construction work. Use when asked to write a toolbox talk, prepare a pre-task plan or JHA/JSA briefing, brief a crew on today's hazards, or plan safety for a specific task like a crane pick, excavation, or hot work. Produces a crew-ready briefing with task-specific hazards, controls ordered by the hierarchy of controls, required permits, and explicit stop-work triggers.
Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
The repository describes itself as: 1255 professional Agent Skills for Claude, ChatGPT, Gemini, Cursor & Codex — PRDs, postmortems, leases, medical bills, layoffs, go-bags, new countries. Plain markdown, MIT, in… The licence is MIT.
When your agent uses it
- Asked to write a toolbox talk
- Prepare a pre-task plan
- JHA/JSA briefing
- Brief a crew on todays hazards
Example prompts
- “/site-safety-briefing”
What it can do on your machine
Read from SKILL.md and the folder at commit 1cbf1f0. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Site Safety Briefing loads about 1.4k tokens when it runs. Until then it costs about 117 tokens; SKILL.md has 695 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from mohitagw15856/pm-claude-skills at commit 1cbf1f0, republished under its MIT licence (© mohitagw15856). 695 words, ~1,400 tokens.
Download SKILL.mdSave it as
.claude/skills/site-safety-briefing/SKILL.md (or your agent's skills folder).- name
- site-safety-briefing
- description
- Produce a toolbox talk or pre-task safety briefing from the day's planned construction work. Use when asked to write a toolbox talk, prepare a pre-task plan or JHA/JSA briefing, brief a crew on today's hazards, or plan safety for a specific task like a crane pick, excavation, or hot work. Produces a crew-ready briefing with task-specific hazards, controls ordered by the hierarchy of controls, required permits, and explicit stop-work triggers.
Site Safety Briefing Skill
A toolbox talk that could apply to any site on any day protects nobody. This skill builds the briefing from today's actual work: what tasks are running, what they conflict with, what the weather and site conditions add, and — critically — what conditions mean the crew stops and calls the supervisor. Controls are ordered by the hierarchy of controls, because "wear your PPE" is the last line of defence, not a plan.
What This Skill Produces
- A crew-ready briefing (readable aloud in 5–10 minutes) for the day's specific tasks
- A task-hazard-control table with controls ordered by the hierarchy of controls
- Permit and inspection checklist (hot work, excavation, confined space, lift plans, LOTO, etc.)
- Simultaneous-operations (SIMOPS) conflicts between crews working near each other
- Explicit, observable stop-work triggers and the emergency basics (muster point, nearest hospital, who calls)
Required Inputs
Ask for what's missing; from a bare task name, build the briefing from typical hazards and label site-specific items [confirm on site]:
- Today's tasks — what work, where on site, which crews/trades
- Site conditions — weather forecast, ground conditions, live utilities, public interface, stage of construction
- Adjacent operations — what else is happening nearby (other trades, deliveries, crane operations)
- Equipment in use — lifts, cranes, excavators, powder-actuated tools, temporary power
- Known site rules — client/GC permit systems, exclusion zones, prior incidents or near-misses worth referencing
Hazard & Controls Framework
Identify hazards per task, not generically. Sweep these classes for each task: gravity (falls, dropped objects), mechanical/energy (struck-by, caught-between, stored energy, electrical), excavation/ground (collapse, utilities, water), atmosphere (confined space, dust, fumes, hot work), environment (heat/cold, wind — especially for crane picks and panel handling), and human factors (new crew members, fatigue, language barriers).
Order every control by the hierarchy — and say which level it is:
| Level | Control | Example |
|---|---|---|
| 1 | Eliminate | Prefabricate at ground level instead of working at height |
| 2 | Substitute | Mechanical lifting instead of manual handling; low-VOC product |
| 3 | Engineering | Guardrails, trench box, ventilation, physical barricades |
| 4 | Administrative | Permits, exclusion zones, spotters, rotation, signage |
| 5 | PPE | Harness, respirator, cut gloves — the last layer, never the plan |
If a briefing's controls are all level 4–5, flag it: the task plan itself may need rework.
Stop-work triggers must be observable. Not "if unsafe" — write conditions a crew member can see: wind above the crane chart limit; water entering the excavation; utility strike or unexpected line; barricade down in the exclusion zone; anyone in the fall zone during the pick. State plainly that anyone can stop work without repercussions.
Output Format
Show full SKILL.md (283 more words)Show less
Pre-Task Safety Briefing — [Date] — [Site/Area]
1. Today's work — tasks, crews, locations, in one glance. 2. Task hazard & control table — | Task | Hazard | Control (hierarchy level) | Who verifies | 3. Permits & inspections required today — permit type, task, who holds it, valid when. 4. SIMOPS / crew interfaces — who's working near whom, and the separation rule. 5. Stop-work triggers — bulleted, observable, with "stop, make safe, call [supervisor]". 6. Emergency info — muster point, first aider, nearest hospital, who calls emergency services. 7. Sign-on sheet — name/signature lines; space for crew-raised concerns (record them — that's the point of the talk).
Quality Checks
- Every hazard ties to a specific task happening today — no generic filler hazards
- Every control states its hierarchy level, and PPE is never the only control for a serious hazard
- Permits listed match the tasks (hot work, excavation >1.2m/4ft, confined space, critical lifts, LOTO)
- Stop-work triggers are observable conditions, not attitudes
- SIMOPS conflicts between today's crews are addressed or explicitly ruled out
- Readable aloud in under 10 minutes — a briefing nobody listens to protects nobody
Anti-Patterns
- Do not produce a generic talk that ignores today's task list — reusability is the enemy of relevance
- Do not jump straight to PPE — walk the hierarchy from elimination down and show the levels skipped
- Do not write "be careful" or "stay alert" as a control — name the physical or procedural measure
- Do not omit adjacent-crew hazards — most struck-by events involve someone else's operation
- Do not fabricate site-specific details (utility locations, wind limits) — mark them
[confirm on site]for the supervisor to fill in
Example Trigger Phrases
- "Write a toolbox talk."
- "Prepare a pre-task plan or JHA/JSA briefing."
- "Brief a crew on today's hazards."
- "Plan safety for a specific task like a crane pick."
© mohitagw15856, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/site-safety-briefing of mohitagw15856/pm-claude-skills.
Open the folder on GitHubat commit 1cbf1f0
Compare with similar skills
Site Safety Briefing next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Site Safety Briefing this skillmohitagw15856/pm-claude-skills | 1.4k | — | ~1.4k | Automated safety check: Pass | MIT | |
| Briefalirezarezvani/claude-skills | 28k | — | ~967 | Automated safety check: Pass | MIT | |
| Sitesasgeirtj/system_prompts_leaks | 69k | — | ~1.6k | Automated safety check: Pass | CC0-1.0 | |
| Python Type Safetywshobson/agents | 40k | — | ~1.4k | Automated safety check: Pass | MIT | |
| Briefdavepoon/buildwithclaude | 3.6k | — | ~1.3k | Automated safety check: Notes | MIT | |
| Review Briefevery-app/open-seo | 23k | — | ~1.2k | Automated safety check: Pass | MIT |
Similar skills
Sites
asgeirtj/system_prompts_leaks
A skill your agent uses when creating or updating a website, web app, or browser game, or when a visual layout or interactive tool would help with what the user is doing.
Python Type Safety
wshobson/agents
Python type safety with type hints, generics, protocols, and strict type checking.
Brief
davepoon/buildwithclaude
Session-start briefing from Origin. An agent skill from davepoon/buildwithclaude.
Review Brief
every-app/open-seo
Produce a scannable review brief for a branch or PR so the maintainer can approve without reading the whole diff.
Conference Talk Slides from Papers
Orchestra-Research/AI-Research-SKILLs
Generates Beamer LaTeX PDF and editable PPTX slides from a compiled paper, with speaker notes and an optional talk script, sized to four talk lengths.
More from mohitagw15856/pm-claude-skills
All 1,348 skills in this repoCar Tco
mohitagw15856/pm-claude-skills
Compare the total cost of car ownership across buy-new, buy-used, lease, and keep-your-current-car — depreciation, insurance, maintenance ramp, and fuel over a real horizon, not just the monthly…
Cs Health Scorecard
mohitagw15856/pm-claude-skills
Build a customer health scorecard for a specific account. An agent skill from mohitagw15856/pm-claude-skills.
Exit Waterfall
mohitagw15856/pm-claude-skills
Compute who gets what at each exit price from a cap table — liquidation preferences, conversion points, and where the founders' share collapses.
Feature Prioritisation
mohitagw15856/pm-claude-skills
Apply prioritisation frameworks (RICE, MoSCoW, Kano, ICE, Opportunity Scoring) to rank features and backlog items.
Fire Number
mohitagw15856/pm-claude-skills
Compute a financial-independence (FIRE) target and years-to-reach with every assumption labeled as an assumption — plus a sensitivity table instead of a single false-precision answer.
Freelance Rate
mohitagw15856/pm-claude-skills
Derive a freelance day/hourly rate backwards from target income, honest billable utilization, overhead, and the self-employment tax premium — the arithmetic that proves a rate is not salary÷2000.
Questions about Site Safety Briefing
What does Site Safety Briefing do?
Produce a toolbox talk or pre-task safety briefing from the day's planned construction work. Site Safety Briefing is an agent skill from mohitagw15856/pm-claude-skills. Produce a toolbox talk or pre-task safety briefing from the day's planned construction work.
When should I use Site Safety Briefing?
Site Safety Briefing fits situations like: asked to write a toolbox talk; prepare a pre-task plan; JHA/JSA briefing; brief a crew on todays hazards.
How do I install Site Safety Briefing in Claude Code?
Run `npx skills add mohitagw15856/pm-claude-skills --skill site-safety-briefing -a claude-code`. Or copy the skill folder (skills/site-safety-briefing in mohitagw15856/pm-claude-skills) into .claude/skills/site-safety-briefing in your project. Claude Code loads it when a task matches its description.
How do I install Site Safety Briefing in Codex?
Run `npx skills add mohitagw15856/pm-claude-skills --skill site-safety-briefing -a codex`. Or copy the skill folder (skills/site-safety-briefing in mohitagw15856/pm-claude-skills) into .agents/skills/site-safety-briefing in your project. Codex loads it when a task matches its description.
Can I use Site Safety Briefing in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mohitagw15856/pm-claude-skills --skill site-safety-briefing -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/site-safety-briefing, .gemini/skills/site-safety-briefing, .github/skills/site-safety-briefing and .opencode/skills/site-safety-briefing in your project.
What does Site Safety Briefing need to run?
SKILL.md names no scripts, command-line tools or credentials: Site Safety Briefing is instructions for the agent only.
Does Site Safety Briefing access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Site Safety Briefing safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Site Safety Briefing use?
Site Safety Briefing is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Site Safety Briefing use?
About 1.4k tokens (SKILL.md is roughly 5.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Site Safety Briefing?
Skills that share tags, products or a category with Site Safety Briefing: Brief (alirezarezvani/claude-skills, 28k stars), Sites (asgeirtj/system_prompts_leaks, 69k stars), Python Type Safety (wshobson/agents, 40k stars) and Brief (davepoon/buildwithclaude, 3.6k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Site Safety Briefing?
mohitagw15856 (a GitHub user) maintains it in mohitagw15856/pm-claude-skills, which has 1,434 GitHub stars. The repository holds 1,348 skills in this directory. The repository was last updated on October 9, 2026.
Source: mohitagw15856/pm-claude-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.