guest-incident-log
Document a guest incident at a hospitality venue — injury, illness, foodborne complaint, altercation, or property loss — into a clear, defensible record. Use when asked to write up a guest incident, log an accident or complaint, document a slip/fall or allergic reaction, or record an incident for insurance/legal. Produces a factual incident report (who/what/when/where, witnesses, actions taken), an immediate-response checklist, notification/escalation steps, and follow-up — objective and liability-aware, without admitting fault.
Profile →npx skills add mohitagw15856/pm-claude-skills --skill guest-incident-log --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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 t
- Working from a brief
- Required Inputs
- Output Format
- Immediate response (if still unfolding)
- Incident report
- Notification & escalation
- Follow-up
- Quality Checks
- Anti-Patterns
What does the guest-incident-log skill do?
Document a guest incident at a hospitality venue — injury, illness, foodborne complaint, altercation, or property loss — into a clear, defensible record. Use when asked to write up a guest incident, log an accident or complaint, document a slip/fall or allergic reaction, or record an incident for insurance/legal. Produces a factual incident report (who/what/when/where, witnesses, actions taken), an immediate-response checklist, notification/escalation steps, and follow-up — objective and liability-aware, without admitting fault.
How do I install it?
Run `npx skills add mohitagw15856/pm-claude-skills --skill guest-incident-log --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From mohitagw15856/pm-claude-skills, a repository with 1,255 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.