Market report
Compliance guardrails, skills, loops & review agents for US residential real estate agents on Claude Code (Fair Housing + fact-accuracy). Not legal advice.
npx -y skills add m-binimran/real-estate-pack --skill market-reportAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Produce a neighborhood or market update - inventory, median price, days on market, absorption, trend - as a client-ready narrative with sourced stats. Use for farming newsletters, seller updates, or buyer briefings.
SKILL.md
1.4 KB, as published. Nobody here has run it
market-report
Turn real market data into a clear, honest story. Every number needs a source.
Process
- Define the market: geography (zip/neighborhood/city), property type, time window.
- Pull the metrics from a real source (MLS, public records, a named market data provider): active inventory, new listings, closed sales, median/avg sale price, $/sqft, median days on market, months of supply, sale-to-list ratio. Cite the source and date.
- Read the trend: buyer's vs. seller's market (months of supply), price direction, momentum. Be measured - don't overstate.
- Make it useful: what it means for a buyer vs. a seller right now.
Output
- A short narrative + a small stats table, each figure sourced. Headline takeaway in one line.
Guardrails
- No invented or stale numbers - cite the source and as-of date; mark anything you couldn't verify.
- Avoid predictions stated as certainty ("prices will rise") - the
superlativerule. Describe trends, note uncertainty. - Keep neighborhood descriptions factual; no steering proxies ("safe," "good schools" -> link objective data instead).