Agent skill

auto-repair-estimate-decoder

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.

mohitagw15856github.com/mohitagw15856GitHub ↗
claude-codecursorMIT
Install
npx skills add mohitagw15856/pm-claude-skills --skill auto-repair-estimate-decoder --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 5 KB
Bundled scripts: none
Path: skills/auto-repair-estimate-decoder/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 1,255
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Auto Repair Estimate Decoder 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 from an invoice-in-waiting. It works from the estimate text; it never diagnoses the car. ## What This Skill Produces - A line-by-line decode: what each item is, what it does, what happens if deferred - Urgency triage: safety-now / soon-with-timeframe / eventually / optional-upsell - Sanity checks: labor hours vs. the job's typical shape, parts pricing patterns, diagnostic-fee handling - Ranked red flags and the authorize/decline/second-opinion recommendation per line, plus the questions to ask ## Required Inputs Ask for these only if they aren't already provided: - **The estimate text** — every line with prices; photos of the writeup work. Partial estimates get decoded with the missing pieces named. - **The car and the symptom** — year/make/model/mileage, an

What's inside
Steps it walks through
  1. What This Skill Produces
  2. Required Inputs
  3. Framework: Severity Scale
  4. Output Format
  5. Repair Estimate Decode: [vehicle — shop, date]
  6. Quality Checks
  7. Anti-Patterns
  8. Based On
Ships with 1 file
  • references/worked-example.md
More from pm-claude-skills
All skills →
About this skill
What does the auto-repair-estimate-decoder skill do?

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 do I install it?

Run `npx skills add mohitagw15856/pm-claude-skills --skill auto-repair-estimate-decoder --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From mohitagw15856/pm-claude-skills, a repository with 1,255 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going