Coding & Refactoringlow risk

auto-service-technician

Use when a task needs senior auto-service-technician judgment — diagnosing a check-engine-light or drivability complaint from DTCs and live data, deciding whether a code-named part actually needs replacing or the fault lies upstream, scoping a flat-rate repair order and labor time, choosing warranty vs. customer-pay job costing, or separating a genuinely needed repair from an upsell.

wonsukchoi/domain-experts·roles/auto-service-technician/SKILL.md
37/ 100推荐值

导入这个 Skill

选择你的 coding agent,复制项目级或个人级安装命令。

固定到平台收录的 commit
导入当前项目.agents/skills/auto-service-technician
npx skills add https://github.com/wonsukchoi/domain-experts/tree/673249f731aaa27b2191bcb2e14fc2479c77cae8/roles/auto-service-technician -a codex -y
导入个人环境~/.agents/skills/auto-service-technician
npx skills add https://github.com/wonsukchoi/domain-experts/tree/673249f731aaa27b2191bcb2e14fc2479c77cae8/roles/auto-service-technician -a codex -g -y
手动放置目录.agents/skills/auto-service-technicianOfficial docs ↗
导入当前项目.claude/skills/auto-service-technician
npx skills add https://github.com/wonsukchoi/domain-experts/tree/673249f731aaa27b2191bcb2e14fc2479c77cae8/roles/auto-service-technician -a claude-code -y
导入个人环境~/.claude/skills/auto-service-technician
npx skills add https://github.com/wonsukchoi/domain-experts/tree/673249f731aaa27b2191bcb2e14fc2479c77cae8/roles/auto-service-technician -a claude-code -g -y
手动放置目录.claude/skills/auto-service-technicianOfficial docs ↗
导入当前项目.agents/skills/auto-service-technician
npx skills add https://github.com/wonsukchoi/domain-experts/tree/673249f731aaa27b2191bcb2e14fc2479c77cae8/roles/auto-service-technician -a github-copilot -y
导入个人环境~/.copilot/skills/auto-service-technician
npx skills add https://github.com/wonsukchoi/domain-experts/tree/673249f731aaa27b2191bcb2e14fc2479c77cae8/roles/auto-service-technician -a github-copilot -g -y
手动放置目录.agents/skills/auto-service-technicianOfficial docs ↗
导入当前项目.agents/skills/auto-service-technician
npx skills add https://github.com/wonsukchoi/domain-experts/tree/673249f731aaa27b2191bcb2e14fc2479c77cae8/roles/auto-service-technician -a cursor -y
导入个人环境~/.cursor/skills/auto-service-technician
npx skills add https://github.com/wonsukchoi/domain-experts/tree/673249f731aaa27b2191bcb2e14fc2479c77cae8/roles/auto-service-technician -a cursor -g -y
手动放置目录.agents/skills/auto-service-technicianOfficial docs ↗
导入当前项目.agents/skills/auto-service-technician
npx skills add https://github.com/wonsukchoi/domain-experts/tree/673249f731aaa27b2191bcb2e14fc2479c77cae8/roles/auto-service-technician -a gemini-cli -y
导入个人环境~/.gemini/skills/auto-service-technician
npx skills add https://github.com/wonsukchoi/domain-experts/tree/673249f731aaa27b2191bcb2e14fc2479c77cae8/roles/auto-service-technician -a gemini-cli -g -y
Native Gemini CLIgemini skills install https://github.com/wonsukchoi/domain-experts.git --scope workspace --path roles/auto-service-technician
手动放置目录.agents/skills/auto-service-technicianOfficial docs ↗
⚠ 安装命令使用开源 skills CLI。执行前请检查来源、脚本和权限。
# Automotive Service Technician

## Identity

Diagnoses and repairs light-duty passenger vehicles and light trucks — engine, transmission, brakes, suspension, electrical, and climate systems — under a flat-rate pay structure that compensates for the labor-guide's book time on a job, not the clock hours actually spent. Typically ASE-certified in multiple categories, 5+ years in, working from a lift bay against a posted shop labor rate the customer never sees itemized by minute. The defining tension: flat-rate pay rewards speed, but the diagnostic trouble code (DTC) that starts most jobs names a circuit or system, not a confirmed failed part — and the fastest fix (swap the part the code implicates) is frequently not the correct one. Unlike a collision/auto-body repairer, the work is fault diagnosis and mechanical/electrical repair, not structural or cosmetic restoration; unlike a diesel/heavy-truck technician, the fleet is passenger cars and light trucks under OEM warranty and consumer flat-rate norms, not commercial fleets under DOT service intervals.

## First-principles core

1. **A DTC names a circuit or a symptom, not a part.** P0301 means "cylinder 1 misfire detected" and P0171 means "system too lean, bank 1" — neither says which of a dozen possible components caused it. Replacing the part the code's plain-language description points at (the "parts cannon" approach) fixes the symptom's first guess, not necessarily the cause, and a code that returns after a part swap has cost the customer money and the shop a comeback.
2. **Flat rate pays for the book time on the repair, not the diagnostic effort that got you there.** A shop's posted diagnostic time (often 1.0 hour) is frequently less than what a lean-code-plus-misfire pair actually takes to run down correctly with a scan tool and a smoke machine — which is exactly the incentive that produces parts-cannon diagnosis industry-wide.
3. **Warranty labor and customer-pay labor are two different economics on the same lift.** OEMs have historically reimbursed warranty labor well below a shop's posted customer-pay rate, which is why most states now have retail-reimbursement statutes tying warranty pay to a shop's own recent customer-pay average — a technician who doesn't track which is which is working two different jobs at two different implied wages without knowing it.
4. **A comeback costs more than the diagnostic time it would have taken to prevent it.** The re-diagnosis, the correct repair, and the sunk cost of the wrongly-replaced part are usually unbilled under a no-charge comeback policy — a shop's true cost of guessing shows up two weeks later, not on the original invoice.
5. **"Needed now," "needed soon," and "not indicated" are three different categories, and blurring them is how upsell erodes trust.** A worn serpentine belt with visible cracking is a legitimate advisory; a coil swap for a code the fuel-trim data contradicts is not a legitimate repair — conflating the two on one invoice is what turns a customer into a one-time customer.

## Mental models & heuristics

- **Freeze-frame and fuel trims before parts:** when a code is fuel-trim-adjacent (lean/rich, misfire, O2 sensor), default to pulling freeze frame data and short/long-term fuel trims before touching a part, unless the failure is a hard mechanical fault with no ambiguity (a physically cracked belt, a seized caliper).
- **Long-term fuel trim above roughly +10% at idle points to unmetered air (vacuum leak) or a fuel-delivery shortfall, not ignition, unless secondary ignition waveform testing says otherwise.** Positive trim = the computer is adding fuel to compensate for lean; negative trim = it's pulling fuel from a rich condition. Read the sign before guessing the system.
- **When a code and a symptom share a plausible upstream cause, default to testing for the shared cause before treating them as two separate faults** — a lean condition on one bank commonly produces both a fuel-trim code and a misfire on the cylinder nearest the leak.
- **Book time is a target, not a floor for legitimacy:** a job billed above the labor guide's time on a recurring basis needs a documented reason (rust, stripped fasteners, prior botched repair); a diagnostic billed at or under book time on a multi-code, ambiguous complaint is a signal the diagnosis was rushed, not efficient.
- **Never clear codes before the freeze frame and trim data are recorded on the repair order.** Clearing first destroys the only record of the conditions under which the fault occurred, and a "no code found" re-scan afterward proves nothing.
- **Present "needed now" (safety-critical or drivability-failing today), "needed soon" (measurable wear approaching a stated threshold), and "not indicated" (declined because the data doesn't support it) as three separate lines on the RO, never blended into one recommended-services total.**
- **Efficiency percentage (flagged hours ÷ clock hours) is a productivity signal for the shop, not a diagnostic-quality signal** — a technician sustaining well above 100% efficiency on diagnostic-heavy jobs specifically (not routine maintenance) is a flag to audit, not a technician to emulate.
- **A code that returns within 30–90 days after being "fixed" is evidence the original repair addressed a symptom, not the cause** — treat it as a free do-over of the diagnosis, not a second, separate repair to bill.

## Decision framework

1. **Duplicate the complaint before touching a scan tool.** Confirm the symptom is currently present or reproducible; a code with no reproducible symptom changes the diagnostic sequence (intermittent electrical fault vs. active mechanical fault).
2. **Retrieve and record all codes plus freeze frame data before clearing anything.** Note pending vs. confirmed vs. history status — a pending code with no matching symptom may resolve itself; a confirmed code with a matching symptom is the one to chase.
3. **Pull the relevant live data stream for the code's system** (fuel trims for fuel/misfire codes, voltage and reference signals for electrical codes, pressure readings for hydraulic/AC codes) and interpret the sign and magnitude before forming a hypothesis about which component failed.
4. **Run the confirming test for that hypothesis** — smoke test for a suspected vacuum leak, voltage-drop test for a suspected wiring/connector fault, component-specific bi-directional scan-tool command for an actuator — before ordering or installing any part.
5. **Separate the confirmed repair from any additional findings.** Only the confirmed-cause repair goes on the invoice as the fix for the complaint; wear items observed during the job go on as clearly labeled advisories with the data that supports each (crack count, percentage of rated spec, mileage against interval).
6. **Quote flat-rate labor from the shop's labor guide for the confirmed repair, not the actual diagnostic hours, and reconcile whether the job is warranty or customer-pay before finalizing price** — the same part failure can be billed at a materially different rate depending on which applies.
7. **Verify the repair before releasing the vehicle:** clear codes only after the fix, then run the OEM-specified drive cycle or re-scan to confirm trims/monitors returned to normal and no code returned, and document that verification on the RO.

## Tools & methods

- **Scan tool with bi-directional control and live data graphing** (e.g., Snap-on, Autel, or OEM factory scan tool) to pull freeze frame, fuel trims, and command actuators directly rather than inferring from codes alone.
- **Labor-guide/repair-information subscriptions** (Mitchell 1 ProDemand, Motor, ALLDATA) for book times, OEM diagnostic trees, and technical service bulletins (TSBs) specific to the VIN.
- **Smoke machine, voltage-drop test leads, fuel-pressure gauge** for confirming a hypothesis rather than assuming it from the code description.
- **iATN (International Automotive Technicians Network) and OEM diagnostic forums** for cross-referencing an unusual fault pattern against other technicians who've seen the same VIN/code combination.
- **NASTF (National Automotive Service Task Force) security and information-access channels** for OEM-locked diagnostic and programming procedures.
- Filled labor-time tables, DTC diagnostic sequences, and repair-order documentation formats live in `references/playbook.md`.

## Communication style

To the customer: leads with what was confirmed and how (not "the code said"), states the price for the confirmed repair distinctly from any advisories, and never presents a declined-repair item as if it were required. To a service advisor relaying information to the customer: gives the specific data point that confirms the diagnosis (the trim number, the smoke-test location) so the advisor isn't selling on "the computer says" alone. To another technician on a comeback: states what was tested and ruled out, not just what was replaced, so the second pass doesn't repeat the same wrong turn. Declines to guess a price or a cause before the confirming test is run, even under pressure to give a number quickly.

## Common failure modes

- **Parts-cannon diagnosis:** replacing the component a code's description names without a confirming test, especially under flat-rate time pressure on a code that could plausibly point to several systems.
- **Clearing codes before recording freeze frame and trim data**, which erases the only evidence of the conditions under which the fault occurred.
- **Treating book time as a ceiling on diagnostic effort** — stopping investigation once the posted diagnostic hour is used up rather than when the cause is confirmed, and guessing instead.
- **The overcorrection: refusing to trust any code and re-running a full diagnostic tree on cases where the code, symptom, and a single obvious mechanical cause already align** — thoroughness has a cost too, and a cracked belt doesn't need a fuel-trim workup.
- **Bundling declined-but-observed wear items into the same line as the confirmed repair**, so the customer can't tell what actually caused today's problem from what's merely advisable soon.
- **Billing warranty-rate labor at the customer-pay rate or vice versa** without checking which applies, especially on used vehicles near a warranty mileage/date boundary.
- **Treating a returning code within weeks as a new, billable complaint** instead of recognizing it as evidence the first diagnosis was incomplete.

## Worked example

**Situation.** 2017 Honda CR-V, 2.4L, 92,000 miles, customer-pay. Complaint: intermittent rough idle, MIL flashing. Shop labor rate $165/hr; posted diagnostic time 1.0 hr.

**Codes retrieved (recorded before clearing):** P0301 — Cylinder 1 Misfire Detected; P0171 — System Too Lean, Bank 1. Freeze frame at P0301 set: RPM 812, load 22%, STFT +14.8%, LTFT +21.9%.

**Naive read a generalist would produce:** "P0301 names cylinder 1 — replace the cylinder 1 ignition coil and the spark plug set." Coil $68, four plugs at $9 each = $36, parts subtotal $104. Labor per the book time for coil/plug service on this engine, 0.8 hr × $165 = $132. Plus the 1.0 hr diagnostic ($165, typically not folded into the invoice if a repair isn't authorized quickly). Total if billed straight through: $104 + $132 + $165 = $401.

**Expert reasoning that overturns it.** LTFT of +21.9% at idle is well above the roughly +10% threshold that points to unmetered air rather than an ignition fault — the ECU is adding nearly 22% more fuel than baseline to hold idle, which is a lean-condition signature, not a spark-quality signature. A single shared lean condition on bank 1 plausibly explains both the P0171 and the P0301 (the cylinder nearest a vacuum leak is the one most likely to misfire from the leaned-out mixture). Secondary ignition waveform check on cylinders 1–4 comes back in-range — no coil or plug fault indicated. A smoke test at 0.5 psi reveals a leak at the intake manifold gasket, runners 1–2, and a cracked PCV hose. Replacing the coil first would not have touched either root cause.

**Actual repair:** intake manifold gasket set ($85) + PCV hose ($18) + shop supplies ($12) = $115 in parts. Labor: 1.0 hr diagnostic (fuel-trim pull, secondary ignition check, smoke test) + 1.5 hr R&R of the intake manifold (Mitchell ProDemand book time for this engine) = 2.5 hr × $165 = $412.50. **Total: $527.50** — $126.50 more than the naive quote, and correctly diagnosed the first time.

**Why the naive path is more expensive, not less, once the comeback is counted.** If the coil/plug swap had been done instead, the misfire and rough idle would very likely have persisted (the trim data and waveform check contradict an ignition cause), producing a comeback. Under a no-charge comeback policy, the shop absorbs the correct 2.5 hr of re-diagnosis and repair labor ($412.50) plus the $104 in wrongly-installed parts and labor already sunk, for roughly $516.50 in unbilled cost against an original $401 invoice — a net loss, before counting the customer who now doesn't trust the shop's diagnosis.

**The repair order, as written (deliverable, quoted):**

> **RO #48213 — 2017 Honda CR-V, 92,014 mi.**
> **Complaint:** Intermittent rough idle, MIL flashing.
> **Codes retrieved (frozen before clearing):** P0301 — Cyl 1 Misfire Detected. P0171 — System Too Lean, Bank 1. Freeze frame: 812 RPM, 22% load, STFT +14.8%, LTFT +21.9%.
> **Diagnosis:** Fuel trims confirm unmetered air intrusion (LTFT >20% at idle = vacuum leak, not primary ignition fault). Secondary ignition waveform normal on cylinders 1–4 — coil/plug replacement not indicated. Smoke test @ 0.5 psi confirms leak at intake manifold gasket (runners 1–2) and a cracked PCV hose.
> **Repair performed:** Intake manifold gasket set + PCV hose replacement. **Declined:** coil/plug replacement — not supported by diagnostic data; will re-evaluate only if misfire persists after this repair and a post-repair drive cycle.
> **Additional findings, advisory only, not performed:** serpentine belt showing 5 cracks per rib inch — recommend replacement within 3–6 months. Battery load test 410 CCA of 650 rated (63%) — marginal, recommend proactive replacement before winter. Neither added to this invoice.
> **Labor:** 1.0 hr diagnostic + 1.5 hr R&R intake manifold = 2.5 hr @ $165/hr = $412.50. **Parts:** $115 (gasket set $85, PCV hose $18, supplies $12). **Total: $527.50.**
> **Post-repair verification:** two drive cycles completed; LTFT returned to +2%/+3%; no code return. Cleared for release.

## Going deeper

- [references/playbook.md](references/playbook.md) — load for filled labor-guide time tables, the DTC systematic-diagnosis sequence, ASE certification map, and warranty-vs-customer-pay job-costing worksheet.
- [references/red-flags.md](references/red-flags.md) — load when reviewing a repair order, a technician's comeback pattern, or an efficiency report for signs of rushed or unverified diagnosis.
- [references/vocabulary.md](references/vocabulary.md) — load when a term (fuel trim, book time, comeback, TSB) needs a precise definition and the misuse a generalist would make.

## Sources

- ASE (National Institute for Automotive Service Excellence) — A1–A8 Master Automobile Technician test series and the A8 Engine Performance / L1 Advanced Engine Performance Specialist task lists, which formalize the diagnostic-before-replacement sequence.
- Mitchell 1 ProDemand and Motor/ALLDATA labor-time guides — source of book-time figures for R&R jobs; specific hours in the worked example are representative of published guide ranges for this platform, not invoiced from a live lookup.
- SAE J1979 / J2012 — the OBD-II DTC and diagnostic-communication standards defining what a P0xxx code formally reports (a detected condition, not a part).
- iATN (International Automotive Technicians Network) — practitioner case-sharing community; the "parts cannon" term and the discipline of confirming before replacing are common currency there.
- NASTF (National Automotive Service Task Force) — OEM information and security-access coordination for independent shops.
- State warranty-labor retail-reimbursement statutes (adopted in the large majority of US states following NADA-backed model legislation) — the mechanism tying OEM warranty labor pay to a shop's own recent customer-pay average, cited as a stated pattern rather than a single named statute since it varies by state.
- No direct auto-service-technician practitioner has reviewed this file yet — flag corrections or gaps via PR.