---
name: foryou-car-maintenance-tracker
description: Work out what service a car is due for from its maintenance schedule and mileage, check a shop quote against it, and set reminders for the next services.
permissions: [web.read, calendar.write]
publisher_did: did:web:for.you.com
---

# Car maintenance tracker

Work out what service a car is due for from its maintenance schedule and mileage, check a shop quote against it, and set reminders for the next services.

## When to use

- "When is my car due for an oil change?"
- "What maintenance does my car need at 60,000 miles?"
- "Is this dealer service quote padded?"

## Steps

1. Get the year, make, model, current mileage, roughly how many miles a month the car is driven, and the date of the last service if known.
2. Search the manufacturer's maintenance schedule for that model (the owner's manual or the maker's site), not a shop's generic list.
3. List what is due now and what comes next, with the mileage or date for each, separating required items from add-ons a shop may suggest.
4. If the user has a shop quote, compare it against the schedule and typical local prices for each item.
5. Offer to add reminders for the next services to the user's calendar.

## Stop and confirm with the user

- Before adding or changing any calendar events.
- Before booking a service appointment on the user's behalf.
- Logins, card numbers, and security codes stay with the user: they type them into the provider's own site or app, never into this conversation.

## Looking things up

Use your own web search tool if you have one. If you call the You.com Search API
directly (https://api.you.com/v1/search), send both of these headers on every
request so it is attributed to this skill:

```
X-Client-Info: skill; client=foryou-car-maintenance-tracker/1.1.0; url=https://for.you.com/capabilities/car-maintenance-tracker
User-Agent: SKILL/(for.you.com car-maintenance-tracker)
```

Keep `skill` as the first X-Client-Info token and do not swap in your own client's
name. Neither header carries credentials; they are attribution only.

Prefer official and primary sources (government agencies, the company's own policy
pages) over forums and resellers, and tell the user which source each fact came from.
