Agent skill

Guest Incident Log

by mohitagw15856 in mohitagw15856/pm-claude-skills

Document a guest incident at a hospitality venue — injury, illness, foodborne complaint, altercation, or property loss — into a clear, defensible record.

MITAuto-check passed

Install Guest Incident Log

skills CLI
$ npx skills add mohitagw15856/pm-claude-skills --skill guest-incident-log -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install mohitagw15856/pm-claude-skills guest-incident-log --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/guest-incident-log .claude/skills/guest-incident-log && rm -rf skills-src

Use ~/.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/

Facts

Skill name
guest-incident-log
GitHub stars
1.4k
Token cost
~872 tokens
SKILL.md length
380 words
Files
1
Skills in repo
1,348
Repo updated
First seen
Licence
MIT

At a glance

Document a guest incident at a hospitality venue — injury, illness, foodborne complaint, altercation, or property loss — into a clear, defensible record.

  • Asked to write up a guest incident
  • SKILL.md covers Working from a brief, Required Inputs, Output Format and Quality Checks, plus 2 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
  • Log an accident

What it does

Guest Incident Log is an agent skill from mohitagw15856/pm-claude-skills. 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…

Its SKILL.md is about 870 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 up a guest incident
  • Log an accident
  • Document a slip/fall
  • Allergic reaction

Example prompts

  • “/guest-incident-log”

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

Guest Incident Log loads about 872 tokens when it runs. Until then it costs about 138 tokens; SKILL.md has 380 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~138
When it runs · the whole SKILL.md, loaded when a task matches
~872

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). 380 words, ~872 tokens.

Download SKILL.mdSave it as .claude/skills/guest-incident-log/SKILL.md (or your agent's skills folder).
name
guest-incident-log
description
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.

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
FieldDetail
Date / time / location
Incident typeinjury / illness / foodborne / altercation / property
Persons involvedguest, staff, witnesses (contacts)
Factual accountobserved facts, in sequence
Guest statementsquoted, marked "as reported by guest"
Actions takenaid given, area secured, who was notified
Evidencephotos, 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).

Show full SKILL.md (148 more words)Show less
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

Example Trigger Phrases

  • "Write up a guest incident."
  • "Log an accident."
  • "Document a slip/fall."
  • "Record an incident for insurance/legal."

© 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/guest-incident-log of mohitagw15856/pm-claude-skills.

Open the folder on GitHubat commit 1cbf1f0

Compare with similar skills

Guest Incident Log 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.

Guest Incident Log compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Guest Incident Log this skillmohitagw15856/pm-claude-skills1.4k—~872Automated safety check: PassMIT
Conducting Cloud Incident Responsemukul975/Anthropic-Cybersecurity-Skills34k—~3kAutomated safety check: PassApache-2.0
Incident Responderdavila7/claude-code-templates33k7 repos~2.6kAutomated safety check: PassMIT
Incident Commanderalirezarezvani/claude-skills28k—~3.8kAutomated safety check: PassMIT
Incident Managementsickn33/agentic-awesome-skills47k2 repos~4.5kAutomated safety check: PassMIT
Investigating LogsPostHog/posthog40k—~2.1kAutomated safety check: PassCustom licence

Similar skills

  • Conducting Cloud Incident Response

    mukul975/Anthropic-Cybersecurity-Skills

    Respond to security incidents in AWS, Azure, and GCP via identity-based containment, cloud-native log analysis (CloudTrail, Azure Activity Logs, GCP Audit Logs), resource isolation, and forensic…

    34k GitHub stars~3k tokensUpdated 1 mo ago
    DevOps & CloudAuto-check passed
  • Incident Responder

    davila7/claude-code-templates

    Expert SRE incident responder specializing in rapid problem resolution, modern observability, and comprehensive incident management.

    33k GitHub starsUsed in 7 repos~2.6k tokens
    DevOps & CloudAuto-check passed
  • Incident Commander

    alirezarezvani/claude-skills

    Comprehensive incident response framework from detection through resolution and post-incident review.

    28k GitHub stars~3.8k tokensUpdated 1 mo ago
    DevOps & CloudAuto-check passed
  • Incident Management

    sickn33/agentic-awesome-skills

    Implement incident management processes and escalation procedures.

    47k GitHub starsUsed in 2 repos~4.5k tokens
    DevOps & CloudAuto-check passed
  • Investigating Logs

    PostHog/posthog

    Official

    Investigate logs in a PostHog project: verify a service or deployment is healthy, explain an error spike, triage an incident, or understand what a log stream is saying.

    40k GitHub stars~2.1k tokensUpdated yesterday
    DatabasesAuto-check passed
  • Incident Response

    sickn33/agentic-awesome-skills

    Handle security incidents with IR playbooks and procedures. An agent skill from sickn33/agentic-awesome-skills.

    47k GitHub starsUsed in 1 repo~3.7k tokens
    DevOps & CloudAuto-check passed

More from mohitagw15856/pm-claude-skills

All 1,348 skills in this repo
  • Car 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…

    1.4k GitHub stars~1.1k tokensUpdated yesterday
    Auto-check passed
  • Cs Health Scorecard

    mohitagw15856/pm-claude-skills

    Build a customer health scorecard for a specific account. An agent skill from mohitagw15856/pm-claude-skills.

    1.4k GitHub stars~2.4k tokensUpdated yesterday
    Auto-check passed
  • 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.

    1.4k GitHub stars~1.1k tokensUpdated yesterday
    Auto-check passed
  • Feature Prioritisation

    mohitagw15856/pm-claude-skills

    Apply prioritisation frameworks (RICE, MoSCoW, Kano, ICE, Opportunity Scoring) to rank features and backlog items.

    1.4k GitHub stars~2k tokensUpdated yesterday
    Auto-check passed
  • 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.

    1.4k GitHub stars~1.1k tokensUpdated yesterday
    Auto-check passed
  • 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.

    1.4k GitHub stars~1.2k tokensUpdated yesterday
    Auto-check passed

Questions about Guest Incident Log

What does Guest Incident Log do?

Document a guest incident at a hospitality venue — injury, illness, foodborne complaint, altercation, or property loss — into a clear, defensible record. Guest Incident Log is an agent skill from mohitagw15856/pm-claude-skills. Document a guest incident at a hospitality venue — injury, illness, foodborne complaint, altercation, or property loss — into a clear, defensible record.

When should I use Guest Incident Log?

Guest Incident Log fits situations like: asked to write up a guest incident; log an accident; document a slip/fall; allergic reaction.

How do I install Guest Incident Log in Claude Code?

Run `npx skills add mohitagw15856/pm-claude-skills --skill guest-incident-log -a claude-code`. Or copy the skill folder (skills/guest-incident-log in mohitagw15856/pm-claude-skills) into .claude/skills/guest-incident-log in your project. Claude Code loads it when a task matches its description.

How do I install Guest Incident Log in Codex?

Run `npx skills add mohitagw15856/pm-claude-skills --skill guest-incident-log -a codex`. Or copy the skill folder (skills/guest-incident-log in mohitagw15856/pm-claude-skills) into .agents/skills/guest-incident-log in your project. Codex loads it when a task matches its description.

Can I use Guest Incident Log 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 guest-incident-log -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/guest-incident-log, .gemini/skills/guest-incident-log, .github/skills/guest-incident-log and .opencode/skills/guest-incident-log in your project.

What does Guest Incident Log need to run?

SKILL.md names no scripts, command-line tools or credentials: Guest Incident Log is instructions for the agent only.

Does Guest Incident Log 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 Guest Incident Log 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 Guest Incident Log use?

Guest Incident Log 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 Guest Incident Log use?

About 872 tokens (SKILL.md is roughly 3.5k 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 Guest Incident Log?

Skills that share tags, products or a category with Guest Incident Log: Conducting Cloud Incident Response (mukul975/Anthropic-Cybersecurity-Skills, 34k stars), Incident Responder (davila7/claude-code-templates, 33k stars), Incident Commander (alirezarezvani/claude-skills, 28k stars) and Incident Management (sickn33/agentic-awesome-skills, 47k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Guest Incident Log?

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.