Update to Meter Drivers & Fleets

{
  "description": "Guide a new fleet owner through Meter fleet setup with the get_onboarding_checklist tool and the settings tools (update_fleet_settings, update_booking_settings, update_ride_option, assign_vehicle), always previewing with dry_run: true and confirming before applying, and knowing when to send them to the web onboarding at meterapp.co/fleet/onboarding instead. Use when someone has just created a fleet, asks what is left to set up, or wants help getting their fleet to its first booking; do not use for day-to-day questions about an established fleet (meter-fleet-insights) or isolated settings edits (meter-settings-changes).",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 473
    }
  ],
  "name": "meter-fleet-onboarding",
  "skill_md_contents": "---\nname: meter-fleet-onboarding\ndescription: \"Guide a new fleet owner through Meter fleet setup with the get_onboarding_checklist tool and the settings tools (update_fleet_settings, update_booking_settings, update_ride_option, assign_vehicle), always previewing with dry_run: true and confirming before applying, and knowing when to send them to the web onboarding at meterapp.co/fleet/onboarding instead. Use when someone has just created a fleet, asks what is left to set up, or wants help getting their fleet to its first booking; do not use for day-to-day questions about an established fleet (meter-fleet-insights) or isolated settings edits (meter-settings-changes).\"\n---\n\n# Onboarding a fleet with Meter\n\nA fleet becomes operational when onboarding is complete and billing is active (`is_operational` in `whoami` and `list_fleets`). Until then, fleet-wide read tools return `fleet_not_operational`, but `get_onboarding_checklist` works on fleets that are still onboarding. This skill turns \"what do I still need to do?\" into a guided checklist that ends with the first booking.\n\n## Start\n\n1. `whoami`. Confirm the person is `owner` (or `admin`) of the fleet. Drivers cannot onboard a fleet; tell them to ask the owner.\n2. `get_onboarding_checklist` with the `fleet_id`. It returns `items` (fleet profile, brand icon, service area, a ride option with a fare, booking settings, a vehicle, a driver, payouts connected as a yes/no, the shareable booking link, the first booking), each saying whether it is done, whether riders can book without it, and how to complete it: the MCP tool to call or the web page to send the human to. It also returns `required_remaining`, `booking_page_status` and the public booking URL. Treat it as the source of truth for what is missing; do not invent steps.\n3. `get_fleet` for the current settings so you can quote them back before changing anything.\n\n## Work through the checklist\n\nFor each incomplete item, in the order the checklist gives:\n\n- Explain the item in one or two sentences in plain language (what it is, why the fleet needs it, whether riders can book without it).\n- Ask for the values you need. Do not fill in defaults the human did not choose, especially fares, cancellation terms and lead times.\n- Call the settings tool the item names with `dry_run: true` and only those fields. `dry_run` defaults to false, so never omit it on the preview call. Show the returned `changes` (each `field`, `from`, `to`) verbatim.\n- Only after an explicit yes, repeat the intended arguments with the saved `proposal_id` and `dry_run: false`. Stale or expired proposals require showing the fresh replacement and asking again. Confirm `status: applied` (a no-op has `applied: false`), then re-run `get_onboarding_checklist` and continue.\n\nNever batch several items into one apply. One item, one confirmation.\n\n## Send them to the web when\n\nSome items cannot be completed through tools and the checklist says so: it names the page instead of a tool. Send the person to `https://www.meterapp.co/fleet/onboarding` (signed in with the same account) for:\n\n- Billing and subscription (payment method, plan) and connecting payouts (the checklist only reports connected yes/no)\n- Uploading the brand icon\n- Creating ride options (the tools edit existing ones) and adding vehicles or inviting drivers\n- Anything involving documents, identity verification or phone number verification\n\nSay exactly which item needs the web and why; do not attempt a workaround through unrelated tools.\n\n## Fares and ride options\n\n`update_ride_option` edits an existing ride option and the rates of its default fare (in major currency units as shown in the console). Changing a fare is a money decision: state `from` and `to` for the base fare, minimum fare, per-distance and per-minute rates with the currency, and require an explicit yes. If the fleet has an official tariff, prefer it; do not guess market rates.\n\n## Vehicles and drivers\n\n- `list_vehicles` shows the fleet's cars; `assign_vehicle` (dry run first) links a vehicle to a driver from `list_fleet_members`, replacing whoever drives it today, or unassigns with `member_id: null`.\n- A fleet needs at least one driver besides the owner to dispatch. Drivers join from the app or the web join link; you cannot add them through tools.\n\n## Finish\n\nWhen `required_remaining` is empty and `booking_page_status` says riders can book, share the booking URL from the checklist, summarize what was set up (with the final values), and suggest the first insight: `list_bookings` for upcoming rides or `get_fleet` to review settings.\n\n## References\n\n- [Tool catalog](../../references/tools.md) (generated)\n- [Data model](../../references/data-model.md) (generated; `OnboardingChecklist`)\n- [Safety](../../references/safety.md)\n"
}