Agent skills for writing listing descriptions
A listing skill writes the description from the property sheet and your photo notes, in your team's voice, at the length each portal wants. The value is not speed on one listing. It is that the fortieth listing this quarter reads as carefully as the first, and that every claim in it can be traced back to a line on the sheet.
Feed it facts, not adjectives
The most common failure is a description full of pleasant language that describes no particular house. That happens when the skill is given a bare address and asked to be enthusiastic. Give it the sheet and it writes about the house.
The property sheet.
Rooms, dimensions, year, lot, systems, what was replaced and when. The replaced-and-when items are the ones buyers search for and the ones agents forget to mention.
Your photo notes.
Twenty seconds of dictation while you walk it: the light in the back bedroom at four o'clock, the neighbour's extension over the fence, the kitchen being smaller than the photos suggest. This is what makes the copy specific.
Three listings your team is proud of.
Voice comes from these. Length limits per portal come from a config line, not from the examples.
A do-not-say list.
Your compliance language, your banned adjectives, the claims your brokerage will not make. This list is not optional, and the next section is why.
The guardrail that has to be written down
Listing copy is regulated. Fair-housing rules restrict language that describes the people who might live somewhere rather than the property itself, and a model trained on the open internet has read a great deal of non-compliant copy. Put the constraint in the skill file explicitly, and check the output against it. A skill will not infer a legal boundary from good manners.
Never describe or imply anything about who lives here or
who would suit it. No references to family status, schools
as a selling point for a type of buyer, religion, ethnicity,
language, ability, or "safe" and "quiet" as codes for the
same. Describe the property, the systems, and the location
by fact: distance, transit, zoning.
Never state a fact absent from the sheet. If square
footage, year built or school assignment is not on the
sheet, write [VERIFY] and stop, do not estimate.The [VERIFY] rule is the second half. Square footage and school assignment invented by a model, then published under your license, is your problem and not the tool's.
What you still do yourself
- Read every line against the sheet before it is published. Every number, every date, every appliance.
- Write the first sentence if the property has one unusual thing. The skill will find the best of the ordinary features and lead with it, which is correct nine times out of ten and wrong on the interesting house.
- Decide what to leave out. A skill given a flaw will usually try to phrase it kindly rather than omit it, which is not always what you want and is sometimes exactly what you must do.
- Set the price and the strategy. None of that is in the sheet.
One skill per output, not one skill for listings
A portal description, a social caption, an email to your buyer list and the printed sheet are four different lengths with four different rules. Built as one skill with a mode argument, it will pick the wrong mode about a third of the time. Built as four skills with clear descriptions, each fires on the request that means it. The reasoning is in the guide on why a skill never fires.
Works with Claude Code.
The Real-estate team pack
Twelve skills for listing copy, showing follow-ups and transaction timelines, with the compliance constraint blocks and the eval cases included. The pack page carries the price, the refund terms, and the date everything was last tested.
See the packs