construction-safety-incident

Identifies construction site safety hazards and generates risk findings with disposal strategies.

Updated Sep 2, 2026
One-click install
npx skills add https://github.com/pinedu/xmc-work-wiki --skill construction-safety-incident-pinedu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: construction-safety-incident
Source: https://github.com/pinedu/xmc-work-wiki/tree/main/skills/construction-safety-incident
Command: npx skills add https://github.com/pinedu/xmc-work-wiki --skill construction-safety-incident-pinedu

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? When a construction site accident or safety hazard occurs, the project owner (甲方) needs a fast, consistent way to identify risks, assign responsibility, push the contractor to rectify, and preserve evidence—without relying on ad-hoc judgment. This Skill turns free-text incident descriptions into deterministic risk findings and actionable disposal plans from the owner's standpoint. ## Core Features & Use Cases - Deterministic risk engine: A self-contained Python script maps case text to 23 hazard categories (falls from height, collapse, electric shock, fire, unlicensed special operations, deep excavation monitoring gaps, etc.) plus 5 compound-risk rules, with stage detection (pre/during/post) and double-negation handling. - Mandatory semantic review: A Stage 2 checklist catches engine false negatives/positives, "experience over certification" traps, and schedule-pressure tactics before any output is produced. - Standardized output template: Produces a fixed 6-section plan covering risk findings, disposal strategies with document artifacts (《停工令》《整改通知单》《责任切割协议》), zero-tolerance red lines, stage-adapted actions, and an evidence preservation checklist. - Use Case: A user reports "the formwork support hasn't been inspected but the owner is pushing to pour concrete on floor 10." The Skill flags a major collapse risk, mandates a stop-work order, rejects schedule-pressure reasoning, and lists the evidence to seal. ## Quick Start Describe the site incident or hazard in plain language and ask the assistant to analyze it and produce a disposal plan using this Skill.

Frequently Asked Questions about construction-safety-incident

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I analyze a construction site safety incident description?

Pass the case text to the safety engine script via --text or --file, which outputs structured risk findings with level, responsible party, and disposal strategy in JSON or Markdown. A mandatory semantic review step then checks for missed or false matches before the final templated plan is produced.

What types of construction hazards does this risk engine cover?

It covers 23 hazard categories including falls from height, scaffold and formwork collapse, temporary electricity violations, hot work without permits, unlicensed electricians/welders/riggers, confined space entry, and deep excavation monitoring gaps, plus 5 compound rules for combined scenarios.

Does the engine handle negated or colloquial Chinese phrasing?

Yes. Attribute derivation uses negation-first matching so phrases like "没有安装临边防护" are not misread as positive, and a double-negation exemption recognizes "不是没戴安全帽" as compliant. A semantic review stage still catches wording that bypasses keywords.

Can this Skill handle quality defects or contract disputes?

No. It is scoped strictly to safety incidents and hazards. Quality defects, schedule disputes, contract clause review, and wage arrears are explicitly out of scope and routed to other skills.

Why might the engine miss a hazard described in unusual wording?

The engine is keyword-based, so synonyms or phrasing outside its keyword dictionary can cause false negatives. The mandatory Stage 2 semantic review exists for this reason: it flags suspected misses and recommends extending the keyword dictionary rather than silently reclassifying.