fax-send

# Fax Send Use this skill when a user asks to fax a supported file, web page, text note, or PDF to an external fax number, or when an inbound fax arrives as an email PDF and needs routing to a document workflow such as DATEV Belegtransfer, file storage, or client records. ## Response Contract - Return exactly one user-facing summary per fax request. Do not restate the same plan, missing-input list, or no-send notice in a second format. - For provider results, write the status sentence once. Do not emit both a markdown-styled version and a plain-text duplicate of the same sentence. - Do not use decorative emoji, checkmarks, sign-off text, or "ready to proceed" filler in fax responses. - If setup is blocked by missing secrets, report each missing secret exactly once and only if it is actually required: `SINCH_FAX_PROJECT_ID` plus either `SINCH_FAX_BASIC_AUTH` or `SINCH_FAX_OAUTH_TOKEN`. Never claim a Sinch service ID secret is required for normal outbound sending. - When the user provides text content such as "Hallo Welt", use the helper's helper-generated PDF upload path after the recipient fax number, stored Sinch project ID, stored credential, and explicit approval are available. Omit `from` when the user wants to use the Sinch Fax service default sender. Do not ask the user for a service ID for a normal outbound send; Sinch uses the product's default Fax service when `serviceId` is omitted. - A live `http_request` to Sinch is terminal for that send ...