Claude skills for real estate agents: save a job once and run it by name

If you're typing the same instructions twice, you're doing it wrong.

By now you've probably noticed a pattern. You give Claude a job, it does it well, and a few days later you need the same job done again. So you scroll back, find the instructions you wrote last time, copy them, paste them and tweak them. Or you type them out again from memory and forget half of it.

That's the problem skills fix.

A quick reminder on words. I call it SI, super intelligence. Most people say AI. When I say SI here I mean tools like Claude, made by Anthropic.

What a skill actually is

A skill is a job you explain once and then just name.

You write out the instructions properly, one time. Claude saves them as a skill with a name. From then on, you don't repeat the instructions. You say the name, give it what it needs for this particular job, and it follows the rules you already set.

Think of it like training a new assistant. The first week, you explain how you like things done. After that, you don't explain it every time. You just say "can you do the listing description for this one?" and they know what you mean.

Under the hood, a skill is a small set of saved instructions, sometimes with example files alongside. Claude knows which skills it has and pulls one in when you ask for it by name, or when the job clearly matches.

Why this matters for an agent's week

Most of the writing in a real estate business isn't one-off. It's the same handful of jobs over and over:

Listing descriptions
Appraisal follow-up emails
Open home recap notes
Price update messages to vendors
Social captions for a new listing

Every one of those has rules. How long it should be. What tone. What to always include. What to never say. Those rules live in your head, and every time you hand the job to Claude without them, the result drifts a bit.

A skill locks the rules in. The listing description you get on a Friday afternoon follows the same standard as the one you carefully briefed on a Monday morning. And you're not spending the first five minutes of every job re-explaining yourself.

It also makes the rules easier to improve. If something comes back wrong, you fix the skill once, and every future job gets the fix.

Start with a job you've already briefed well

Yesterday was about briefing Claude properly. A skill is that brief, saved.

So the best time to make a skill is straight after a job has gone well. You've just written clear instructions, Claude has followed them, and you've checked the result. That conversation already holds everything the skill needs.

For listing descriptions, your instructions might cover things like:

Length. A rough word count or number of paragraphs.
Structure. What goes first, what goes last.
Tone. How it should sound, and words to avoid.
Accuracy. Only use features in the notes. Never invent a room, a view or a distance.
Spelling. Australian spelling throughout.
What to send back. For example, a headline plus the description, ready to paste.

Those are your rules, not mine. Write the ones that match how you work and what your office requires.

The Day 15 prompt

Use this in the same conversation where you've already given Claude your listing description instructions.

Prompt

Turn the instructions I gave you for listing descriptions into a reusable skill called Listing Description, so next time I just say 'listing description' and paste my notes.

Here's what each part is doing.

"Turn the instructions I gave you for listing descriptions" points Claude at the brief that's already in the conversation. You don't have to write it all again. It gathers up what you said.

"into a reusable skill" tells it the output isn't a description. It's a saved set of instructions it can use again later.

"called Listing Description" gives it a clear name. Pick names you'll actually remember and say. Plain names beat clever ones.

"so next time I just say 'listing description' and paste my notes" describes how you'll use it. That shapes the skill: it knows to expect raw notes as the input and to turn them into a finished description using your rules.

Try it yourself

Check skills are turned on. In the Claude desktop app, look in Settings for the area that covers capabilities or skills. Depending on your plan and version, it may be on already. If you can't find it, ask Claude where skills live in your version of the app.
Brief one listing description properly. Start a conversation, write out your rules in full, and paste notes from a property. Use notes with no client personal details in them.
Check the result. Fix anything you don't like by adjusting the rules, not just the description. You want the instructions right before you save them.
Paste the Day 15 prompt. Add "show me the skill before you save it" on the end, so you can read the instructions it's about to keep.
Read what it shows you. Make sure every rule you care about is in there and nothing has been added that you didn't ask for.
Save it. Depending on your version, Claude will either save the skill for you, or give you a skill file to add through Settings. Follow what it tells you.
Test it in a fresh conversation. Start a new chat, type "listing description", paste a different set of notes, and see if the result follows your rules without any extra explaining.

If the test result is off, go back to the skill and tighten the instructions. That's normal. Most skills get better over the first few uses.

Keep the same safety habits

Skills make jobs faster, which is exactly why the habits from earlier in the series still matter.

One narrow folder. If a skill works with files, give it the folder for that job only. Not your whole computer.
Approvals on. Keep approvals on for anything that sends, spends or deletes. A skill that drafts a vendor email is fine. A skill that sends it should still wait for your yes.
"Show me your plan first." Especially the first few times you run a new skill. You'll see whether it's following your rules before it does the work.
Read before you use. A listing description still goes out under your name. Check it against the property before it goes anywhere.

What to save next

Once the first skill works, you'll start noticing other jobs you repeat. A good rule of thumb: if you've briefed the same job twice, it's ready to be a skill.

Build them one at a time. Brief the job well, check the result, then save it. A small set of skills you trust is worth more than a long list you've never tested.

Missed yesterday? Day 14: How to brief AI properly

Every prompt from the series is on my free prompts page, with a new one each day as the episodes go up, ready to copy.