Update to DocsAutomator

{
  "description": "Make a quote in the user's own brand with DocsAutomator and send it to them for acceptance, so they can accept it and see the accepted PDF in DocsAutomator. Use when the user wants to send a quote or proposal for acceptance, or asks how to start with DocsAutomator.",
  "included_files": [],
  "name": "send-quote-for-acceptance",
  "skill_md_contents": "---\nname: send-quote-for-acceptance\ndescription: Make a quote in the user's own brand with DocsAutomator and send it to them for acceptance, so they can accept it and see the accepted PDF in DocsAutomator. Use when the user wants to send a quote or proposal for acceptance, or asks how to start with DocsAutomator.\n---\n\n# Send a quote for acceptance\n\nYou make a quote in the user's brand and send it to the user for acceptance. The user accepts it from the email and sees the accepted PDF and its record in DocsAutomator under Documents.\n\n## First check\n\nIf no DocsAutomator tools are available, tell the user plainly that DocsAutomator is not signed in. To fix it, they open Settings, then MCPs, choose docsautomator and choose Authenticate, then start a new chat. Do not try to do the task another way.\n\n## Before you start\n\nAsk for two things in one message: the user's email address (the quote goes to them) and, optionally, their website (for the brand colors and logo).\n\n## Steps\n\n1. Call `list_automations`. If a quote automation exists, ask the user whether to reuse it; to reuse it, go to step 6. Otherwise call `create_automation` with `title: \"Quotes\"` and `dataSourceName: \"API\"`.\n2. Call `generate_word_template` on the new automation:\n   - `title: \"Quote\"` and `signingMode: \"none\"`, because acceptance needs no signature block.\n   - `brandWebsite` set to the user's website, when they gave one. It reads their brand colors and logo.\n   - A prompt for a one-page quote: logo, quote number, date, valid-until date, sender and client details, a line items table (description, quantity, rate, amount), subtotal, tax, total and terms.\n3. If generation fails, call `search` with `in: \"templates\"` and the query \"quote\", then `set_template` with the `galleryTemplateId` of a result that has a Word version.\n4. Call `configure_placeholders` with a description for every placeholder and a format for every amount and date. Set the user's `locale` with `configure_automation`.\n5. Call `configure_esignature` with `closeType: \"acceptance\"`, `deliveryMethod: \"email\"` and one signer `{ role: \"Client\", emailSource: \"request\" }`.\n6. Call `get_automation` for the placeholders. Fill every placeholder with realistic sample data for the user's business. Send numbers as numbers and dates as ISO dates.\n7. Call `create_document` with `mode: \"test\"` and `recipients: [{ signer: 1, email: <user's email>, name: <user's name> }]`.\n8. Tell the user to open the email from DocsAutomator, type their name and click Accept.\n\nTest mode sends the real email and adds a preview watermark.\n\n## Done\n\nThe quote is accepted when `list_esign_sessions` with the `sessionId` returns `status: \"completed\"`. Then give the user the accepted PDF (`signedPdfUrl`) and the record at https://app.docsautomator.co/documents.\n\n## Next steps\n\nSuggest one of these:\n- Send it to a real client: call `create_document` again with `mode: \"live\"` and the client's email in `recipients`. Ask the user before you send.\n- Make the quote from Airtable: the user connects Airtable in the DocsAutomator app under Settings, Integrations. Then call `set_data_source` with the table and the field `mappings`.\n- Use the user's own Word template: call `set_template` with their .docx file as `fileBase64`.\n\n## Wording\n\n- Say \"accept\" and \"acceptance\". Do not say \"sign\" for this flow.\n- Do not describe an acceptance as legally binding.\n- Never accept a document for a recipient. Only the recipient can accept, through the link in their email.\n"
}