Real Estate Listing Trust Scanner

Real Estate Listing Trust Scanner

What it is:

A text-analysis tool that scans real estate listings for marketing spin and likely omissions, then outputs a Trust Score (1–10) and a targeted due diligence checklist.

Who it’s for:

• Property managers reviewing many deals weekly
• Real estate investors
• Serious, high-intent home buyers

Core inputs:

• Full raw listing description and feature list
• Optional: link to photos (for context you describe)
• Location and asking price
• Any specific concerns you already have

Core outputs:

1. Trust Score (1–10): How reliable the listing language appears, based on common omission tactics.
2. Omitted Hazards: Items that are conspicuously missing (e.g., roof age, parking, HOA fees, heating system, foundation, noise factors).
3. Due Diligence Checklist: Tactical, pointed questions to ask the listing agent on the first call.

What it looks for (examples):

• Euphemisms like “cozy,” “TLC,” “priced to sell,” “vibrant/up-and-coming”
• Suspicious pairings like “original features” + no mention of recent updates
• Missing basics: roof age, windows, HVAC, plumbing, electrical, parking, HOA/condo fees, assessments, days on market, prior sale history, flood/fire risk, noise sources

How to use it (workflow):

1. Paste the listing: Include the full description and bullet-point features.
2. Add context: Asking price, location, and any specific worries (e.g., “concerned about structural issues” or “HOA surprises”).
3. Review the Trust Audit:

• Trust Score (1–10)
• List of likely omissions and risk areas
• Custom questions for the agent

1. Call the agent: Use the checklist to push past the marketing language and surface real issues before scheduling a viewing.

Example (from description):

• Input: “Charming Victorian with original windows. Needs some TLC. Priced to sell. Located in a high-growth, up-and-coming area.”
• Output:
• Trust Score: 4/10
• Red Flag: Combination of “original windows” + “TLC” + “priced to sell” suggests major deferred maintenance and poor energy efficiency (potentially $30k+ in near-term work).
• Omission: No mention of roof or foundation.
• Questions:
• “When was the last structural survey performed?”
• “What are the average monthly heating costs with the current windows?”

Best use cases:

• Screening properties that seem too good to be true before you waste time on a viewing
• Portfolio/asset managers triaging dozens of listings weekly
• Training junior staff to spot red flags and missing data in listings

When not to use it:

• New construction (language patterns differ)
• As a replacement for a professional inspection or title search
• Ultra-thin listings with only a sentence or two

Limitations:

• It cannot actually inspect the property or read hidden defects from photos; it only uses the text and whatever you explicitly describe.
• It knows common real estate patterns but not hyper-local zoning or disclosure rules unless you provide them.

Related tools:

• Legal Ops Clause Risk Reviewer: For contract-stage risk review.
• B2B Lead Qualification Scorecard Builder: To rank and compare properties in your investment pipeline.

Use this scanner to cut through listing “charm” and surface the hard questions before you commit time, money, or attention.

Related skills

Skills that pair well, or that you'd reach for instead:

Install

Start with the ZIP package, then choose the AI tool workflow that fits your setup.

1. Download real-estate-listing-trust-scanner.zip ().
2. Open the package and read SKILL.md, plus any included references, templates, or scripts.
3. Use the instructions directly in any AI tool that supports reusable instructions, project knowledge, custom agents, or uploaded reference files.

In Claude, open the command picker with / and select this skill by name when you want to use it.

For Claude Code, unzip into ~/.claude/skills/ so the folder lands at ~/.claude/skills/real-estate-listing-trust-scanner/, then reload Claude Code. For Claude.ai, upload the same ZIP from Customize → Skills.

Use with other AI tools

This package is not locked to one vendor. If your AI tool does not support Claude-style skills, copy the core instructions from SKILL.md into the tool's custom instructions, project prompt, agent setup, or reusable prompt library.

• Upload or paste any included reference files as project knowledge where your tool supports it.
• Keep the output format from SKILL.md intact so results stay predictable.
• Run a small test with your own data before using the workflow in production.

Compatibility depends on the features your AI tool provides. Treat scripts as optional local helpers unless your environment can run them safely.

Claude installation reference