Update to Exayard

{
  "description": "Turn a priced Exayard takeoff into a bid the customer can edit, export and send. Use when the customer asks to make, write or send a bid, quote or proposal for a project.",
  "included_files": [],
  "name": "build-bid",
  "skill_md_contents": "---\nname: build-bid\ndescription: Turn a priced Exayard takeoff into a bid the customer can edit, export and send. Use when the customer asks to make, write or send a bid, quote or proposal for a project.\n---\n\n# Build a bid\n\n## Steps\n\n1. **Find the project.** If the customer says \"this\" or \"the selected\", call `get_selection` first. Otherwise\n   use `list_projects` and `get_project`.\n2. **Check the prices.** Call `get_takeoff_summary`. If the quantities are not priced yet, price them first\n   (`build_priced_boq`). If any line has no price, tell the customer before going on; never invent one.\n3. **Propose the bid.** Call `propose_bid_build` with kind \"bid\", and any notes the customer asked to include.\n   Its card shows **Approve**, and only the customer's press builds the bid. Stop and wait. You never build it\n   yourself.\n4. **Open it.** When the bid is ready, the customer presses **Open** to write, change options, share or export in\n   the bid editor. To read an existing bid, use `list_documents` and `get_document`.\n5. **Export.** For a PDF or Word file, call `export_document` and give the customer the download link.\n6. **Share.** Sharing a bid with a client is done in the bid editor, which asks the customer to confirm. Never\n   share it any other way.\n\n## Rules\n\n- A bid only states quantities and prices the tools returned.\n- If a step is refused because of the account's plan or its AI usage, pass on the message and its link as given,\n  and say nothing more about plans or prices.\n- Plain words to the customer: no record ids and no tool names.\n"
}