Purpose
Turn raw temperature log data into a violation-flagged compliance report — identifying every out-of-range reading, ranking each by food-safety severity, prescribing the exact corrective action, and summarizing overall compliance status so managers catch problems before an inspector does.
When to Use
Invoke this skill when the user asks to:
- Review temperature logs for coolers, freezers, walk-ins, or hot-holding units
- Flag out-of-range or missing temperature readings in a log
- Diagnose why a unit keeps failing temperature checks
- Prepare a temperature compliance summary before a health inspection
- Verify cooling or cooking steps met HACCP time/temperature requirements
- Build a corrective action list from a week or month of logs
Inputs Required
Before starting, collect:
- Log data: The readings — as a table, list, or pasted export (include timestamps and unit/location labels if available)
- Equipment/step type: Cold-holding, freezer, hot-holding, cooking, cooling, or reheating (one or a mix)
- Applicable code standard: FDA Food Code, local health department, or organization SOP (default: FDA Food Code)
- Reading frequency expected: How often logs should be recorded (e.g., every 2 hours, per shift)
- Time period covered: Date range of the logs
- Product context (optional): What food is stored/prepared in each unit, if known
If no code standard is specified, apply the FDA Food Code thresholds below and note the assumption.
Instructions
Step 1: Apply the Correct Temperature Thresholds
Match each reading to its standard (FDA Food Code defaults):
- Cold-holding: 41°F (5°C) or below. Anything 42°F+ is out of range.
- Freezer: 0°F (-18°C) or below recommended; product must remain frozen solid.
- Hot-holding: 135°F (57°C) or above. Anything 134°F or below is out of range.
- Cooking (final internal temps): Poultry 165°F; ground meat 155°F; whole cuts/fish 145°F; eggs to order 145°F. Flag any reading below the required minimum for that product.
- Cooling: 135°F → 70°F within 2 hours, then 70°F → 41°F within an additional 4 hours (6 hours total). Flag any cooling record that breaches either window.
- Reheating: 165°F within 2 hours.
- Danger zone: 41°F–135°F. Time spent here is cumulative and matters for cooling/cold-holding failures.
Step 2: Flag Every Reading
Classify each log entry:
- In range — meets threshold
- Out of range — breaches threshold (report actual vs. required)
- Missing — a scheduled reading has no entry (a documentation violation even if temps were fine)
- Suspect — physically implausible or duplicated values suggesting the log was backfilled rather than measured live
Step 3: Assign Severity to Each Violation
- Critical: Reading in the danger zone with likely time-temperature abuse (e.g., cold-holding at 50°F, or cooling that missed the 2-hour mark). Product safety compromised — likely discard.
- Major: Out of range but marginal or short-duration, or a repeated pattern on one unit signaling equipment failure.
- Minor: Missing or late entries, or readings 1–2°F over threshold on a single occasion.
Step 4: Prescribe Corrective Actions
For each flagged reading or pattern, give a specific action — not "monitor more closely":
- Cold-holding breach → check product temp with calibrated thermometer; discard TCS food held above 41°F beyond 4 cumulative hours; service the unit if internal temp is failing.
- Hot-holding breach → reheat to 165°F within 2 hours or discard; verify unit is set correctly.
- Cooling failure → discard product that missed a window; retrain on ice-bath/shallow-pan methods; log corrective in the temperature record.
- Recurring unit failure → escalate to equipment repair; move product to a working unit; increase check frequency until resolved.
- Missing/late entries → identify accountable shift; retrain on logging cadence; consider a reminder system.
Step 5: Identify Patterns
Look across the full period for:
- A single unit failing repeatedly (equipment problem, not human error)
- Failures clustered at specific times (shift change, delivery, defrost cycle)
- Systematic missing entries on certain shifts or days
- Signs of backfilled logs (identical values, round numbers, timestamps out of sequence)
Step 6: Summarize Compliance Status
Produce an overall status: Compliant / Compliant with Corrections Needed / Non-Compliant, with the counts and the top risks driving the rating.
Output Format
- Structure: Compliance summary header → violation table → severity-ranked corrective actions → pattern findings → inspection-readiness note
- Length: 500–900 words depending on log volume
- Format: A violation table (reading, unit, timestamp, actual vs. required, status, severity), plus prose sections for patterns and summary
- Sections: Overall Compliance Status → Flagged Readings Table → Corrective Actions (ranked Critical → Major → Minor) → Patterns & Root Causes → Inspection Readiness
- Tone: Compliance officer — precise, non-alarmist, action-first; cites the specific threshold each violation breached
Quality Checklist
Before delivering output, verify:
- [ ] Every reading is classified (in range / out of range / missing / suspect) — none skipped
- [ ] Each out-of-range reading shows actual value vs. required threshold
- [ ] Every violation has an assigned severity (Critical / Major / Minor)
- [ ] Each corrective action is specific and executable — no "monitor more closely"
- [ ] Missing/skipped scheduled readings are flagged as violations, not ignored
- [ ] The report ends with a single clear compliance status and the count of critical violations
Notes
- Missing documentation is itself a violation — an inspector treats a blank log the same as a failed reading.
- Cooling failures are the most commonly missed on manual review because they require checking two time windows, not one temperature — always verify both the 2-hour and 4-hour marks.
- If timestamps are absent, note that time-based standards (cooling, danger-zone duration) cannot be fully verified, and recommend adding timestamps to future logs.
- Recurring failures on one unit are almost always equipment, not staff — recommend a service check before retraining.
How to use this skill
This file is a Claude Code skill in Anthropic's standard format — markdown with YAML frontmatter at the top.
Installing in Claude Code:
~/.claude/skills/<folder-name>/SKILL.md— auto-loads in every session anywhere on your machine (recommended for skills you'll use across multiple projects)<your-project>/.claude/skills/<folder-name>/SKILL.md— auto-loads only when working in that project (recommended for project-specific skills)
Restart Claude Code or open a new session to register.
Using in Claude.ai, ChatGPT, Gemini, or other AI tools:
- Drag this file into a new chat, or copy and paste its contents
- Send your task or request as your next message — the AI will apply the skill where it fits
For Claude Code skill details: https://docs.anthropic.com/en/docs/claude-code/skills