auto-shop-ops
Turn a technician's findings into a printable digital vehicle inspection — feed in the vehicle and an item list with ok/watch/urgent statuses, get a clean HTML report with green/yellow/red badges, tech notes, and print CSS. Comes with a service-interval reminder guide (oil every 5k, rotate every 7.5k) showing how to compute "due in X miles." Use when running an auto repair shop that wants professional inspection reports customers can read.
$ skillbank install auto-shop-ops@1.0.0 # pins exactly 1.0.0 · README + changelog included
Auto Shop Ops
Overview
Customers approve work they understand. A clipboard of checkmarks nobody can read sells nothing; a clean inspection report with green/yellow/red status per item sells the *urgent* work honestly and plants the seed for the *watch* items at the next visit. Auto Shop Ops turns your technician's findings JSON into a printable HTML report — badges, notes, summary counts, print-friendly CSS — ready to hand to the customer or attach to the invoice.
Everything runs on your own machine. The script reads your JSON and writes the HTML file — nothing is uploaded anywhere.
Installation
1. Copy the auto-shop-ops/ directory anywhere convenient. 2. Make the script executable (Unix):
chmod +x scripts/inspection.py
No pip install needed — standard library only.
Configuration
The report reads one JSON file describing the vehicle and the findings:
{
"vehicle": {"year": 2019, "make": "Toyota", "model": "Camry", "mileage": 87500},
"findings": [
{"item": "Engine oil", "status": "urgent", "notes": "Low and dark; change due 5,000 miles ago"},
{"item": "Tire tread", "status": "watch", "notes": "5/32 in, even wear all around"},
{"item": "Brake pads", "status": "ok", "notes": "8mm remaining"}
]
}
vehicle—year,make,model,mileage(all required).findings— one entry per inspected item;statusmust be exactly
ok, watch, or urgent; notes is the technician's plain-language note for the customer.
Status meanings: OK (green) — no action needed. WATCH (yellow) — monitor, plan for the next visit. URGENT (red) — repair recommended now.
Inputs
| Input | Required | Description | |---------------|----------|----------------------------------------------------------| | inspection | yes | JSON file with vehicle and findings (see above). | | --out | yes | Path for the generated HTML report. |
Worked example
$ ./scripts/inspection.py camry-87500.json --out camry-87500-report.html
Wrote camry-87500-report.html (8 items inspected).
Open camry-87500-report.html in a browser (or print it for the customer). An 8-item inspection with 3 OK, 3 watch, and 2 urgent findings renders as a table with green/yellow/red badges, the technician's notes beside each item, and a summary line:
> Summary: 3 OK · 3 watch · 2 urgent
plus a legend ("OK = no action needed · WATCH = monitor at next visit · URGENT = repair recommended now") and a print button that hides itself on paper via print CSS.
Playbooks
- Service-interval reminders — the
mileage math behind "due in X miles" for oil, tires, brakes, and fluids, so your watch items turn into booked return visits.
Safety notes
This is a benign business tool. Vehicle and customer data stays on your machine; the script makes no network calls and never uploads anything. Inspection findings are your technician's professional judgment — the tool formats them, it does not diagnose.
Version history
Changelog
1.0.0 — 2026-09-27
- Initial release:
scripts/inspection.pydigital vehicle inspection - Playbook: service-interval reminder math ("due in X miles").
report generator (findings JSON → printable HTML with ok/watch/urgent badges, tech notes, print CSS).