Vertical Real Estate

Residential-proptech domain knowledge so architect / pm aren't naive when speccing real-estate products (listings, lead-crm, transaction-coordination, property-mgmt). Codifies MLS/IDX reality, listing status lifecycle + syndication canonical-source, long-cycle lead nurture, transaction-coordination as the high-pain wedge, and the must-model entities. Applied during spec authoring so the architecture reflects how real estate actually works — not a generic CRUD assumption.

38 stars 11 forksMarketing, Sales & Business

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add jeremybrasher/grokbot-skills --skill vertical-real-estate
Manual install
git clone --depth 1 https://github.com/jeremybrasher/grokbot-skills.git /tmp/grokbot-skills
mkdir -p ~/.claude/skills
cp -r /tmp/grokbot-skills/collections/great-cto/skills/vertical-real-estate ~/.claude/skills/vertical-real-estate

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Vertical: residential real estate — don't spec it naively

Real estate looks like generic CRUD (a listing is a record, a lead is a contact, a deal is
a checklist). It isn't. The domain has hard-won structure — MLS quirks, status lifecycles,
months-long sales cycles, agent-vs-brokerage data boundaries — that a naive build ignores
and then rebuilds. This skill front-loads that structure so the spec is right the first time.

Incumbents to know (and what they own): **Lone Wolf / Propertybase** (brokerage CRM + back
office), **Follow Up Boss** (lead-to-close CRM, the nurture gold standard), **CINC** (lead-gen
+ CRM), **Top Producer** (legacy CRM), **kvCORE / BoldTrail** (all-in-one platform). They are
expensive, broad, and switching-cost-heavy — which is why the wedge matters (see per-product).

## 1. Domain vocabulary (use these terms in the spec)

- **MLS** (Multiple Listing Service) — regional database of listings; there are ~500+ MLSs in
  the US, each its own system, login, and field set. There is no single national MLS.
- **IDX** (Internet Data Exchange) — the rules + feed that let a brokerage display *other*
  brokers' MLS listings on its own site. Governed by per-MLS display/redistribution rules.
- **RESO** — the standards body. **RESO Web API** (modern REST/OData feed) and **RESO Data
  Dictionary** (canonical field names) are the standard — but adoption and cleanliness vary
  per MLS. "RESO-compliant" still means per-MLS quirks.
Read the full skill on GitHub

Details

Skill name
vertical-real-estate
Path
collections/great-cto/skills/vertical-real-estate/SKILL.md
Repo updated
15 September 2026

FAQ

What does the Vertical Real Estate skill do?

Residential-proptech domain knowledge so architect / pm aren't naive when speccing real-estate products (listings, lead-crm, transaction-coordination, property-mgmt). Codifies MLS/IDX reality, listing status lifecycle + syndication canonical-source, long-cycle lead nurture, transaction-coordination as the high-pain wedge, and the must-model entities. Applied during spec authoring so the architecture reflects how real estate actually works — not a generic CRUD assumption.

How do I install the Vertical Real Estate skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add jeremybrasher/grokbot-skills --skill vertical-real-estate. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Vertical Real Estate popular?

It lives in jeremybrasher/grokbot-skills, which has 38 GitHub stars and 11 forks.

Related skills

Anti Patterns

38

jeremybrasher/grokbot-skills

Catalogue of known SDLC anti-patterns that great_cto agents must actively reject when reviewing architecture, plans, code, or post-mortems. Used by architect (pre-impl), pm (planning), senior-dev (impl), l3-support (post-incident).

Software Development11

Anydesign

38

jeremybrasher/grokbot-skills

Analyze images, websites, and Figma files to extract their design and generate a `design.md` with token system, component inventory, and reconstruction notes. Use this skill whenever the user wants to understand, document, replicate, or audit the design of something visual: a screenshot, a URL, a Figma link, a Pinterest reference, a mockup, a competitor's site, a component, a dashboard, a landing page. Also when they ask 'extract the design system from X', 'document the style of Y', 'analyze this visually', 'convert this image into tokens', 'help me replicate this design', 'what palette does t

Frontend & Design11

Archetype Review Base

38

jeremybrasher/grokbot-skills

Shared review framework that every domain reviewer (pci, oracle, gov, edtech, healthcare, mlops, etc.) MUST follow. Defines the output artifact (TM-{slug}.md), mandatory sections, severity scale, verdict format, the workflow scaffold (when-invoked, Step-0 read-inputs, HANDOFF), and the "domain heuristic vs generic check" boundary. Eliminates duplication across the ~30 reviewer prompts.

Finance & Crypto11

Vertical Retail

38

jeremybrasher/grokbot-skills

Retail & e-commerce domain knowledge for SMB storefront products (storefront, inventory, pricing, cart-recovery). Codifies the vocabulary (SKU vs variant, reorder point, COGS/margin, ATS, AOV), the non-obvious rules (Shopify owns the storefront — don't fight it head-on; the wedge is multichannel inventory + reorder and cart recovery), the must-model entities (Product→Variants matrix, channel-aware InventoryLevel, ReorderRule, PricingRule, AbandonedCart), and what a naive build gets wrong (no variant model, single-channel inventory, reorder without lead-time/safety-stock). Applied by architect/

Marketing, Sales & Business11

Vertical Hr Recruiting

38

jeremybrasher/grokbot-skills

Domain-knowledge primer for the HR & recruiting vertical (ATS, onboarding, workforce scheduling, engagement). Applied by architect/pm during spec authoring so they aren't naive about hiring pipelines, the admitted offer→onboard data-carry gap, EEO/I-9 compliance, and shift-coverage rules. Stops the four products from being specced as generic CRUD when the domain has hard legal and workflow constraints.

Marketing, Sales & Business11

Abm Strategy

39

lionelsimai/claude-skills-collection

Design account-based marketing strategies with targeting. TRIGGERS - Use when user needs help with abm-strategy related tasks.

Marketing, Sales & Business

Browse the most popular Claude skills, all marketing, sales & business skills, or write your own with the skills generator.