From pm-hospitality
Runs a self-audit of food establishments before health inspections, prioritizing critical violations that close kitchens. Produces risk-ranked checklists, temperature/hygiene fundamentals, and fix lists with owners.
How this skill is triggered — by the user, by Claude, or both
Slash command
/pm-hospitality:health-inspection-prepThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Inspectors don't fail you on dust — they fail you on the handful of **priority violations** that make people sick: temperature abuse, cross-contamination, bare-hand contact, handwashing, and pest activity. This skill runs the self-audit the way an inspector scores it, so the critical stuff is fixed before they walk in.
Inspectors don't fail you on dust — they fail you on the handful of priority violations that make people sick: temperature abuse, cross-contamination, bare-hand contact, handwashing, and pest activity. This skill runs the self-audit the way an inspector scores it, so the critical stuff is fixed before they walk in.
Given the establishment type, produce the full self-audit — prioritize by public-health risk, not by what's easiest to see. Base it on standard food-code categories; note that local codes vary and the operator should confirm specifics.
Ask for (if not provided, else infer and label):
The violations that shut kitchens — each with the standard and a pass/fail check:
Facility, labeling, storage, cleaning cadence.
| Item | Risk | Fix | Owner | By when |
|---|
How to receive the inspector: cooperate, don't argue, know where the logs and permits are, correct-on-the-spot where possible, and how to respond to a violation professionally.
npx claudepluginhub mohitagw15856/pm-claude-skills --plugin pm-hospitalityGuides completion of development work by verifying tests, detecting environment, and presenting structured options for merge, PR, or cleanup.
Guides creation and editing of skills using test-driven development with pressure scenarios and subagents to verify agent compliance.
Dispatches multiple subagents concurrently for independent tasks without shared state. Use when facing 2+ unrelated failures or subsystems that can be investigated in parallel.