▮ Automotive AI Skills
Doc /skills/fleet-manager/ENJA

Fleet Manager

English 日本語

An AI skill for managing multiple vehicles — maintenance scheduling across a fleet, cost tracking and TCO analysis, downtime planning, driver check routines, and replacement timing.

Description

The Fleet Manager scales single-vehicle maintenance thinking to fleets of two to two hundred: staggering services so vehicles aren’t all down at once, tracking cost per kilometer to spot problem vehicles, building driver inspection routines that catch faults early, and deciding when repairing stops making sense and replacement begins. It works for delivery vans, company cars, trade utes and trucks, and equally well for a family managing several private vehicles.

Audience: Small business owners and fleet coordinators, tradespeople running work vehicles, and households managing multiple cars.

Capabilities

Example Prompts

I run 5 delivery vans (3 diesel, 2 EV) doing 40,000 km/year each. Build a
maintenance calendar that never has more than one van off the road.
Design a 5-minute daily walk-around checklist my drivers will actually do,
plus a defect report format that reaches me the same day.
Van #3 cost 4x the fleet average in repairs this year. Here's the history:
[paste]. Is this a lemon pattern or bad luck? Repair or replace?
Set up a spreadsheet structure for tracking costs across 8 vehicles that
lets me compare cost-per-km and spot trends. What columns do I need?
Our family runs 3 cars with different ages and mileages. Combine them
into one seasonal maintenance plan with a shared budget forecast.
  1. Inventory the fleet. For each vehicle: year, make, model, fuel type, current mileage, annual mileage, role, and known condition.
  2. State the operational constraints. How many vehicles can be down at once, budget cycle, who does the driving, in-house wrenching capability.
  3. Start with the calendar and the checklist. These two artifacts deliver most of the value fastest.
  4. Feed data back monthly. Update mileages and costs; ask for outlier and trend analysis as history accumulates.
  5. Run repair-vs-replace analysis whenever a vehicle needs a repair exceeding roughly 30–50% of its value — before authorizing the work.
  6. Review annually. Fleet composition, replacement pipeline, and whether the record system is actually being maintained.

Limitations