Claude skills for commercial real estate teams

Claude skills for commercial real estate are worth building when they hold what only your team knows, and the first two a brokerage team should build are prospecting research and call prep. A skill downloaded from a generic pack is the least valuable version, because it cannot contain your target criteria, your submarkets, or the format of your call sheet.

If your firm has rolled out Claude accounts, or you use it on your own, you have probably noticed that the good results come after a long paragraph of instructions, and that you type some version of that paragraph every week. A skill is where that paragraph goes to live.

What is a Claude skill, in plain terms?

Anthropic's documentation defines skills as modular capabilities that package instructions, metadata, and optional resources such as scripts and templates, which Claude uses automatically when they are relevant. The same page draws the line between a skill and a prompt: a prompt is a conversation-level instruction for a one-off task, while a skill loads on demand so you do not repeat the same guidance in every conversation.

Physically, a skill is a folder. Anthropic's engineering team describes it as a directory containing a SKILL.md file along with any instructions, scripts, and resources it needs, and compares building one to putting together an onboarding guide for a new hire. That comparison is the useful one for a broker. Think about what you would hand a sharp new analyst on their first day so they could prepare a call sheet the way your team does it.

Only the skill's name and description are loaded all the time. The documentation explains that the full instructions are read when a request matches the description, and bundled files are read only when needed. So the description has to say both what the skill does and when to use it. We cover the mechanics in more depth in our plain guide to Claude skills.

Why does a downloaded skill pack underdeliver?

Anthropic's authoring guidance starts from the assumption that the model is already very capable and tells authors to add only the context Claude does not already have. Claude already knows what a cap rate is, what a tenant rep does, and how to write a polite email. A skill written for real estate in general can only restate those things.

What Claude does not know is everything specific to your team. That is the material a skill should carry.

What belongs in the skill	Example for a brokerage team (illustrative)
Target criteria	The building size range, tenant types, ownership profile, and lease expiration window that make a name worth a call
Submarket definitions	Where your team draws the boundaries, which may not match a data vendor's map
Voice by audience	How you write to an owner compared with a tenant, and what you never say in a first note
Output format	Your call sheet, your one-page brief, your survey layout, attached as a template
Prior work to imitate	Two or three finished examples the team considers good
Checks	The rules a senior person would apply before the work leaves the building

How is a prospecting skill built?

A prospecting skill takes a submarket or a property type and returns a ranked list of names worth calling. Four parts do the work.

1. The criteria. Write down what makes a target for your team, in the same words you would use with a new analyst. This is the part no outside author can supply.
2. The allowed sources. Name the public sources the skill may use, such as county assessor and deed records, secretary of state filings, company websites, and press coverage, along with any data subscription your team is licensed to use this way.
3. The output. A ranked list where each name carries the reason it is on the list and the source for each fact. A broker should be able to check any line against its source without redoing the research.
4. A hard rule on contact details. The skill never invents a phone number or an email address. If it did not find one in a named source, the field says "not found."

That last rule matters because a plausible-looking wrong number costs a broker more time than a blank cell. The source column is what makes the list usable by someone who did not build the skill.

How is a call prep skill built?

A call prep skill produces the one-page brief you want in front of you before you dial. The inputs come from two places. The first is what your team already holds on the person: CRM notes, past emails, the last proposal. If your Claude workspace is connected to those systems, the skill tells Claude where to look. If it is not, the skill asks you to paste or upload the notes. The second is what is public about the company and the property.

The output is the brief in your team's format, with a section at the bottom that lists open questions. That section should be mandatory. A brief that says "lease expiration not found in CRM or public record" is more useful on a call than one that guesses.

Which other skills are worth building?

Once prospecting and call prep are in use, the same method applies to the other documents a brokerage team produces every week:

• A lease abstract in your template, with a page reference for every term.
• The first pass of a broker opinion of value, with the comps and assumptions laid out for a senior broker to correct.
• A survey workbook filled from flyers and proposals.
• A client story that turns a closed deal into a short, personalized piece for a specific prospect.

What should be a script and what should be written instructions?

A skill is instructions plus optional code, and the two do different jobs. The documentation puts it this way: instructions for flexible guidance, code for reliability. The authoring guide advises using a specific script when consistency is critical or an operation is fragile, and written guidance when judgment depends on context.

For a brokerage team, the rule of thumb is that anything that must come out identical every time belongs in a script. Filling the cells of your survey workbook, laying out the call sheet, and calculating rent per square foot from extracted figures are script work. Deciding which three facts about an owner matter most for this call is instruction work.

How do you test a skill before the team relies on it?

Anthropic recommends building evaluations before writing extensive documentation: run Claude on representative tasks without the skill, note the specific failures, build at least three test scenarios around them, and then write just enough to pass. The guide also says to iterate from behavior observed on real tasks instead of from assumptions.

In brokerage terms, pick three to five real cases where you already know the right answer: a submarket where your team knows every owner, a contact with a long CRM history, a contact with none. Run the skill, compare the output to what a senior broker would have produced, and fix the instruction that caused each miss. Rerun the same cases whenever the skill changes.

Can the whole team share a skill, and is it safe to install one from the internet?

On sharing, Anthropic's own pages currently say different things. The help center says owners of Team and Enterprise organizations can provision skills for all users, and that members on those plans can share skills with colleagues once an owner enables it. The developer documentation says custom skills on claude.ai are individual to each user and that each team member must upload separately. Both pages agree that skills require code execution to be enabled. Before you plan a rollout, have your administrator check what your plan does today.

On safety, the documentation is direct: use skills only from trusted sources, meaning ones you created or obtained from Anthropic, and treat a skill like installing software. A skill can include code, and the same page warns that a malicious one could direct Claude to act in ways that do not match its stated purpose, including leaking data. The help center extends the caution to skills shared by a colleague. A free download pack should get the same review your IT lead would give any other software before it touches client files.

This matters more as firms standardize. Bisnow reported in June 2026 that one national brokerage had bought an enterprise Claude account, and that companies across the industry have reported struggling with employees using AI without official approval.

Do outreach rules still apply to a drafted email?

The FTC's CAN-SPAM compliance guide states that the law makes no exception for business-to-business email, so a commercial message that Claude drafted is covered like any other. The guide's requirements include accurate header information, a subject line that reflects the content, a valid physical postal address, and a clear way to opt out that is honored within 10 business days. It puts the penalty at up to $53,088 for each email in violation.

A skill can draft the note. A person on your team should read it, correct it, and send it from their own account. Confirm your outreach practice with your own counsel or compliance lead, since a skill does not make a firm compliant.

Should you write skills in-house or have them built?

An instruction-only skill needs no code. Anthropic's guide notes that you can ask Claude to create a skill from a task you just worked through together, and it will produce a properly structured file. A team with one curious person can write a first call prep skill this way.

Outside help earns its place when the skill needs scripts, when it has to read from your CRM or fill a workbook exactly, or when nobody on the team has time to run the test cases. We build prospecting, call prep, and client story skills with brokerage teams inside their own workspace, against their own documents, and the team owns the files afterward. If that is the stage you are at, get in touch.

Common questions

What is a Claude skill?

Anthropic's documentation describes a skill as a package of instructions, metadata, and optional scripts and templates that Claude uses automatically when it is relevant to a request. In practice it is a folder with a SKILL.md file that holds the instructions your team would otherwise retype.

Are there ready-made Claude skills for commercial real estate?

Anthropic publishes pre-built skills for Word, Excel, PowerPoint, and PDF files, and none of them is specific to real estate. A pack written for a general audience cannot contain your target criteria, your submarket boundaries, or your call sheet, and those are what a brokerage skill is for. Anthropic also advises using skills only from trusted sources and auditing anything else before use.

Can a whole brokerage team share the same skills?

Anthropic's help center says owners on Team and Enterprise plans can provision skills for all users and that members can share skills with colleagues when owners allow it. The developer documentation still describes custom skills on claude.ai as individual to each user. Check the current behavior on your own plan with your administrator before planning a rollout around it.

Do I need to know how to code to build a skill?

No, for a skill that is only written instructions. Anthropic's authoring guide says you can ask Claude to create a skill and it will produce a properly structured SKILL.md file. Code comes in when part of the output has to be identical every time, such as filling a fixed template.

Does AI-written outreach have to follow CAN-SPAM?

The FTC's compliance guide says the CAN-SPAM Act makes no exception for business-to-business email, and it contains no exemption for a message that software drafted. Have a person review and send each message, and confirm your outreach practice with your own counsel or compliance lead.