agentsclimarketplace
Sign in

Quick start 3 wins

Skill TheProsperityAgent/prosperity-real-estate-skills/skills/quick-start-3-wins

Three plug-and-play prompts for new realtors getting started with Claude — listing descriptions, counter-offer replies, and social posts from MLS pulls. Use when an agent has just installed Claude and wants three useful workflows running today.From its SKILL.md

Install
npx -y skills add TheProsperityAgent/prosperity-real-estate-skills --skill quick-start-3-wins

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 7 stars7 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

3.4 KB, 804 tokens by cl100k_base, as published. Nobody here has run it

Quick Start — 3 Wins for Realtors

When to use this skill

You just installed Claude. You want three workflows running today, not next week. You don't want to read a tutorial — you want copy-paste-go.

What it does

Three prompts. One paragraph each. Compliant from the first character: no school references, no scarcity language, no fair-housing violations, always positive.

Prompt 1 — Listing Description

You're writing a [CITY] [STATE] listing description for me, an agent.
Tone: warm, specific. NEVER use "must-see" or "won't last" or any cliché.
145 words max. The home is at [ADDRESS], [BEDS] bed [BATHS] bath, [SQFT]
sqft, on [LOT] acres, built [YEAR]. Standout features: [3 BULLETS]. End
with a line about [CITY] life that doesn't mention schools.

Why these constraints:

  • Banned clichés ("must-see", "won't last") signal low-quality content to search engines.
  • The school exclusion is a fair-housing rule — we never sort buyers by school perception.
  • 145-word cap matches the optimal MLS field length.

Prompt 2 — Counter-Offer Reply

I'm a real estate agent. My buyer offered $[X] on a list price of $[Y].
The seller countered at $[Z] with [TERMS]. Write a reply email to the
listing agent that holds my position on price but signals flexibility on
close date / inspections / appliances. Tone: collegial, no pressure,
respect their professionalism.

Why this works:

  • The reply email is half the negotiation. Most agents under-write it.
  • "Collegial, no pressure" matters in small markets where you'll see the same listing agents every week.
  • Hold price, flex on close-date / appliances — that's how a 20-year agent writes.

Prompt 3 — Three Social Posts From Today's MLS Pull

I'm a real estate agent in [CITY] [STATE]. Here are today's [N] new
listings under $[BAND]: [PASTE]. Write 3 social posts:
  - Post 1: Instagram caption ≤2200 chars, hook + 5 hashtags, no links
  - Post 2: Facebook ≤700 chars, conversational, ask a question
  - Post 3: TikTok caption ≤300 chars, punchy, 5 hashtags
Frame: positive, never knock anywhere or anyone. No school rankings.
No "won't last."

Why these constraints:

  • IG 2200 / FB 700 / TikTok 300 = the actual Notion-rule character caps for compliance.
  • "Always positive" and "no school rankings" are fair-housing requirements.
  • 5 hashtags hits the sweet-spot for reach on every major platform in 2026.

Compliance notes

  • Fair Housing: never references schools, never describes neighborhoods by demographic.
  • TCPA: these prompts produce content for owned channels (your social, your listings) — not unsolicited outreach.
  • MLS rules: banned clichés ("must-see", "won't last") protect against MLS data-quality penalties.
  • Always positive: never knocks a town, builder, neighborhood, competing platform, or competing agent.

Companion content

Built by

Al & Victoria Pinder · The Prosperity Agent · ICON Agents, eXp Realty

What ships with it: 3 files

11.2 KB alongside SKILL.md

examples/

Gives 0 of the 12 instructions most context ai engineering skills give in 804 tokens

Counted across 1,328 of the 2,349 authors here whose files we hold, read 2026-09-06

  • Dispatch a fresh subagent for each taskin 76 of 1328, across 59 files
  • Perform spec compliance review before code quality reviewin 44 of 1328, across 34 files
  • Dispatch a final code reviewer after all tasksin 38 of 1328, across 26 files
  • Answer subagent questions before allowing implementationin 36 of 1328, across 26 files
  • Use the least powerful model capable of the taskin 33 of 1328, across 26 files
  • Create a TodoWrite list for all tasksin 32 of 1328, across 22 files
  • Perform a task review after each implementationin 31 of 1328, across 24 files
  • Extract all tasks and context from the planin 29 of 1328, across 20 files
  • Provide full task text to subagentsin 28 of 1328, across 20 files
  • Use git worktrees for isolated workspacesin 25 of 1328, across 20 files
  • Specify the model explicitly when dispatching a subagentin 23 of 1328, across 18 files
  • Execute all tasks from the plan without stoppingin 21 of 1328, across 16 files

Said here and by no other author read

  • write listing descriptions under 145 words
  • maintain a warm and specific tone
  • write counter-offer emails with a collegial tone
  • hold price while signaling flexibility on terms
  • create three social media posts from listing data
  • use five hashtags for social media posts

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.