From safetysure-erp
Research-driven emergency identification and analysis skill aligned with AS 3745:2010 Clause 3.2. Conducts web-based research for location-specific external hazards (flood zones, bushfire prone areas, seismic data, cyclone regions, neighbouring industrial facilities) and combines these with internal facility hazards to produce a comprehensive emergency identification register (Appendix G) and grouped emergency types for response procedures. Can be invoked standalone via /erp-assess or as part of the full ERP development workflow. Use this skill whenever conducting emergency identification for a facility, researching location-based hazards for emergency planning, building an emergency risk register, or assessing what emergencies a site needs to plan for.
npx claudepluginhub teddychenfeiyang-png/safetysure-plugins --plugin safetysure-erpThis skill uses the workspace's default tool permissions.
You are conducting an emergency identification and analysis for a facility per AS 3745:2010 Clause 3.2. This assessment identifies all foreseeable emergencies — both from facility operations (internal) and from the facility's geographic location and surroundings (external) — and organises them for use in an Emergency Response Plan.
Searches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.
Searches prompts.chat for AI prompt templates by keyword or category, retrieves by ID with variable handling, and improves prompts via AI. Use for discovering or enhancing prompts.
Checks Next.js compilation errors using a running Turbopack dev server after code edits. Fixes actionable issues before reporting complete. Replaces `next build`.
You are conducting an emergency identification and analysis for a facility per AS 3745:2010 Clause 3.2. This assessment identifies all foreseeable emergencies — both from facility operations (internal) and from the facility's geographic location and surroundings (external) — and organises them for use in an Emergency Response Plan.
The assessment produces two distinct outputs that serve different purposes:
erp-emergency-library skill — read its SKILL.md to understand the available industry scenario baselines.as-3745 reference skill — you will need Clause 3.2 for the emergency identification methodology.references/research-checklist.md — this is your structured checklist for location-based research. You work through every item on this checklist for every assessment.references/assessment-output-format.md — this defines the exact table structures for your outputs.Before starting the assessment, confirm you have:
These can come from an intake form JSON, site tool data, or conversational input from the user.
Work through these steps in sequence. Each step builds on the previous one.
Read the appropriate industry scenario file from the erp-emergency-library skill's scenarios/ directory based on the facility type. Also read scenarios/common-all-facilities.md — these universal emergencies apply to every site.
The scenario files provide a starting list of foreseeable emergencies with pre-written consequence and vulnerability descriptions. These are baselines — you will add to them based on research and facility-specific information.
This is the research-driven step. Using the facility address and region, conduct web searches to identify external hazards specific to the location.
Work through every item on references/research-checklist.md. Mark each item as applicable or not applicable with a brief rationale. For applicable items, record your findings.
The research checklist covers:
Natural hazards:
External / neighbouring hazards:
Research quality rules:
Review the facility data (intake form, site tool data, or user-provided information) to identify internal hazards beyond the industry baseline. The research checklist includes triggers for common site-specific hazards:
| Trigger from Intake Data | Emergency to Consider |
|---|---|
| DG Class 3 chemicals listed | Flammable/combustible liquid fire or spill |
| Any hazardous chemicals listed | Chemical spill / toxic release |
| Combustible dust processes | Dust explosion |
| Compressed gas systems | Compressed gas failure / leak |
| Confined spaces identified | Confined space emergency |
| Multi-level or elevated work | Working at height rescue |
| High-voltage equipment, switchrooms | Electrical incident / arc flash |
| LPG or natural gas on site | Gas leak, gas fire/explosion |
| Forklifts or mobile plant | Vehicle/plant incident |
Compile all identified emergencies from Steps 1–3 into a single list, organised by the three AS 3745 categories:
Present this list to the user and ask them to:
Wait for user confirmation before proceeding.
For each confirmed emergency, assess:
| Column | Description |
|---|---|
| Source | Internal, External, or Both |
| Consequences | Potential outcomes for people within the facility |
| Vulnerability Before | Factors that increase likelihood or severity before the event |
| Vulnerability During | Factors that affect response capability during the event |
| Vulnerability After | Factors that affect recovery after the event |
Use conservative, factual language. Describe specific, observable consequences — not vague generalities. Draw on the industry scenario library's pre-written descriptions as a starting point, then adapt to the specific facility.
Produce the full emergency identification register. Every individual risk gets its own row — do not group or consolidate at this stage. Number each item sequentially.
Appendix G table format:
| No. | Risk | Source | Consequences | Vulnerability Before | Vulnerability During | Vulnerability After |
|---|
See references/assessment-output-format.md for the complete table structure and example entries.
Group the Appendix G items into practical response categories for Section 17 procedures. The grouping logic:
Grouping table format:
| Procedure Group | Appendix G Items | Colour Code | Primary Strategy |
|---|
Present the proposed groupings to the user. Explain the rationale: Appendix G lists all individual risks for completeness, while Section 17 uses grouped procedures for usability — workers need practical response steps, not 27 separate procedures.
Wait for user confirmation or adjustments.
Produce two outputs:
Section 16 — Types of Emergencies summary table: Lists the grouped emergency types with colour codes and cross-references to Appendix G item numbers. This goes into the ERP document.
Grouping map (internal reference): Links each Appendix G item to its Section 17 procedure group. This is used by the erp-developer skill in Phase 4 when generating procedures — it does not appear in the final document.
When invoked as part of the full ERP workflow (/erp-develop Phase 3), the outputs feed directly into the ERP document sections.
When invoked standalone (/erp-assess), produce a Word document (.docx) containing:
Save the document to the working folder using the docx skill.