Qsr Labor Leak Auditor

This skill is internally consistent and appears to do what it says. Before installing, consider: (1) privacy — the skill stores day-by-day labor data in agent memory, so confirm who can read that memory and how long it persists; avoid storing employee PII (names, SSNs, payroll IDs) unless you intend to and have proper protections in place; (2) verification — double-check the calculations (hourly cost, projected overspend) on first runs before taking schedule actions; (3) auditability — keep a separate copy of raw inputs (sales, hours) if you need records for compliance; and (4) model choice — use a capable model for reliable numeric tracking. If you need the skill to integrate directly with POS or scheduling systems, expect it to require explicit API credentials and a different evaluation.