---
name: al-323-prep-a-buyer-s-saturday-showings-in-minutes-have-an-ai-br
description: "A buyer sends six homes to tour and you face six listings to open, six sets of showing instructions to copy and six listing agents to track down. An Austin agent signs in to his MLS himself, then lets Claude in Chrome open each listing and fill one table with the showing instructions and how each listing agent wants showings booked, writing \"not found\" instead of guessing. You still book every showing and send every message yourself. Use when the user wants help with real estate (sales) for a small business."
---

# Prep a buyer's Saturday showings in minutes: have an AI browser agent pull each listing's showing instructions from your MLS into one table

A buyer sends six homes to tour and you face six listings to open, six sets of showing instructions to copy and six listing agents to track down. An Austin agent signs in to his MLS himself, then lets Claude in Chrome open each listing and fill one table with the showing instructions and how each listing agent wants showings booked, writing "not found" instead of guessing. You still book every showing and send every message yourself.

## Inputs to collect first
Ask the user for anything below that they haven't already given you. Don't guess missing facts.

- MLS numbers or addresses
- Your own material (text, notes or data)

## Instructions

Do the task below with the user's inputs in place of each [bracket].

I'm a buyer's agent. I'm signed in to my MLS in this browser. My buyer wants to see these homes on [day]: [paste MLS numbers or addresses]. Open each listing one at a time and build me a table with: address, MLS number, list price, status, showing instructions (copied word for word), how the listing agent wants showings booked (showing service, text, call or email), listing agent name and phone, lockbox or access notes, and any restrictions (notice needed, pets, tenant-occupied, time windows). Rules: never invent a fact. If a field isn't in the MLS data, write "not found". Don't book anything, don't message anyone and don't change anything in the MLS. When done, suggest a showing order that fits the time windows, and list which homes need a call or text from me first. Before using this, check that your MLS rules allow this kind of assisted browsing.

## Safety checks (share these with the user)

- Check every figure, price and total against your own records before anything is sent, posted or booked. A person approves refunds, discounts, payments and price changes.
- Remove names, contact details, account numbers and other personal data the task doesn't need before you paste, and check your AI tool's data and training settings.
- Read and edit the draft before it reaches a customer or goes public. If you later automate this prompt, start with "draft and notify me", not "send automatically".
- Check names, dates, numbers and any claim against your own source material before you use the answer. AI can misread or invent details.
- Say clearly which parts need a person to review or approve before anything is sent, paid, posted or filed.

## About this skill

- Works with: Claude in Chrome, ChatGPT agent, your MLS
- Based on this real-world example: https://realestateusecases.com/u/showing-instructions-from-mls-claude-chrome/
- Free prompt from AgentPlaybook Real Estate: https://agentic-library.netlify.app/prompt/al-323-prep-a-buyer-s-saturday-showings-in-minutes-have-an-ai-brows/
- To install in an agent that supports Agent Skills, save this file as SKILL.md in a folder with the same name as `name` above (for example in your skills directory). Install steps for Claude.ai, Claude Code, Cursor and Codex: https://agentic-library.netlify.app/skills/