Claude Skills for Real Estate Agents: Automate Seller Updates and Listing Descriptions

The seller email you keep putting off

Every agent with a pile of listings knows the pattern. A seller has not heard from you in three weeks, you know the listing has had two showings and no offers, and writing the honest version of that email takes 20 minutes you do not have. So you do not write it, the seller starts to wonder what you do all day, and the price conversation gets harder.

A North Texas land agent documented on this site, Jason Northcutt, solved this for 60 plus active listings with two reusable Claude Skills (builtwithagents.ai/strategy/claude-skills-real-estate-seller-listing-updates). Every listing gets a seller update on a two-week cadence, and every new listing gets three channel-specific descriptions from a single input. He does not publish time saved or revenue figures, and he is clear that the Skills assist him rather than run on their own. His rule is that the Skill should capture your process, not invent one. This guide shows how to build the same pair.

What a Skill is, and why it beats a saved prompt

A Skill is a folder with a file called SKILL.md. The top of the file has a name and a description, and below that are your instructions: how you think, how you write, what the output looks like. Claude reads only the short name and description up front, and loads the full instructions when your request matches. So you stop pasting the same 400 words of context into every chat.

Two practical notes from Anthropic's documentation. The name can only use lowercase letters, numbers and hyphens, and it cannot include the word claude. And the description should say both what the Skill does and when to use it, because that is what Claude matches your request against. Custom Skills on claude.ai belong to your account alone, so they do not sync to a team or to the API.

What this costs

As of November 2026, Claude Pro is listed at $20 a month billed monthly, or $17 a month on an annual plan, and Max starts at $100 a month. Anthropic's help pages say Skills are available across consumer plans and require the code execution and file creation setting to be turned on, while its developer documentation lists custom Skills on Pro and above, so plan on Pro to be safe. Northcutt notes in his write-up that Skills work on the standard subscription. The Skills themselves cost nothing extra.

Your real cost is the hour or two to set them up and the minutes you spend checking each draft. A Skill drafts. You still own the numbers and the advice.

Step by step

Step 1: Write down your own process first

Open a blank note and answer four questions for the seller update: what numbers do you share (showings, days on market, online views, inquiries), how do you judge whether a listing is on track, what do you recommend at each level, and how do you sound? Paste in three real seller emails you are proud of. Do the same for listing descriptions: what do buyers in your market care about, and what do you never say? Land buyers want access, water, taxes and usable acreage. Condo buyers want HOA fees and parking. Your Skill is only as good as this note.

Step 2: Turn on the setting and ask Claude to draft the Skill

In Claude, go to Settings, then Capabilities, and enable code execution and file creation. Then start a chat and tell Claude you want to build a Skill for your seller updates. Paste your note and ask it to interview you about anything unclear, then produce the Skill as a folder with a SKILL.md file. Northcutt built his by talking it through rather than writing code. Anthropic's current docs describe uploading a zip of the Skill folder under Customize, then Skills, so you may end up downloading Claude's output and uploading it. Menu names change, so follow what the Help Center shows today.

Step 3: Give the seller update Skill a traffic light

The most stealable idea from the case study is a Green, Yellow, Red framework. Write rules like these into the Skill, using your own numbers. Green: showings are on pace with similar listings and feedback is positive, so the message is "stay the course." Yellow: decent traffic but no offers, so the message is "price and presentation tweaks worth discussing." Red: little traffic after a set number of weeks, so the message is "we need to talk about price." The Skill should always quote the real numbers you gave it and end with one clear recommendation. Tell it never to invent a number you did not provide.

Step 4: Feed it real metrics every two weeks

Each cycle, paste in the listing address, days on market, showings since the last update, any buyer feedback and your own note. A 10-line input is plenty. Ask for the email. Claude classifies the listing, drafts the message in your voice and cites your numbers. Read it against your data, change the one sentence that sounds off, and send from your own email.

Step 5: Build the description Skill with three outputs

Create a second Skill that takes property facts once and returns three versions: an MLS description with whatever length and abbreviation rules your board uses, a version written for Zillow, and a version for Google. Northcutt wrote his for rural land buyers rather than generic residential copy. Add to the instructions a list of banned phrases, a rule that it only uses facts you supply, and a reminder to stay inside fair housing language. Never let a Skill describe the neighborhood's people.

Step 6: Test on three old listings

Run both Skills on listings you already know well. Check every claim. If the description says something you did not provide, add a line to the Skill forbidding it. If the seller email is too soft on a stale listing, add a harder example. Expect two or three rounds before it sounds right.

Step 7: Put it on a calendar

A Skill does nothing on its own. Set a recurring reminder every second Monday to run the update across your active listings. Sixty listings at two minutes each is two hours, which is the whole point: the writing stops being the bottleneck.

A worked example

Take a solo agent with 12 active listings. On a Monday she pastes in listing 7, a three-bedroom with 21 days on market, four showings since the last update and feedback that the kitchen feels dated. Her Skill classifies it as Yellow and drafts an email that gives the four showings and the kitchen comment, suggests a $5,000 price adjustment or a seller-funded cosmetic refresh, and asks for a call Thursday. She changes the dollar figure to $7,500 because she knows the comps, and sends it. Twelve updates take her about 40 minutes instead of the three or four hours of writing she used to dread. Those times are an estimate, not a measured result.

What goes wrong

The Skill will write confidently about numbers you gave it wrong. It cannot see your MLS or your showing app unless you paste the data in, so garbage in, garbage out. It can also drift toward blandness, which is why your three sample emails matter.

Do not paste a seller's private details, financial situation or anything under confidentiality into a tool unless you understand your brokerage's policy. Check your broker's rules on AI use and your MLS rules on how descriptions may be written and disclosed. Claude's Skills documentation also notes that Skill data follows Anthropic's standard retention policy.

Also, a Skill is not a CRM. It will not remember that the Hendersons asked for weekly calls. Keep that in your own system.

When not to do this

If you have five or fewer listings, a good saved prompt does the job. If your sellers want a phone call, no email fixes that. And if you do not have the data, because you are not tracking showings and feedback, fix that before you automate the writing.

Frequently Asked Questions