Zhimu WebPrinter

Problem

When printing from a local environment needs to bypass a desktop client, sending files, PDFs, Office documents, or HTTPS documents to a specific printer can get stuck on device discovery, job parameters, and remote link accessibility. Zhimu WebPrinter wraps WEBPRINTER_ACCESS_TOKEN authentication, printer queries, file upload, roaming/direct printing, and task parameter updates into callable actions.

How It Works

The default path creates a roaming print task: local files are first sent through upload-file to obtain an accessible URL, then create-roaming-task is called. If the user explicitly specifies a printer, the skill runs query-printers, uploads local files when needed, and calls print-document. On demand, it can use query-printer-detail to inspect capabilities, or update sides, color, copies, and paper through separate actions. Paper names are converted to millimeter dimensions first, such as A4 to 210 x 297, so the backend does not receive raw paper names.

Boundaries And Cautions

The skill accepts only local files or explicitly provided accessible HTTPS links, and rejects localhost, .local, and similar local addresses. Internal addresses must be flagged because the printing service must be able to reach them. Initial use depends on an OAuth token, the official client, and bound printers; if the token is missing, the client is not bound, or printers are not visible, the flow should stop and surface the corresponding issue.