From pm-decoders
Decode an auto repair estimate — what each line actually is, which items are urgent vs upsell, and the questions that separate a fair shop from a fishing expedition. Use when someone asks 'is this repair quote fair', 'decode my mechanic's estimate', 'do I really need all this', or 'is the shop ripping me off'. Produces a line-by-line decode with urgency triage, parts/labor sanity checks, ranked red flags, and the exact questions to ask the shop before authorizing.
How this skill is triggered — by the user, by Claude, or both
Slash command
/pm-decoders:auto-repair-estimate-decoderThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Repair estimates mix three different things on one page: what your car needs now, what it will need eventually, and what the shop would like to sell you this week. This skill separates them — decoding each line into plain language, triaging by "what happens if I don't," and flagging the patterns (fluid-flush bundles, replace-instead-of-repair, labor-hour padding) that distinguish an estimate fr...
Repair estimates mix three different things on one page: what your car needs now, what it will need eventually, and what the shop would like to sell you this week. This skill separates them — decoding each line into plain language, triaging by "what happens if I don't," and flagging the patterns (fluid-flush bundles, replace-instead-of-repair, labor-hour padding) that distinguish an estimate from an invoice-in-waiting. It works from the estimate text; it never diagnoses the car.
Ask for these only if they aren't already provided:
Triage every line by the deferral question: what specifically happens if this isn't done today? Safety items (brakes at spec limits, steering, tires at cords) get named as safety items. "Eventually" items get a mileage/timeframe. Anything the shop can't attach a consequence to is optional by definition. Frame typical-cost comparisons as ranges to verify locally, never as fact — labor rates vary wildly by region.
1. The verdict — total quoted vs. the defensible-now subset, in two sentences.
2. Line-by-line decode
| Line | What it actually is | If you defer it | Urgency | Severity |
|---|
3. 🚩 Red flags, ranked — the quoted line, the pattern it matches, and the question that resolves it.
4. Questions for the shop — 4–6, specific: "What's the measured pad thickness?", "Is the diagnostic fee credited if I authorize?", "Can you show me the old part?", "What's the labor overlap if these are done together?"
5. The authorization plan — authorize now / get the measurement first / decline / second-opinion, per line; and the it's-your-car reminder that declining maintenance is a scheduling decision, not a moral failing.
End the artifact with, verbatim: "This is a plain-language reading, not legal/financial advice — laws vary by jurisdiction; confirm anything load-bearing with a qualified professional."
Consumer-side repair-order review practice — symptom-to-line reconciliation, urgency triage, labor-overlap questioning.
npx claudepluginhub mohitagw15856/pm-claude-skills --plugin pm-decodersGuides collaborative design exploration before implementation: explores context, asks clarifying questions, proposes approaches, and writes a design doc for user approval.
Creates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.
Synthesizes the current conversation into a structured spec (PRD) and publishes it to the project issue tracker with a ready-for-agent label, without interviewing the user.