Update to Otis

{
  "description": "Show the Otis menu and route a user to an independent business workflow when they ask for /otis or need help choosing a task.",
  "included_files": [],
  "name": "menu",
  "skill_md_contents": "---\nname: menu\ndescription: \"Show the Otis menu and route a user to an independent business workflow when they ask for /otis or need help choosing a task.\"\n---\n\n# Otis menu\n\nUse when the user asks for /otis, the Otis menu, or help choosing an Otis task. If a task is already explicit, use its workflow without a menu detour.\n\nCall the connected Otis otis_menu tool and show its numbered choices. Wait for a number, an action name or a natural-language task. Showing the menu does not authorize a write or invoice issuance.\n\nIf Otis is not connected, label this as a navigation preview, show the choices below, and explain how to connect the bundled remote MCP. Sign-in uses an email code in the browser; never ask for the code in chat. Do not invent business records or imply the user is authenticated.\n\n1. Create invoice — workflow: create-invoice\n2. Record work — workflow: record-work\n3. Add expense — workflow: add-expense\n4. Clients — workflow: clients\n5. Invoices — workflow: invoices\n6. Payments — workflow: payments\n7. Business settings — workflow: business-settings\n8. Tax settings — workflow: tax-settings\n9. Export — workflow: export\n\nAfter the user selects a task, use its matching workflow skill or the mapped steps returned by otis_menu. Discover the business and current permissions before accessing records. The public demo is fictional and read-only; these packaged workflow skills target the private connection.\n\nUse the host's actual skill picker or namespace. Do not promise that /otis or a hyphenated alias is installed universally.\n"
}