Agent skill

Inspection Report Decoder

by mohitagw15856 in mohitagw15856/pm-claude-skills

Decode a home inspection report into what's cosmetic, what's expensive, and what kills deals — with repair-cost ranges and the negotiation list.

MITAuto-check passed

Install Inspection Report Decoder

skills CLI
$ npx skills add mohitagw15856/pm-claude-skills --skill inspection-report-decoder -a claude-code

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

GitHub CLI
$ gh skill install mohitagw15856/pm-claude-skills inspection-report-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/inspection-report-decoder .claude/skills/inspection-report-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
inspection-report-decoder
GitHub stars
1.4k
Token cost
~1.1k tokens
SKILL.md length
535 words
Files
2 (incl. references)
Skills in repo
1,348
Repo updated
First seen
Licence
MIT

At a glance

Decode a home inspection report into what's cosmetic, what's expensive, and what kills deals — with repair-cost ranges and the negotiation list.

  • Works in 5 steps: The big five get found first:… → Cost ranges honestly: wide ranges with… → Age vs defect: a 19-year-old roof on a… → …
  • Asked to decode my inspection report
  • SKILL.md covers What This Skill Produces, Required Inputs, Framework and Output Format, plus 3 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Inspection Report Decoder is an agent skill from mohitagw15856/pm-claude-skills. Decode a home inspection report into what's cosmetic, what's expensive, and what kills deals — with repair-cost ranges and the negotiation list. Use when asked to decode my inspection report, is this inspection bad, what should I ask the seller to fix, or should I walk after inspection. Produces a findings triage (walk-risk / negotiate / cosmetic), cost ranges per item, the ask-the-seller list, and the questions for your inspector before the objection deadline.

Its SKILL.md is about 1.1k 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

  • Asked to decode my inspection report
  • Is this inspection bad
  • What should I ask the seller to fix
  • Should I walk after inspection

Example prompts

  • “s cosmetic, what”
  • “/inspection-report-decoder”

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. The big five get found first: foundation/structural movement, roof (age + active leaks), electrical (panel type, aluminum branch wiring)…
  2. Cost ranges honestly: wide ranges with the driver named ("panel replacement: low thousands; if service upgrade needed, more — electrician…
  3. Age vs defect: a 19-year-old roof on a 20-year design life is pricing information, not a defect the seller "hid" — decode which findings…
  4. Negotiate credits over repairs where possible — the seller's rushed contractor is nobody's friend; state the tradeoff.
  5. The deadline governs everything: objection windows are short and expire silently; every recommendation carries the date.

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

Inspection Report Decoder loads about 1.1k tokens when it runs, and up to ~2.7k if it reads all its reference files. Until then it costs about 123 tokens; SKILL.md has 535 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~123
When it runs · the whole SKILL.md, loaded when a task matches
~1.1k
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). 535 words, ~1,134 tokens.

Download SKILL.mdSave it as .claude/skills/inspection-report-decoder/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
inspection-report-decoder
description
Decode a home inspection report into what's cosmetic, what's expensive, and what kills deals — with repair-cost ranges and the negotiation list. Use when asked to decode my inspection report, is this inspection bad, what should I ask the seller to fix, or should I walk after inspection. Produces a findings triage (walk-risk / negotiate / cosmetic), cost ranges per item, the ask-the-seller list, and the questions for your inspector before the objection deadline.

Inspection Report Decoder Skill

Inspection reports bury a $15,000 foundation note between forty comments about caulk — everything is written in the same alarmed font. This skill triages: what threatens the deal, what's a negotiation line, what's Saturday-morning maintenance — with cost ranges, because a finding without a number can't be negotiated.

What This Skill Produces

  • The triage — 🔴 walk-risk / 🟡 negotiate / 🟢 cosmetic-or-maintenance, every finding placed
  • Cost ranges — order-of-magnitude repair estimates per meaningful finding, stated as ranges with the "get a specialist quote" flag where warranted
  • The seller ask-list — repairs vs credits, ranked by leverage, with the deadline noted
  • Inspector follow-ups — the questions to ask while you still can

Required Inputs

Ask for these only if not provided:

  • The report (paste the findings; photos' captions help)
  • The deal context — price, market temperature (multiple offers?), objection/resolution deadline
  • The house basics — age, region (cost ranges and typical failure modes vary), how long you plan to stay
  • Your risk appetite — first home stretched thin vs experienced renovator changes the triage

Framework

  1. The big five get found first: foundation/structural movement, roof (age + active leaks), electrical (panel type, aluminum branch wiring), plumbing (supply material, sewer line), water intrusion/grading. Everything else waits.
  2. Cost ranges honestly: wide ranges with the driver named ("panel replacement: low thousands; if service upgrade needed, more — electrician quote required"). A specialist-quote flag beats a false-precision number.
  3. Age vs defect: a 19-year-old roof on a 20-year design life is pricing information, not a defect the seller "hid" — decode which findings are negotiation-legitimate vs already-in-the-price.
  4. Negotiate credits over repairs where possible — the seller's rushed contractor is nobody's friend; state the tradeoff.
  5. The deadline governs everything: objection windows are short and expire silently; every recommendation carries the date.

Output Format

Show full SKILL.md (249 more words)Show less
Inspection Decode: [address] — objection deadline: [date]

The one-paragraph verdict: proceed / negotiate hard / specialist-inspect before deciding / walk-risk present — and why.

Triage table | Finding (report §) | Plain English | Cost range | Tier |

🚩 The money findings — each: what it is, the realistic range, the driver, specialist-quote flag The seller list — asks ranked by leverage: [credit/repair/price] with suggested wording Ask your inspector — 3–6 questions (verbal answers are often franker than the written report) Budget reality — year-one likely spend if you buy as-is: [range]

End verbatim: "This is a plain-language reading, not a professional inspection, engineering, or legal opinion — cost ranges are regional estimates; get specialist quotes for anything load-bearing before your objection deadline."

Quality Checks

  • Every finding is tiered — none left floating in report-speak
  • Every 🔴/🟡 carries a cost range with its driver named
  • Age-based findings are distinguished from defects
  • The objection deadline appears in the header and the asks
  • The disclaimer appears verbatim

Anti-Patterns

  • Do not mirror the report's flat tone — triage IS the value; forty equal alarms equal zero alarms
  • Do not price findings as points ("$8,500") — ranges with drivers; false precision dies at the first quote
  • Do not treat every finding as seller-negotiable — priced-in aging isn't a gotcha
  • Do not let 🟢 items pad the ask-list — nickel lists cost credibility on the dollar items
  • Do not say walk/don't-walk for them — surface the walk-risks, price the rest, hand the decision back

Example Trigger Phrases

  • "Decode my inspection report."
  • "Is this inspection bad?"
  • "What should I ask the seller to fix?"
  • "Should I walk after inspection?"

© 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/inspection-report-decoder of mohitagw15856/pm-claude-skills.

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

Open the folder on GitHubat commit 1cbf1f0

Compare with similar skills

Inspection Report 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.

Inspection Report Decoder compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Inspection Report Decoder this skillmohitagw15856/pm-claude-skills1.4k—~1.1kAutomated safety check: PassMIT
Node Inspect Debuggeropenclaw/openclaw392k1 repos~894Automated safety check: PassMIT
Blender Motion State Inspectionaffaan-m/ECC276k1 repos~2kAutomated safety check: PassMIT
Speculative DecodingOrchestra-Research/AI-Research-SKILLs13k2 repos~3.5kAutomated safety check: PassMIT
Inspect Diskfelixrieseberg/windows9524k—~1.3kAutomated safety check: PassCustom licence
Inspect AIa2ui-project/a2ui17k1 repos~226Automated safety check: PassApache-2.0

Similar skills

  • Node Inspect Debugger

    openclaw/openclaw

    Debug Node.js with node inspect, --inspect, breakpoints, CDP, heap, and CPU profiles.

    392k GitHub starsUsed in 1 repo~894 tokens
    Frontend & DesignAuto-check passed
  • A skill your agent uses when inspecting Blender characters, rigs, poses, animation retargeting, ground contact, facing direction, or model-vs-motion alignment where screenshots alone are not enough.

    276k GitHub starsUsed in 1 repo~2k tokens
    Game DevelopmentAuto-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
  • Inspect Disk

    felixrieseberg/windows95

    Inspect or modify the Windows 95 disk image offline with mtools — no QEMU, no Electron, no boot.

    24k GitHub stars~1.3k tokensUpdated 28 days ago
    Auto-check passed
  • Inspect AI

    a2ui-project/a2ui

    Useful when working with the Inspect AI evaluation framework (e.g., in the eval/ directory).

    17k GitHub starsUsed in 1 repo~226 tokens
    DevelopmentAuto-check passed
  • Performing Ssl Tls Inspection Configuration

    mukul975/Anthropic-Cybersecurity-Skills

    Configure SSL/TLS break-and-inspect on next-generation firewalls and forward proxies to decrypt, inspect, and re-encrypt HTTPS traffic for malware and exfiltration detection, including deploying…

    34k GitHub stars~2.9k tokensUpdated 1 mo ago
    SecurityAuto-check: notes

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 Inspection Report Decoder

What does Inspection Report Decoder do?

Decode a home inspection report into what's cosmetic, what's expensive, and what kills deals — with repair-cost ranges and the negotiation list. Inspection Report Decoder is an agent skill from mohitagw15856/pm-claude-skills. Decode a home inspection report into what's cosmetic, what's expensive, and what kills deals — with repair-cost ranges and the negotiation list.

When should I use Inspection Report Decoder?

Inspection Report Decoder fits situations like: asked to decode my inspection report; is this inspection bad; what should I ask the seller to fix; should I walk after inspection.

How do I install Inspection Report Decoder in Claude Code?

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

How do I install Inspection Report Decoder in Codex?

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

Can I use Inspection Report 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 inspection-report-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/inspection-report-decoder, .gemini/skills/inspection-report-decoder, .github/skills/inspection-report-decoder and .opencode/skills/inspection-report-decoder in your project.

What does Inspection Report Decoder need to run?

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

Does Inspection Report 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 Inspection Report 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 Inspection Report Decoder use?

Inspection Report 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 Inspection Report Decoder use?

About 1.1k tokens (SKILL.md is roughly 4.5k 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.6k tokens, read only when the agent opens those files.

What are the alternatives to Inspection Report Decoder?

Skills that share tags, products or a category with Inspection Report Decoder: Node Inspect Debugger (openclaw/openclaw, 392k stars), Blender Motion State Inspection (affaan-m/ECC, 276k stars), Speculative Decoding (Orchestra-Research/AI-Research-SKILLs, 13k stars) and Inspect Disk (felixrieseberg/windows95, 24k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Inspection Report Decoder?

mohitagw15856 (a GitHub user) maintains it in mohitagw15856/pm-claude-skills, which has 1,433 GitHub stars. The repository holds 1,348 skills in this directory. The repository was last updated on October 8, 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.