Claude Skills for Real Estate Agents: The 5 to Build First

Every agent has a handful of jobs they do the same way every week. The listing remarks. The photo captions. The Friday email explaining to a seller why there were showings and no offers. You've explained how you like these done to Claude in a dozen separate chats.

A skill ends that. You explain the job once, Claude saves it as a playbook, and from then on it follows your process every time that job comes up, in any chat, without you pasting the same instructions again.

This post covers what a skill is in plain agent terms, how it differs from Projects and prompts, the five skills I tell agents to build first, and the exact prompts to build them. If you haven't set Claude up yet, start with how to use Claude for real estate agents and come back.

What is a Claude skill, in real estate terms?

A Claude skill is a saved playbook for one job. Think of it like the checklist you'd hand a new assistant: here's when this job comes up, here's how I do it, here's what good looks like, here's what I never want. Claude keeps that checklist on file and pulls it out on its own when the job comes up.

Under the hood, a skill is a file called SKILL.md with instructions, plus optional reference files like templates, examples, or rules documents. The name and description sit at the top. Claude reads that top section first to decide whether the skill fits what you just asked, then loads the full instructions if it does.

You don't need to write any of that yourself. Per Anthropic's tutorial on creating a skill through conversation, you describe your process in a normal chat, and Claude writes the file, organizes your materials, and packages it for you.

When I teach this in class, the first thing agents ask is "isn't that just a saved prompt?" Not quite. A saved prompt is something you remember to paste. A skill is something Claude remembers to use.

Skills vs Projects vs prompts: what's the difference?

A prompt is a one-time request, a Project is a workspace with files and instructions, and a skill is a process Claude can run anywhere. They work together, and most agents end up using all three.

The Project holds the stuff (files, rules, history). The skill holds the steps. Typing the same instructions over and over? That's a skill. Uploading the same files over and over? That's a Project. More on Projects in Claude's help article on Projects.

What are the 5 Claude skills every agent should build first?

Build skills for jobs that are mostly writing, that you do every week, and where you already know what "good" looks like. These five fit that for nearly every agent in my classes.

1. Listing description skill

This one takes your property facts and walkthrough notes and returns MLS remarks, a short social caption, and headline options in your voice. Bake in your character limit, your structure, and your Fair Housing rules so you never have to restate them. For the prompt side of this, see the AI listing description prompt.

2. Listing photo caption skill

Hand it the photos and it writes a caption for each room in gallery order. Your rules: describe what's visible, no made-up upgrades, keep captions short.

3. Follow-up drafts in your voice

This skill drafts follow-ups after showings, open houses, and consults. Give it a few real follow-ups you've sent that got replies, so it learns your sentence length, sign-off, and how direct you are. With the Gmail connector on, it can find the thread and save the draft for you to review. The bigger system is in AI lead follow-up for real estate.

4. Seller weekly update skill

Showings, feedback, new competition, and one recommendation, in the same format every week. The hard part of a seller update isn't the writing, it's deciding what to say, so spell out your rules: no pushing a price change unless the data supports it, no guessing about buyer motives. There's a full walkthrough in the AI seller weekly update.

5. CMA talking points from exported data

You export the comps from your MLS as a CSV or PDF, give that file to Claude, and the skill turns it into talking points: price per square foot range, days on market, list-to-sale ratio, outliers, and the three points to make at the kitchen table. More in AI CMA for real estate.

If you want to see what finished tools look like before you build your own, the free Claude 101 kit includes three ready-made ones: the Listing Description Machine, the Listing Photo Captioner, and the Price Reduction Conversation.

How to create a Claude skill by describing your process

Open a new chat, describe the job step by step, upload examples of work you're proud of, and ask Claude to interview you before it builds anything. Claude asks about when you'd use the skill and what good output looks like, then writes the skill and packages it as a file you save.

1. Pick one job. Not "marketing." One job, like "MLS remarks for a new listing."
2. Gather your materials. Two or three examples you were happy with, any template you use, and your brokerage's advertising rules if they apply.
3. Start a new chat and paste the prompt below. Fill in the brackets and attach your files.
4. Answer the questions one at a time. Give enough detail that a capable assistant who's never met you could follow your approach. That's the bar the tutorial sets, and it's the right one.
5. Let Claude build it. It writes the SKILL.md, organizes your files, and packages everything.
6. Save the skill file Claude gives you.

The "build me a skill" prompt

I want you to build me a Claude skill for a job I do every week as a real estate agent. Before you write anything, interview me one question at a time until you understand the job well enough to do it without me. Then build the skill and package it so I can save it and turn it on.

THE JOB: [NAME IT, e.g. "MLS public remarks for a new listing"]

WHEN IT COMES UP: [e.g. "after I walk a new listing and have the property facts and my notes"]

WHAT I GIVE YOU TO START: [e.g. "property facts sheet, my walkthrough notes, sometimes photos"]

HOW I DO IT NOW:
1. [STEP, e.g. "Pull the three features buyers will care about most"]
2. [STEP, e.g. "Open with the strongest one, not the bedroom count"]
3. [STEP, e.g. "Cover layout, updates, outdoor space, location facts"]
4. [STEP, e.g. "Check against my character limit"]

WHAT A GREAT RESULT LOOKS LIKE: [e.g. "under [CHARACTER LIMIT] characters, specific details, no hype words, reads like a person wrote it"]

WHAT I NEVER WANT:
- Invented features or details I didn't give you
- Anything about who the home is ideal or perfect for, school quality, or neighborhood demographics. Describe the property, not the people.
- [YOUR OWN, e.g. "exclamation points, the words 'stunning' or 'boasts'"]

WHAT YOU SHOULD DELIVER EACH TIME: [e.g. "MLS remarks with a character count, a 2-sentence social caption, 3 headline options"]

IF SOMETHING IS MISSING: ask me before writing, don't fill the gap with a guess.

I've attached [NUMBER] examples I was happy with. Match their voice and structure more than any generic real estate style.

Write the skill's description using the words I'd actually type when I need this, so you recognize the job when it comes up.

Start your interview now.

That last line matters. Claude decides whether to use a skill based on its description, so it should sound like you, not a manual.

Record yourself explaining the job

Here's a tip that works better than typing for most agents: record yourself explaining the job out loud, like you're training a new assistant. Use your phone's voice memo app or dictation, talk for five minutes, and paste the transcript into the chat along with the prompt above.

You'll say things out loud you'd never bother to type, like "I never lead with the bedroom count." Those details are what make a skill sound like you. Claude will sort the rambling into steps.

How do you turn a good chat into a skill?

If you already had a chat where Claude nailed a job after some back and forth, ask Claude to turn that chat into a skill. Everything you corrected along the way (tone, length, what to leave out) becomes part of the playbook, so you don't lose the work you put into that conversation.

Paste this at the end of the chat that went well:

This came out exactly how I wanted. Turn what we just did into a Claude skill so you do it this way every time without me re-explaining.

Before you build it:
1. List every correction or preference I gave you in this chat (tone, length, structure, words to avoid, what to ask me first). Show me the list so I can confirm or fix it.
2. List what inputs I gave you to start, so the skill knows what to ask for next time.
3. Point out anything that was specific to this one [LISTING / CLIENT / EMAIL] that should NOT become a rule.

After I confirm, build the skill with:
- A name and a description written in the words I'd actually use when I need this job done
- Step-by-step instructions based on what worked here
- The final version from this chat saved as an example of a great result, with any client names, addresses, and personal details removed
- A rule to ask me for missing information instead of guessing

Then package it so I can save it and turn it on.

Step 3 is the one people skip. If the chat was about one particular house, you don't want "mention the mountain view" turned into a rule for every listing.

How do you turn on a skill in Claude?

Go to Settings > Capabilities > Skills and switch the skill on. That page is your skill library, where you can see every skill you've added and turn each one on or off.

Turn off skills you aren't using. If you built two caption skills while experimenting, keep the good one on so Claude isn't choosing between them. And you don't need a special Project: ask for the job the way you normally would and Claude picks up the skill.

How do you test and fix a Claude skill?

Test a skill by giving Claude a real job it should handle, checking that it says it's using the skill, comparing the output to your standard, and asking Claude to update the skill with whatever was off. Then run it again. Two or three rounds usually gets a skill to where it needs only light edits.

1. Ask for the job naturally. Don't mention the skill. Type what you'd normally type: "write remarks for [ADDRESS], here are my notes."
2. Look for the skill by name. You should see a note that Claude is using your skill in its thinking. If it's not there, the description doesn't match how you talk.
3. Compare to your best example. Is the voice right? The length? Did it ask for missing info, or did it guess?
4. Fix it in words. Use the prompt below.
5. Repeat on a different listing or client, so you know it works beyond the first case.

You used my [SKILL NAME] skill for that, and here's what was off:
- [e.g. "Too long. Remarks should be under [CHARACTER LIMIT] characters."]
- [e.g. "You opened with the bedroom count. Lead with the strongest feature."]
- [e.g. "You said 'updated kitchen' but I never told you it was updated. Only use details I give you."]

Update the skill so these don't happen again. Show me exactly what you changed in the instructions before you save it, then package the updated skill.

If Claude didn't pick up the skill at all, use this instead: "My [SKILL NAME] skill didn't trigger when I asked '[WHAT YOU TYPED].' Update its description so it recognizes requests worded like that."

What guardrails should a real estate skill include?

Every skill that produces something a client or the public will see should have the same four rules written into it: describe the property not the people, never invent facts, ask when something's missing, and leave the final review to you. Put them in the skill once and they're there every time.

• Fair Housing. Listing and marketing skills should describe the property, never who should live there. The NAR guidance on Fair Housing in advertising flags phrases like "ideal for empty nesters" and "perfect for students," while "easy walk to train" describes the property. No school quality claims, no neighborhood demographics. See the Fair Housing checklist for AI listing copy.
• No invented details. Claude makes mistakes and can state wrong facts confidently. The skill should only use what you give it and say so when it's unsure.
• Data comes from you. For CMA and market skills, the first step is "ask for the MLS export." Claude can't see your MLS, and you should check its numbers against your file.
• Sensitive information stays out. Never paste Social Security numbers, bank or account numbers, or anything your brokerage forbids into any AI tool.
• Legal questions go to pros. Anything legal, tax, or compliance related gets confirmed with your broker, an attorney, or a CPA.
• Drafts, not sends. For follow-up skills, have Claude save drafts. You read and send.

What to do this week

Pick the one job on the list above that you did most often last week. For most agents, that's follow-up drafts or the seller weekly update. Record yourself explaining it for five minutes, then run the "build me a skill" prompt with the transcript and two good examples.

Turn it on, test it on three real jobs, and fix it after each one. Once it needs only light edits, build the next. One solid skill beats five half-finished ones. And when you're ready to have Claude run jobs on a schedule, the morning briefing guide is the natural next step.