What problem does it solve? When receipts or kitchen tickets stop printing, staff often blindly hammer the reprint button, wasting paper and never fixing the real cause. This Skill reads the print job status and error type first, then narrows the cause to paper, network, or configuration before taking any action. ## Core Features & Use Cases - Error-type triage: Classifies failures by error signature (EX_TIMEOUT+200 means paper jam/out, Failed to fetch+HTTP 0 means network loss, claim jobs failed means benign transient blip) so the right fix is applied. - Safe execution gating: Read-only diagnostics (list_print_jobs, list_printers, get_print_transport) run first; test prints, retries, and transport changes require explicit human confirmation, one operation at a time. - Escalation handling: Near-irreversible transport changes require manager/admin approval, and permission-denied operations are escalated rather than forced. - Use Case: A kitchen ticket stops arriving mid-service. The Skill checks the failed job, sees EX_TIMEOUT with HTTP 200, concludes the printer is reachable but out of paper, and directs staff to refill paper before retrying that single job. ## Quick Start Ask the assistant to figure out why the kitchen tickets are not printing and diagnose the cause before resending anything.
