mechanic

20
3
Source

Vehicle maintenance tracker and mechanic advisor. Tracks mileage, service intervals, fuel economy, costs, warranties, and recalls. Researches manufacturer schedules, estimates costs, projects service dates, tracks providers, and proactively reminds about upcoming/overdue services. Supports VIN decode and auto-population of vehicle specs, NHTSA recall monitoring, MPG tracking with anomaly detection, warranty expiration alerts, pre-trip/seasonal checklists, mileage projection, service provider history, tax deduction integration, emergency info cards, and cost-per-mile analysis. Use when discussing vehicle maintenance, oil changes, service intervals, mileage tracking, fuel economy, warranties, recalls, RV maintenance, roof sealing, generator service, slide-outs, winterization, or anything mechanic-related. Supports any vehicle type including trucks, cars, motorcycles, dirt bikes, ATVs, RVs, and boats.

Install

mkdir -p .claude/skills/mechanic && curl -L -o skill.zip "https://mcp.directory/api/skills/download/1847" && unzip -o skill.zip -d .claude/skills/mechanic && rm skill.zip

Installs to .claude/skills/mechanic

About this skill

Mechanic — Vehicle Maintenance Tracker

Track mileage and service intervals for any combination of vehicles — trucks, cars, motorcycles, RVs, dirt bikes, ATVs, boats, and more. Decodes VINs to auto-populate vehicle specs, researches manufacturer-recommended maintenance schedules, tracks service history, estimates costs, monitors recalls, tracks fuel economy, manages warranties, and proactively reminds about upcoming and overdue services.

Data Storage

All user data lives in <workspace>/data/mechanic/:

FilePurpose
state.jsonAll vehicles: current mileage/hours, history, service records, fuel logs, warranties, providers, emergency info
<key>-schedule.jsonPer-vehicle service schedule with intervals and cost estimates

Convention: Skill logic lives in <skill>/, user data lives in <workspace>/data/mechanic/. This keeps data safe when the skill is updated or reinstalled.

First-Time Setup

If <workspace>/data/mechanic/state.json doesn't exist:

  1. Create <workspace>/data/mechanic/ directory
  2. Ask the user what vehicles they want to track
  3. For each vehicle, run the Adding a New Vehicle workflow (includes choosing check-in frequency per vehicle)
  4. Create state.json with the vehicle entries
  5. Set up the cron job (see Mileage Check Setup)

State File Structure

{
  "settings": {
    "check_in_tz": "America/Phoenix"
  },
  "providers": [
    {
      "id": "jims_diesel",
      "name": "Jim's Diesel Repair",
      "location": "123 Main St, Mesa, AZ",
      "phone": "480-555-1234",
      "specialties": ["diesel", "trucks"],
      "rating": 5,
      "notes": "Great with Power Stroke engines"
    }
  ],
  "vehicles": {
    "f350": {
      "label": "2021 Ford F-350 6.7L Power Stroke",
      "schedule_file": "f350-schedule.json",
      "check_in_frequency": "monthly",
      "current_miles": 61450,
      "last_updated": "2026-01-26",
      "last_check_in": "2026-01-26",
      "vin": "1FT8W3BT0MED12345",
      "vin_data": {
        "decoded": true,
        "decoded_date": "2026-01-26",
        "year": 2021,
        "make": "Ford",
        "model": "F-350",
        "trim": "Lariat",
        "body_class": "Pickup",
        "drive_type": "4WD",
        "engine": "6.7L Power Stroke V8 Turbo Diesel",
        "displacement_l": 6.7,
        "cylinders": 8,
        "fuel_type": "Diesel",
        "transmission": "10-Speed Automatic",
        "doors": 4,
        "gvwr_class": "Class 3",
        "bed_length": "8 ft",
        "wheel_base": "176 in",
        "plant_country": "United States",
        "plant_city": "Louisville",
        "raw_response": {}
      },
      "business_use": false,
      "business_use_percent": 0,
      "mileage_history": [
        {"date": "2026-01-26", "miles": 61450, "source": "user_reported"}
      ],
      "service_history": [
        {
          "service_id": "oil_filter",
          "date": "2025-11-15",
          "miles": 58000,
          "hours": null,
          "notes": "Full synthetic Motorcraft FL-2051S",
          "actual_cost": 125.00,
          "provider": {
            "id": "jims_diesel",
            "name": "Jim's Diesel Repair",
            "parts_warranty_months": 12,
            "labor_warranty_months": 6
          }
        }
      ],
      "fuel_history": [
        {
          "date": "2026-01-20",
          "gallons": 32.5,
          "cost": 108.55,
          "odometer": 61300,
          "mpg": 14.2,
          "notes": "Regular fill-up"
        }
      ],
      "warranties": [
        {
          "type": "factory_powertrain",
          "provider": "Ford",
          "start_date": "2021-03-15",
          "end_date": "2026-03-15",
          "start_miles": 0,
          "end_miles": 60000,
          "coverage_details": "Engine, transmission, drivetrain components",
          "status": "active"
        }
      ],
      "recalls": {
        "last_checked": "2026-01-26",
        "open_recalls": [],
        "completed_recalls": []
      },
      "emergency_info": {
        "vin": "1FT8W3BT0MED12345",
        "insurance_provider": "State Farm",
        "policy_number": "SF-123456789",
        "roadside_assistance_phone": "1-800-555-1234",
        "tire_size_front": "275/70R18",
        "tire_size_rear": "275/70R18",
        "tire_pressure_front_psi": 65,
        "tire_pressure_rear_psi": 80,
        "oil_type": "15W-40 CK-4 Full Synthetic",
        "oil_capacity": "15 quarts",
        "coolant_type": "Motorcraft Orange VC-3DIL-B",
        "def_type": "API certified DEF",
        "tow_rating_lbs": 20000,
        "gvwr_lbs": 14000,
        "gcwr_lbs": 37000,
        "key_fob_battery": "CR2450",
        "fuel_type": "Diesel (Ultra Low Sulfur)",
        "fuel_tank_gallons": 48,
        "notes": ""
      }
    }
  },
  "last_service_review": "2026-01-26"
}

Top-level fields:

  • settings — global settings (timezone, etc.)
  • providers — reusable list of service providers
  • vehicles — keyed by short slug (e.g., f350, rv, crf450)
  • last_service_review — date of last full review

Per-vehicle fields:

  • label — human-readable vehicle name
  • schedule_file — path to the service schedule JSON
  • check_in_frequency — how often to ask for mileage (weekly/biweekly/monthly/quarterly)
  • current_miles / current_hours — latest known readings
  • last_updated / last_check_in — date tracking
  • vin — Vehicle Identification Number (for recalls, VIN decode, and emergency info)
  • vin_data — decoded VIN data from NHTSA VPIC API (specs, engine, transmission, etc.)
  • business_use — whether vehicle is used for business (boolean)
  • business_use_percent — percentage of business use (0-100)
  • mileage_history — chronological array of mileage/hours entries
  • service_history — chronological array of completed services (with optional actual_cost and provider)
  • fuel_history — chronological array of fuel fill-ups
  • warranties — array of warranty records
  • recalls — recall monitoring state (last checked, open/completed)
  • emergency_info — quick-reference vehicle specs and emergency contacts

Reading State

On skill load, read:

  1. <workspace>/data/mechanic/state.json — current state for all vehicles
  2. The relevant <key>-schedule.json file(s) depending on what's being discussed

Adding a New Vehicle

When the user wants to track a new vehicle:

1. Gather Vehicle Info

Ask for the VIN first. If the user provides a VIN, run the VIN Decode (see below) to auto-populate year, make, model, engine, transmission, drive type, and other specs. This saves the user from answering questions you can look up automatically.

Ask for:

  • VIN (strongly recommended — auto-populates specs, enables recall monitoring, emergency info)
  • Year, make, model (only ask if no VIN provided)
  • Engine/trim (only ask if no VIN or VIN decode was incomplete)
  • Usage pattern — daily driver, towing, off-road, weekend toy, etc.
  • Current mileage/hours
  • Business use? — if yes, what percentage? (enables tax deduction tracking)
  • Warranty info — any active factory or extended warranties? Expiration date/mileage?
  • Emergency info — insurance provider, roadside assistance number, tire sizes (can be filled in later)

If the user doesn't have the VIN handy, proceed with manual info and note that VIN can be added later to unlock auto-population and recall monitoring.

2. Determine Duty Level

Ask about usage to classify the maintenance schedule:

UsageDuty LevelEffect
Normal commutingNormalStandard intervals
Towing, haulingSevereShorter intervals (typically 50-75% of normal)
Off-road, dusty conditionsSevereShorter intervals, more frequent filter changes
Extreme temps (hot desert, harsh cold)SevereShorter intervals, fluid/battery concerns
Track/racingSevere+Aggressive intervals, specialized fluids
Light use, garage keptNormalStandard intervals, but watch time-based items

Most manufacturers publish both "normal" and "severe/special conditions" schedules. Use the one that matches.

3. Choose Check-In Frequency

Ask how often they want to be asked about this vehicle's mileage/hours:

FrequencyBest for
WeeklyDirt bikes, race vehicles, commercial/fleet, high-mileage daily drivers
Every 2 weeksActive riders/drivers, vehicles with short service intervals
MonthlyMost cars and trucks (recommended default)
QuarterlySeasonal vehicles, low-mileage, garage queens, stored boats

Suggest a frequency based on the vehicle type and usage pattern, but let the user override.

4. Research the Service Schedule

Look up manufacturer-recommended maintenance intervals for that specific year/make/model/engine:

  • Use web search to find the official maintenance schedule
  • Check the owner's manual intervals
  • Cross-reference with enthusiast forums for real-world advice
  • Factor in the duty level from step 2

5. Build the Schedule File

Create <workspace>/data/mechanic/<key>-schedule.json:

{
  "vehicle": {
    "year": 2021,
    "make": "Ford",
    "model": "F-350",
    "type": "truck",
    "engine": "6.7L Power Stroke V8 Turbo Diesel",
    "transmission": "10R140 10-Speed Automatic",
    "duty": "severe",
    "notes": "Tows fifth wheel RV"
  },
  "services": [
    {
      "id": "oil_filter",
      "name": "Engine Oil & Filter Change",
      "interval_miles": 7500,
      "interval_months": 6,
      "details": "Specific oil type, filter part number, capacity, and any special instructions.",
      "priority": "critical",
      "cost_diy": "$XX-XX",
      "cost_shop": "$XX-XX",
      "cost_dealer": "$XX-XX",
      "cost_note": "Optional note about related expensive repairs"
    }
  ]
}

Required for every service item:

  • id — unique snake_case identifier
  • name — human-readable name
  • At least one interval: `i

Content truncated.

You might also like

flutter-development

aj-geddes

Build beautiful cross-platform mobile apps with Flutter and Dart. Covers widgets, state management with Provider/BLoC, navigation, API integration, and material design.

1,5701,369

ui-ux-pro-max

nextlevelbuilder

"UI/UX design intelligence. 50 styles, 21 palettes, 50 font pairings, 20 charts, 8 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, check UI/UX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, mobile app, .html, .tsx, .vue, .svelte. Elements: button, modal, navbar, sidebar, card, table, form, chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, flat design. Topics: color palette, accessibility, animation, layout, typography, font pairing, spacing, hover, shadow, gradient."

1,1161,188

drawio-diagrams-enhanced

jgtolentino

Create professional draw.io (diagrams.net) diagrams in XML format (.drawio files) with integrated PMP/PMBOK methodologies, extensive visual asset libraries, and industry-standard professional templates. Use this skill when users ask to create flowcharts, swimlane diagrams, cross-functional flowcharts, org charts, network diagrams, UML diagrams, BPMN, project management diagrams (WBS, Gantt, PERT, RACI), risk matrices, stakeholder maps, or any other visual diagram in draw.io format. This skill includes access to custom shape libraries for icons, clipart, and professional symbols.

1,4181,109

godot

bfollington

This skill should be used when working on Godot Engine projects. It provides specialized knowledge of Godot's file formats (.gd, .tscn, .tres), architecture patterns (component-based, signal-driven, resource-based), common pitfalls, validation tools, code templates, and CLI workflows. The `godot` command is available for running the game, validating scripts, importing resources, and exporting builds. Use this skill for tasks involving Godot game development, debugging scene/resource files, implementing game systems, or creating new Godot components.

1,193747

nano-banana-pro

garg-aayush

Generate and edit images using Google's Nano Banana Pro (Gemini 3 Pro Image) API. Use when the user asks to generate, create, edit, modify, change, alter, or update images. Also use when user references an existing image file and asks to modify it in any way (e.g., "modify this image", "change the background", "replace X with Y"). Supports both text-to-image generation and image-to-image editing with configurable resolution (1K default, 2K, or 4K for high resolution). DO NOT read the image file first - use this skill directly with the --input-image parameter.

1,153683

pdf-to-markdown

aliceisjustplaying

Convert entire PDF documents to clean, structured Markdown for full context loading. Use this skill when the user wants to extract ALL text from a PDF into context (not grep/search), when discussing or analyzing PDF content in full, when the user mentions "load the whole PDF", "bring the PDF into context", "read the entire PDF", or when partial extraction/grepping would miss important context. This is the preferred method for PDF text extraction over page-by-page or grep approaches.

1,311614

Stay ahead of the MCP ecosystem

Get weekly updates on new skills and servers.