Update to Meter Drivers & Fleets

{
  "description": "Help an individual Meter driver or rider with their own data through the Meter MCP tools: their trips (list_trips driver \"me\"), bookings (list_bookings scope \"driver\" or \"rider\"), Meter Pay earnings and pay stubs (get_earnings scope \"me\"), and their own profile and availability (whoami, update_my_profile, update_my_availability). Use when the signed-in person asks about \"my trips\", \"my earnings\", \"my schedule\", their past rides or their account; do not use to book, track or cancel a ride as a rider (meter-ride), for fleet-wide questions (meter-fleet-insights) or for fleet settings (meter-settings-changes), which need an owner or admin role.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 489
    }
  ],
  "name": "meter-driver-personal",
  "skill_md_contents": "---\nname: meter-driver-personal\ndescription: \"Help an individual Meter driver or rider with their own data through the Meter MCP tools: their trips (list_trips driver \\\"me\\\"), bookings (list_bookings scope \\\"driver\\\" or \\\"rider\\\"), Meter Pay earnings and pay stubs (get_earnings scope \\\"me\\\"), and their own profile and availability (whoami, update_my_profile, update_my_availability). Use when the signed-in person asks about \\\"my trips\\\", \\\"my earnings\\\", \\\"my schedule\\\", their past rides or their account; do not use to book, track or cancel a ride as a rider (meter-ride), for fleet-wide questions (meter-fleet-insights) or for fleet settings (meter-settings-changes), which need an owner or admin role.\"\n---\n\n# A driver's or rider's own Meter data\n\nMost Meter users are individual drivers (solo or in a fleet) and riders. Their tools work regardless of fleet role and never require an operational fleet. This skill keeps the agent inside that person's own data.\n\n## Start with `whoami`\n\n- `fleets[]`: a driver may belong to one or more fleets; `role: \"driver\"` means fleet-wide tools will refuse. That is expected, not an error to work around.\n- `is_rider: true`: the person has booked rides; `list_bookings` with `scope: \"rider\"` returns them.\n- `profile`: the person's own name, email and phone (never anyone else's).\n\n## Own trips and rides\n\n| Ask | Call |\n| --- | --- |\n| \"My trips this month\" | `list_trips` with `driver: \"me\"`, `start_date`, `end_date`; page with `cursor` |\n| \"How far did I drive / how much did I collect\" | Sum `distance_meters` and `total_minor` over all pages; state the range and currency |\n| \"My upcoming rides\" | `list_bookings` with `scope: \"driver\"`, `after: now`, `sort: \"asc\"` |\n| \"The ride I booked\" (as a rider) | `list_bookings` with `scope: \"rider\"`, then `get_booking` |\n| \"What happened to that booking\" | `get_booking_audit_log` (redacted timeline) |\n\nSolo drivers without a fleet still have trips: `list_trips` with `driver: \"me\"` and no `fleet_id`.\n\n## Earnings and pay stubs\n\n`get_earnings` with `scope: \"me\"` returns Meter Pay payouts (card payments transferred to the person's bank account) per currency, with a `day` or `week` series. It does **not** include cash fares. For a pay-stub style summary:\n\n1. Call `get_earnings` for the pay period (`start_date` inclusive, `end_date` exclusive), `granularity: \"week\"`.\n2. Call `list_trips` with `driver: \"me\"` for the same period and total trips, distance, fares and tips by payment method.\n3. Present: period, trip count, gross fares, tips, card payouts (from earnings), cash collected (from trips with a cash payment method), currency, and the fleet's payout fraction if the person is in a fleet (`get_fleet` shows it to admins only; otherwise say it is set by the fleet).\n\nLabel every figure with its source tool. Do not present the result as an official tax document.\n\n## Profile and availability\n\n`update_my_profile` (name, business name on receipts, navigation app, receipt privacy options with Meter Pro) and `update_my_availability` (the weekly hours riders may book the driver for; the whole week is replaced, so include every working day) change only the signed-in person's own record. Follow the dry-run sequence from `meter-settings-changes`: call with `dry_run: true` first, save the returned proposal, show every `changes` row (`field`, `from`, `to`), get an explicit yes, then repeat the intended arguments with `proposal_id` and `dry_run: false`. Stale or expired proposals require showing the fresh replacement and asking again. Email, phone, role and payout details are managed in the Meter app, not here.\n\n## What this skill does not do\n\n- It does not look at other drivers. `list_fleet_members`, `driver: \"all\"` and `scope: \"fleet\"` are owner/admin tools; a `forbidden` error confirms the person is a driver.\n- It does not guess ids. Trip and booking ids come from the list tools.\n- It does not change fares, fleet settings or bookings.\n- It does not book, track or cancel a ride as a rider; `meter-ride` does, with its own preview and confirmation.\n\n## References\n\n- [Tool catalog](../../references/tools.md) (generated)\n- [Data model](../../references/data-model.md) (generated; `Trip`, `Booking`, `EarningsSummary`)\n"
}