guest-incident-log
Document a guest incident at a hospitality venue — injury, illness, foodborne complaint, altercation, or property loss — into a clear, defensible re…
它会碰到什么
这一栏是扫描器报的事实,不是结论。命中多不等于有毒(安全工具、规则库、示例脚本本来就会包含危险写法),命中少也不等于干净。它和你手上的凭据、文件、网络有什么关系,需要你自己看。
技能内容
Guest Incident Log Skill
When a guest slips, has a reaction, or complains of illness, what you write in the next hour can protect both the guest and the business — or sink it. This skill captures the facts objectively, records the response, and routes the notifications, without the speculation or apologies-as-admissions that create legal exposure.
Working from a brief
Given what happened, produce the full record — capture only observed facts, mark anything reported-by-guest as such, and never invent details. Flag anything that requires immediate medical, legal, or regulatory action.
Required Inputs
Ask for (if not provided, else infer and label):
- What happened — the incident type and a factual account
- Who — guest, staff involved, witnesses (and contact info if available)
- When/where and the immediate actions already taken
Output Format
Immediate response (if still unfolding)
The right-now checklist: ensure safety/medical aid, secure the area/preserve evidence (the spilled item, the food, photos), don't move hazards until documented, get witness details.
Incident report
| Field | Detail |
|---|---|
| Date / time / location | |
| Incident type | injury / illness / foodborne / altercation / property |
| Persons involved | guest, staff, witnesses (contacts) |
| Factual account | observed facts, in sequence |
| Guest statements | quoted, marked "as reported by guest" |
| Actions taken | aid given, area secured, who was notified |
| Evidence | photos, retained item, CCTV reference |
Notification & escalation
Who to inform and when — manager on duty, owner/GM, insurance carrier, and any mandatory reporting (a suspected foodborne illness may require the health department).
Follow-up
Guest follow-up (care, not admission), corrective action to prevent recurrence, and where the record is retained.
Quality Checks
- [ ] The account is factual and objective; guest claims are marked as reported, not asserted
- [ ] Witnesses and their contact details are captured while fresh
- [ ] Immediate safety/medical response is documented, and evidence preserved
- [ ] Notifications/escalation (incl. any mandatory health-dept reporting) are listed
- [ ] No admissions of fault or speculation about cause
- [ ] Follow-up includes a corrective action to prevent recurrence
Anti-Patterns
- Speculating on cause or fault ("we should have mopped sooner") in the record
- Apologies phrased as admissions of liability
- Vague account with no times, witnesses, or actions
- Losing the evidence (throwing out the food, mopping before photos)
- Forgetting mandatory reporting for a suspected foodborne illness
- Filing it nowhere retrievable when insurance/legal needs it later
想直接用这个技能?
本站把开放许可(MIT / Apache 等)的技能按仓库打包整理到网盘,点一下转存到你自己的网盘,不用一个个从 GitHub 拉。许可未声明的技能只给原始仓库链接,不打包。
同名技能的其他版本
有 3 个不同仓库或目录里都有叫 guest-incident-log 的技能。它们内容并不相同,别混用:
- mohitagw15856/pm-claude-skills — Document a guest incident at a hospitality venue — injury, illness, foodborne complaint, a
- mohitagw15856/pm-claude-skills — Document a guest incident at a hospitality venue — injury, illness, foodborne complaint, a