{"id":90094,"plugin_id":"plugin_asdk_app_6adff0c4ea78819192c2da795f3a258f","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-11-11T00:09:19.937Z","digest":"f15d1a709872d763ae7b84fcec4557acb1dd5424e05e91c69058f58d210b70fe","against":null,"payload":{"description":"Answer questions about a Meter fleet's trips, bookings, drivers, vehicles, earnings and accounting using the Meter MCP tools (whoami, list_trips, list_bookings, list_fleet_members, list_vehicles, get_earnings, get_accounting_summary). Covers picking the right tool, role limits, pagination and presenting money and times correctly. Use for any \"how many / how much / who / which / when\" question about a fleet; do not use for changing settings (meter-settings-changes), setting up a new fleet (meter-fleet-onboarding), an individual driver's own data (meter-driver-personal), booking a ride as a rider (meter-ride), or explaining the API itself (meter-api-explainer).","included_files":[{"relative_path":"agents/openai.yaml","size_in_bytes":536}],"name":"meter-fleet-insights","skill_md_contents":"---\nname: meter-fleet-insights\ndescription: \"Answer questions about a Meter fleet's trips, bookings, drivers, vehicles, earnings and accounting using the Meter MCP tools (whoami, list_trips, list_bookings, list_fleet_members, list_vehicles, get_earnings, get_accounting_summary). Covers picking the right tool, role limits, pagination and presenting money and times correctly. Use for any \\\"how many / how much / who / which / when\\\" question about a fleet; do not use for changing settings (meter-settings-changes), setting up a new fleet (meter-fleet-onboarding), an individual driver's own data (meter-driver-personal), booking a ride as a rider (meter-ride), or explaining the API itself (meter-api-explainer).\"\n---\n\n# Fleet insights with Meter\n\nThe Meter MCP server at `https://www.meterapp.co/api/mcp/fleet` returns the data the signed-in person already sees in the Meter apps. Owners and admins see the whole fleet; drivers see only themselves. Nothing in this skill changes data.\n\n## Always start with `whoami`\n\nCall `whoami` once per session. It returns:\n\n- `fleets[]` with `fleet_id`, `role` (`owner`, `admin`, `driver`) and `is_operational`\n- `default_fleet_id` when the person belongs to exactly one fleet (then `fleet_id` may be omitted everywhere)\n- `suggested_next_tools`\n\nIf there are several fleets and the question does not name one, ask which fleet before calling anything else. Never construct a `fleet_id`.\n\n## Pick the right tool\n\n| Question | Tool | Notes |\n| --- | --- | --- |\n| Who is in the fleet, which drivers exist | `list_fleet_members` | owners/admins only; `member_id` feeds `list_trips` |\n| Which cars, who drives which | `list_vehicles` | `assigned_driver` is admin-only |\n| Completed metered rides, revenue per trip, tips | `list_trips` | `driver: \"all\"` (admins) or a `member_id`; filter with `start_date`/`end_date` |\n| One trip in detail | `get_trip` | id from `list_trips` |\n| Scheduled and on-demand rides, what is unassigned | `list_bookings` | `scope: \"fleet\"` for admins; filter by `status`, `after`, `before` |\n| What happened to a booking and when | `get_booking_audit_log` | redacted timeline; roles, never names |\n| Card payouts to bank accounts | `get_earnings` | `scope: \"fleet\"`, `include_members: true` for a per-driver split |\n| Full ledger: cash, card, unpaid, balances between fleet and drivers | `get_accounting_summary` | owners/admins of an operational fleet |\n| Fleet settings, ride options, service zones | `get_fleet` | admins also get booking and payout settings |\n| How far a new fleet is from its first booking | `get_onboarding_checklist` | owners/admins; works before the fleet is operational (see `meter-fleet-onboarding`) |\n\n`get_earnings` counts only Meter Pay card payouts. For \"how much did the fleet make\" including cash, use `get_accounting_summary`. Say which one you used.\n\n## Pagination and time ranges\n\n- Lists return `items` and `next_cursor`. Pass `cursor` back until it is null; keep `limit` at or below 100. For totals over a period, page through everything or use the summary tools instead of stopping early.\n- `start_date`/`end_date` (trips, earnings, accounting) and `after`/`before` (bookings) take ISO 8601 dates. Interpret \"last week\" in the fleet's timezone (`get_fleet` or `list_fleets` return `timezone`), and state the range you used.\n- Trips are metered rides that happened. Bookings are scheduled rides, some of which become trips (`trip_id` on the booking once completed). Do not add them together.\n\n## Present numbers correctly\n\n- Money fields end in `_minor` and are in the currency's minor unit: divide by 100 for USD, EUR, GBP and most currencies (JPY and a few others have no minor unit). Show the currency code from the result.\n- Distances are meters, durations are seconds, timestamps are ISO 8601. Convert for the human and keep the fleet timezone.\n- When a field's meaning is unclear, call `explain_data` with the tool and field name rather than guessing.\n\n## Role limits are final\n\nA `forbidden` error means the person's role does not allow that view. Do not retry with other ids or arguments. Drivers can still get their own data: `list_trips` with `driver: \"me\"`, `list_bookings` with `scope: \"driver\"`, `get_earnings` with `scope: \"me\"`. A `fleet_not_operational` error means fleet-wide data is unavailable until onboarding and billing are complete; own-data tools still work.\n\n## Privacy\n\nResults already exclude payment-provider ids, GPS traces, internal notes and other people's contact details beyond what the role allows. Do not infer them, and do not compile per-person profiles the human did not ask for. Rider contact details appear only where the role permits; treat them as confidential.\n\n## References\n\n- [Tool catalog](../../references/tools.md) (generated)\n- [Data model](../../references/data-model.md) (generated)\n- [Safety](../../references/safety.md)\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}