agentleFS
TemperbyteTemperbyte/temperbyte-skills./skills/listing-writer/SKILL.md

listing-writer

Skill0 starsChanged 5 days agoMITView on GitHub

Writes MLS-ready real estate listing copy (headlines, MLS public remarks, website description, feature bullets, social caption) from an agent's rough property notes, with a built-in fair housing language check and a list of facts to verify before publishing. Use when a real estate agent asks for a listing description, MLS remarks, property ad copy, or wants an existing listing rewritten or improved.

The file

We split this skill into the rules it gives an agent

8 rules. About 0 are common, 8 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈8

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If anything required is missing, ask for all missing items in ONE short message, then wait.

    line 21
  2. Distinctive:

    If the agent says to proceed anyway, write the copy and list the gaps under "Facts to Verify".

    line 22
  3. Distinctive:

    Never invent facts: Do not add measurements, years, brands, materials, school names, distances, views, HOA details or amenities that are …

    line 23
  4. Distinctive:

    Default limit: 1,000 characters including spaces, unless the agent gives a different limit.

    line 45
  5. Distinctive:

    Mention each feature once: If the hook already named the backyard or courtyard, do not bring it back later in the remarks.

    line 48
  6. Distinctive:

    Do not include agent names, phone numbers, websites, showing instructions or price.

    line 50
  7. Distinctive:

    Use numerals for bedrooms, bathrooms, years, distances and measurements.

    line 71
  8. Distinctive:

    Use "primary bedroom" / "primary suite", not older terms.

    line 72

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Listing Writer

Turn an agent's rough property notes into specific, compliant, ready-to-paste listing copy. The agent should be able to publish the output after checking the "Facts to Verify" list, with no rewriting.

Privacy first

  • Do not ask for or repeat personal details of sellers, buyers or tenants (names, phone numbers, email addresses, finances or personal circumstances). Describe the property and the transaction only. If the paste contains such details, leave them out of the output and add one line at the top: "Tip: remove client names and contact details before pasting."
  • Example data in your replies must be invented, never a real client's data.

Step 1: Collect inputs

Required: property type, location (city or neighborhood), bedrooms, bathrooms, and at least three notable features.

Optional but valuable: square footage, lot size, year built, upgrades with their years, garage/parking, HOA, price, MLS character limit, preferred tone.

  • If anything required is missing, ask for all missing items in ONE short message, then wait.
  • If the agent says to proceed anyway, write the copy and list the gaps under "Facts to Verify".
  • Never invent facts. Do not add measurements, years, brands, materials, school names, distances, views, HOA details or amenities that are not in the notes. If it was not provided, it does not appear.
  • Do not derive one fact from another. For example, "original 1920s brick exterior" does not establish the year built, and "updated bath" does not mean an "updated interior". Use only what is stated, and list the gap under "Facts to Verify".

Step 2: Find the hook

Rank the features by how much they matter to buyers, highest first:

  1. Rare or hard-to-change: location specifics, lot, views, layout, natural light, outdoor space.
  2. Recent big-ticket updates with years: roof, HVAC, windows, kitchen, bathrooms, flooring.
  3. Lifestyle spaces: office, finished basement, patio, garage workshop.
  4. Standard finishes and everything else.

Open with the one or two strongest features. Never open with "Welcome home", "Don't miss", "Look no further" or a question.

Step 3: Write the outputs

Produce all of the following, in this order, using exactly these headings.

Headlines

Three options, each 60 characters or fewer, each built around a different specific feature.

MLS Public Remarks (N characters)

  • Default limit: 1,000 characters including spaces, unless the agent gives a different limit.
  • Count characters with a code tool if one is available; otherwise estimate conservatively and stay about 10% under the limit. Put the final count in the heading.
  • Structure: hook sentence → interior in walk-through order (living areas → kitchen → bedrooms → baths) → updates with years → outdoor space and location → closing line with square footage and year built if provided.
  • Mention each feature once. If the hook already named the backyard or courtyard, do not bring it back later in the remarks.
  • Use the space the notes support. Aim for 60–90% of the character limit when the notes have enough facts; use the room for specifics (room details, update years, location facts), never filler. Thin notes give shorter remarks.
  • Do not include agent names, phone numbers, websites, showing instructions or price. Many MLSs prohibit contact details in public remarks, and price has its own field.

Website Description

100–250 words, short paragraphs, same facts as the remarks but with more room for flow and detail. Length follows the notes: thin notes give a shorter description. Never pad with filler or invented detail to reach a word count. Open with the strongest feature stated directly, not with commentary about the listing ("The first thing to see here is..."). Write in the listing agent's voice: no closing line like "Contact your agent", and no call to action unless the agent asks for one.

Feature Highlights

6–10 bullets, facts only, scannable, most valuable first.

Social Caption

300 characters or fewer, 1–3 relevant hashtags, no emojis unless the agent asks for them. Price may appear here if the agent provided it.

Compliance Check

List every phrase from the agent's notes that was removed or rewritten, what replaced it, and a one-line reason. If nothing needed changing, write "No issues found in the notes."

Facts to Verify

Up to 8 items: every specific claim that would be costly if wrong in print (years, measurements, brands, distances, HOA, price), so the agent can confirm before publishing.

Writing rules

  • Specific beats generic. "2023 quartz counters" beats "updated kitchen". Every adjective must be backed by a fact in the same sentence.
  • Banned filler: stunning, nestled, boasts, gem, must-see, won't last, dream home, pride of ownership, charming, cozy, turnkey, one-of-a-kind, breathtaking, oasis, entertainer's dream.
  • Use numerals for bedrooms, bathrooms, years, distances and measurements.
  • Use "primary bedroom" / "primary suite", not older terms.
  • Present tense. No ALL CAPS. At most one exclamation mark across all outputs.
  • Match the agent's requested tone; default to confident and plain.

Fair housing check (mandatory, run before output)

Describe the property, not the people who should live in it. Scan the notes and your draft, and rewrite anything that:

  • Says who the buyer should be: "perfect for families", "ideal for young professionals", "great for retirees", "empty nesters", "bachelor pad". Replace with the features behind the claim (for example "3 bedrooms on one level", "fenced backyard").
  • Refers to protected characteristics of residents or the neighborhood. Under US federal law these are race, color, religion, sex, disability, familial status and national origin; state and local laws often add more (for example age, sexual orientation, gender identity, source of income).
  • Characterizes the neighborhood's people or safety: "safe neighborhood", "exclusive", "family neighborhood", "quiet street of retirees". Replace with verifiable facts the agent provided, such as distances to named parks, trails or transit.
  • Rates or ranks schools: "great schools", "top-rated district". Name a school or district only if the agent provided the name, and never rate it.
  • Uses religious landmarks as selling points. Omit unless the agent explicitly asks to include a named landmark.

Factual descriptions remain fine: "0.4 miles to Cedar Park", "family room" as a room name, and accessibility features stated plainly ("no-step entry", "grab bars in primary bath").

This check reduces risk but is not legal review. The agent is responsible for final compliance with their MLS rules and applicable law.

Rewriting an existing listing

When given an existing description instead of notes: keep every fact, apply all rules above, produce the full output set, and add a final section "### What Changed" with up to three bullets about structure, opening and style. Do not repeat items already listed in the Compliance Check.

Review reminder

End every output with this line, exactly: Draft made with AI. Check every number, fact and recommendation before you use it.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.