New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Auto Repair Estimate Decoder

by mohitagw15856 in mohitagw15856/pm-claude-skills

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.

MITAuto-check passed

Install Auto Repair Estimate Decoder

skills CLI
$ npx skills add mohitagw15856/pm-claude-skills --skill auto-repair-estimate-decoder -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install mohitagw15856/pm-claude-skills auto-repair-estimate-decoder --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/auto-repair-estimate-decoder .claude/skills/auto-repair-estimate-decoder && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
auto-repair-estimate-decoder
GitHub stars
1.4k
Token cost
~1.4k tokens
SKILL.md length
736 words
Files
2 (incl. references)
Skills in repo
1,348
Repo updated
First seen
Licence
MIT

At a glance

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.

  • Someone asks is this repair quote fair
  • SKILL.md covers What This Skill Produces, Required Inputs, Framework: Severity Scale and Output Format, plus 4 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
  • Decode my mechanics estimate

What it does

Auto Repair Estimate Decoder is an agent skill from mohitagw15856/pm-claude-skills. 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.

Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/worked-example.md`).

The repository describes itself as: 1255 professional Agent Skills for Claude, ChatGPT, Gemini, Cursor & Codex — PRDs, postmortems, leases, medical bills, layoffs, go-bags, new countries. Plain markdown, MIT, in… The licence is MIT.

When your agent uses it

  • Someone asks is this repair quote fair
  • Decode my mechanics estimate
  • Do I really need all this
  • Is the shop ripping me off

Example prompts

  • “is this repair quote fair”
  • “decode my mechanic”
  • “do I really need all this”
  • “/auto-repair-estimate-decoder”

What it can do on your machine

Read from SKILL.md and the folder at commit 1cbf1f0. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Auto Repair Estimate Decoder loads about 1.4k tokens when it runs, and up to ~2.7k if it reads all its reference files. Until then it costs about 124 tokens; SKILL.md has 736 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~124
When it runs · the whole SKILL.md, loaded when a task matches
~1.4k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~2.7k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from mohitagw15856/pm-claude-skills at commit 1cbf1f0, republished under its MIT licence (© mohitagw15856). 736 words, ~1,442 tokens.

Download SKILL.mdSave it as .claude/skills/auto-repair-estimate-decoder/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
auto-repair-estimate-decoder
description
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.

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, and what brought it in (the estimate should connect to the symptom; lines that don't are the interesting ones).
  • Context — how long they plan to keep the car, and whether this shop has history with them.

Framework: Severity Scale

  • 🔴 Challenge before authorizing — repairs unrelated to the presenting symptom appearing without explanation, "replace" where "repair/resurface" is standard practice for the condition described, fluid-flush bundles on intervals far shorter than typical service schedules, labor hours that imply the job twice ("remove and replace" charged for overlapping operations), vague lines ("front end work") with specific prices, diagnostic fees charged and not credited toward authorized work (shop-dependent — ask).
  • 🟡 Verify — reasonable questions to ask — OEM vs. aftermarket parts pricing unstated, "while we're in there" additions (sometimes genuinely economical — labor overlap is real; make them show the overlap math), preventive recommendations stated without the wear measurement that justifies them ("brakes at 4mm" is information; "brakes soon" is a mood).
  • 🟢 Looks standard — lines that match the symptom, itemized parts+labor, wear items at plausible mileage; say so — most shops are honest, and knowing which lines are fine is half the value.

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.

Output Format

Show full SKILL.md (318 more words)Show less
Repair Estimate Decode: [vehicle — shop, date]

1. The verdict — total quoted vs. the defensible-now subset, in two sentences.

2. Line-by-line decode

LineWhat it actually isIf you defer itUrgencySeverity

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."

Quality Checks

  • Every line gets a deferral consequence or is labeled optional
  • Safety-critical items are named as such and never bundled with upsell critique
  • Cost comparisons are framed as verify-locally ranges, not asserted facts
  • Lines unrelated to the presenting symptom are flagged for explanation, not assumed fraudulent
  • The questions are specific enough that a shop's answers are checkable
  • The disclaimer line appears verbatim in the artifact

Anti-Patterns

  • Do not diagnose the vehicle — decode the estimate; the car itself is the mechanic's domain
  • Do not treat every recommendation as a scam — wear items exist; the triage is the value, not the cynicism
  • Do not soften a genuine red flag — double-charged labor is double-charged labor
  • Do not invent typical prices as fact — regional labor rates make national numbers fiction
  • Do not let safety items get deferred silently — if brakes are at spec limits, that line leads

Based On

Consumer-side repair-order review practice — symptom-to-line reconciliation, urgency triage, labor-overlap questioning.

Example Trigger Phrases

  • "Is this repair quote fair?"
  • "Decode my mechanic's estimate."
  • "Do I really need all this?"
  • "Is the shop ripping me off?"

© mohitagw15856, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file (references) in skills/auto-repair-estimate-decoder of mohitagw15856/pm-claude-skills.

  • SKILL.md
  • references/worked-example.md

Open the folder on GitHubat commit 1cbf1f0

Compare with similar skills

Auto Repair Estimate Decoder next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Auto Repair Estimate Decoder compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Auto Repair Estimate Decoder this skillmohitagw15856/pm-claude-skills1.4k—~1.4kAutomated safety check: PassMIT
Openclaw Repair Sweepopenclaw/openclaw392k—~1.8kAutomated safety check: PassMIT
TDD Repairruvnet/ruflo74k—~1.6kAutomated safety check: NotesMIT
Task Effort EstimatorDonchitos/Claude-Code-Game-Studios26k—~1.2kAutomated safety check: PassMIT
Progressive Estimationsickn33/agentic-awesome-skills47k2 repos~863Automated safety check: PassMIT
Speculative DecodingOrchestra-Research/AI-Research-SKILLs13k2 repos~3.5kAutomated safety check: PassMIT

Similar skills

  • Openclaw Repair Sweep

    openclaw/openclaw

    Run scoped OpenClaw issue/PR repair campaigns: coordinate workers, prove root causes, and land or close verified work under the requested authority.

    392k GitHub stars~1.8k tokensUpdated today
    DevelopmentAuto-check passed

  • TDD Repair

    ruvnet/ruflo

    Test-Driven Repair — given a failing test, spawn a bounded headless claude -p (Read/Edit/Bash only) that makes the test pass without modifying it.

    74k GitHub stars~1.6k tokensUpdated today
    Testing & QAAuto-check: notes

  • Task Effort Estimator

    Donchitos/Claude-Code-Game-Studios

    Estimates the effort for a game development task from code complexity, scope, risk and past sprint data, returning a range with a confidence level.

    26k GitHub stars~1.2k tokensUpdated 2 days ago
    Product & Project ManagementAuto-check passed

  • Progressive Estimation

    sickn33/agentic-awesome-skills

    Estimate AI-assisted and hybrid human+agent development work with research-backed PERT statistics and calibration feedback loops

    47k GitHub starsUsed in 2 repos~863 tokens
    Data & AnalyticsAuto-check passed

  • Speculative Decoding

    Orchestra-Research/AI-Research-SKILLs

    Explains three ways to speed up LLM inference: draft-model speculative decoding, Medusa heads and lookahead decoding with Jacobi iteration, and when each one fits.

    13k GitHub starsUsed in 2 repos~3.5k tokens
    AI & LLM EngineeringAuto-check passed

  • DB Repair

    garrytan/gbrain

    Auto-fix gbrain's Postgres access so the brain stays available.

    31k GitHub stars~1.5k tokensUpdated today
    Agent WorkflowsAuto-check passed

More from mohitagw15856/pm-claude-skills

All 1,348 skills in this repo

  • Car Tco

    mohitagw15856/pm-claude-skills

    Compare the total cost of car ownership across buy-new, buy-used, lease, and keep-your-current-car — depreciation, insurance, maintenance ramp, and fuel over a real horizon, not just the monthly…

    1.4k GitHub stars~1.1k tokensUpdated yesterday
    Auto-check passed

  • Cs Health Scorecard

    mohitagw15856/pm-claude-skills

    Build a customer health scorecard for a specific account. An agent skill from mohitagw15856/pm-claude-skills.

    1.4k GitHub stars~2.4k tokensUpdated yesterday
    Auto-check passed

  • Exit Waterfall

    mohitagw15856/pm-claude-skills

    Compute who gets what at each exit price from a cap table — liquidation preferences, conversion points, and where the founders' share collapses.

    1.4k GitHub stars~1.1k tokensUpdated yesterday
    Auto-check passed

  • Feature Prioritisation

    mohitagw15856/pm-claude-skills

    Apply prioritisation frameworks (RICE, MoSCoW, Kano, ICE, Opportunity Scoring) to rank features and backlog items.

    1.4k GitHub stars~2k tokensUpdated yesterday
    Auto-check passed

  • Fire Number

    mohitagw15856/pm-claude-skills

    Compute a financial-independence (FIRE) target and years-to-reach with every assumption labeled as an assumption — plus a sensitivity table instead of a single false-precision answer.

    1.4k GitHub stars~1.1k tokensUpdated yesterday
    Auto-check passed

  • Freelance Rate

    mohitagw15856/pm-claude-skills

    Derive a freelance day/hourly rate backwards from target income, honest billable utilization, overhead, and the self-employment tax premium — the arithmetic that proves a rate is not salary÷2000.

    1.4k GitHub stars~1.2k tokensUpdated yesterday
    Auto-check passed

Questions about Auto Repair Estimate Decoder

What does Auto Repair Estimate Decoder 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. Auto Repair Estimate Decoder is an agent skill from mohitagw15856/pm-claude-skills. 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.

When should I use Auto Repair Estimate Decoder?

Auto Repair Estimate Decoder fits situations like: someone asks is this repair quote fair; decode my mechanics estimate; do I really need all this; is the shop ripping me off.

How do I install Auto Repair Estimate Decoder in Claude Code?

Run `npx skills add mohitagw15856/pm-claude-skills --skill auto-repair-estimate-decoder -a claude-code`. Or copy the skill folder (skills/auto-repair-estimate-decoder in mohitagw15856/pm-claude-skills) into .claude/skills/auto-repair-estimate-decoder in your project. Claude Code loads it when a task matches its description.

How do I install Auto Repair Estimate Decoder in Codex?

Run `npx skills add mohitagw15856/pm-claude-skills --skill auto-repair-estimate-decoder -a codex`. Or copy the skill folder (skills/auto-repair-estimate-decoder in mohitagw15856/pm-claude-skills) into .agents/skills/auto-repair-estimate-decoder in your project. Codex loads it when a task matches its description.

Can I use Auto Repair Estimate Decoder in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mohitagw15856/pm-claude-skills --skill auto-repair-estimate-decoder -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/auto-repair-estimate-decoder, .gemini/skills/auto-repair-estimate-decoder, .github/skills/auto-repair-estimate-decoder and .opencode/skills/auto-repair-estimate-decoder in your project.

What does Auto Repair Estimate Decoder need to run?

SKILL.md names no scripts, command-line tools or credentials: Auto Repair Estimate Decoder is instructions for the agent only.

Does Auto Repair Estimate Decoder access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Auto Repair Estimate Decoder safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Auto Repair Estimate Decoder use?

Auto Repair Estimate Decoder is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Auto Repair Estimate Decoder use?

About 1.4k tokens (SKILL.md is roughly 5.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.3k tokens, read only when the agent opens those files.

What are the alternatives to Auto Repair Estimate Decoder?

Skills that share tags, products or a category with Auto Repair Estimate Decoder: Openclaw Repair Sweep (openclaw/openclaw, 392k stars), TDD Repair (ruvnet/ruflo, 74k stars), Task Effort Estimator (Donchitos/Claude-Code-Game-Studios, 26k stars) and Progressive Estimation (sickn33/agentic-awesome-skills, 47k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Auto Repair Estimate Decoder?

mohitagw15856 (a GitHub user) maintains it in mohitagw15856/pm-claude-skills, which has 1,434 GitHub stars. The repository holds 1,348 skills in this directory. The repository was last updated on October 9, 2026.

Source: mohitagw15856/pm-claude-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.