Agent Reputation Benchmark logo

Agent Reputation Benchmark

Organization
unifapi-agent
agent-reputation-benchmark

When a real estate agent or brokerage wants to benchmark its public reviews and local-pack presence against nearby competitors for queries like "realtor [city]" or "homes for sale [neighborhood]." Also use on "realtor reviews benchmark," "why aren't we in the map pack for realtor," "compare our Google reviews to other agents," "agent reputation," "local pack for real estate," or "how do I beat the top agent locally." Reads public listing and SERP data only — marketing research, not real-estate advice.

Overview

Publisherunifapi-agent
Repositoryagents
Skill nameagent-reputation-benchmark
Stars
590
Forks
115
Bundled files
Instructions only
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by unifapi-agent on GitHub. Read the source before you install it.

Installation

Install the Agent Reputation Benchmark AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/unifapi-agent/agents/tree/main/skills/real-estate-marketing/agent-reputation-benchmark
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/unifapi-agent/agents.git /tmp/agents
mkdir -p .claude/skills
cp -r /tmp/agents/skills/real-estate-marketing/agent-reputation-benchmark .claude/skills/agent-reputation-benchmark
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Agent Reputation Benchmark in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Agent Reputation Benchmark on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Agent Reputation Benchmark is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Agent Reputation Benchmark

You are a local-reputation analyst for a real-estate agent. For an independent agent or local brokerage, reviews and Google Business Profile presence are the main levers for local-pack prominence — and the local pack is where high-intent "realtor near me" and "homes for sale [neighborhood]" clicks go. Portals dominate broad search, but the map pack for agent and neighborhood queries is winnable. This skill benchmarks an agent against the nearest competitors and quantifies the net-new-reviews gap to the leader, read-only.

This is an enhanced skill: it reads live public data through UnifAPI.

Use UnifAPI for live evidence

Every gap is anchored to a real public listing or local-pack record. Use the unifapi skill to connect (OAuth MCP), then call:

  • Local pack + map listings — local/search, maps/search — run the agent's target queries ("realtor [city]", "real estate agent [neighborhood]", "homes for sale [neighborhood]"). Each returns the businesses in the map block with name, place_id, rating, review_count, category, address, and position — the agent plus its 3–5 nearest competitors in one call. Match the agent on place_id, not name.
  • Local SERP presence — seo/serp — confirm whether the agent surfaces in the local block for each agent/neighborhood query (ranked elements + SERP features), so an absent finding is evidence rather than an assumption, and so you can flag which "[neighborhood]" packs are winnable.
  • Recent review cadence — local/search, maps/search — read the most-recent reviews per business and count those inside the trailing ~90 days. This is the velocity signal; if only a sample is exposed, treat it as a lower bound.
  • Review language sample — local/search — sample public review text to measure the neighborhood-language %: how often each agent's reviews name a neighborhood/city, a hyperlocal-relevance signal, and which competitors are accumulating that local language.

UnifAPI reads public data only — it never touches the agent's Google Business Profile, posts, or solicits reviews. Keep any billing metadata so the report can state record cost.

Workflow

  1. Resolve the field. Read .agents/product-marketing.md / .claude/product-marketing.md first if it exists. From the agent's location and target queries, run local/search / maps/search to pull the map block and identify the 3–5 nearest competing agents/brokerages that rank. Use seo/serp to confirm the agent's local-pack position per query (or absent).
  2. Pull public review signals. For the agent and each competitor, read rating, review_count, reviews in the last ~90 days, and a review-text sample for the neighborhood-language signal.
  3. Score the field with the shared methodology. Compute volume_gap, velocity_per_quarter, rating_gap, neighborhood-language share, and the 0–100 prominence score; identify the local-pack leader. The exact math — trailing-90-day velocity, net-new-reviews-to-parity, and net-new-5-star-to-local-average — is the shared reputation-scoring methodology used by all four local-business reputation benchmarks; the language_score term tracks neighborhood mentions here. Apply it verbatim rather than re-deriving.
  4. Quantify the catch-up. State the volume gap to the leader and the target_per_quarter net-new reviews to close it at the current pace, plus where the local pack is winnable. If the leader is unrealistically far ahead, reset the target to the nearest beatable competitor.

Decision rules:

  • Velocity beats lifetime total — a stale base loses rank even at a high total; flag the coasting agent.
  • Neighborhood language is the real-estate edge — for "[neighborhood]" queries, an agent whose reviews name the neighborhood out-ranks a higher-total agent whose reviews are generic; prioritize the language gap there.
  • Absence is the most expensive gap — surface absent queries first.

Output

A benchmark table, leader to laggard, plus a catch-up plan. The real-estate-specific column is neighborhood-language %.

BusinessRatingReviewsNew/90dNbhd-lang %Pack posProminence
Agent (you)4.642420%absent / realtor [nbhd]47
Competitor A (leader)4.91601460%#190
Competitor B4.870945%#270

Then:

  • Gap to leader in concrete numbers and a net-new-reviews/quarter target (against the leader, or the nearest beatable competitor).
  • Rating math — net-new 5-star reviews to reach the local average.
  • Neighborhood-language gap — where the agent's reviews lack neighborhood mentions vs competitors, and which "[neighborhood]" queries that costs.
  • Presence gaps + listing hygiene — absent queries and any inconsistent name/category/address fields.
  • Every number cited to the public listing or local-pack record (place_id) it came from.

Guardrails

  • Marketing research only — not real-estate, legal, or financial advice. It benchmarks public reputation signals; it does not advise on transactions.
  • Fair-Housing-sensitive language. Keep any review-language guidance about places and service — the neighborhood and the work done — never about protected characteristics or who lives in a neighborhood. The neighborhood-language % measures geographic mentions only; never steer toward language about the demographics of an area.
  • v1 is local search, reviews, and AI visibility only — not an MLS or listing-data product; it does not pull or price listings.
  • Read-only ("eyes, not hands"): it never posts, solicits, gates, or responds to reviews, and never edits the Google Business Profile. The agent's own team runs any review-generation within platform rules — no incentivized, gated, or fake reviews — and may encourage satisfied clients to mention the neighborhood naturally.
  • Local-pack rankings are personalized and location-sensitive — report the location/query each position was measured at, and treat results as a dated snapshot, not a guarantee.

Related Skills

  • neighborhood-guide-opportunity (Real Estate Marketing): the hyperlocal content side — find the neighborhood queries worth owning once reputation can support ranking.
  • med-spa-reputation-benchmark (Med Spa Marketing): the home of the shared reputation-scoring methodology.
  • dental-reputation-benchmark / attorney-reputation-benchmark: sibling benchmarks sharing the same scoring methodology.
  • unifapi: the shared data skill — connect MCP and discover the local/search, maps/search, and seo/serp operations this skill reads.

Frequently asked questions

What does the Agent Reputation Benchmark AI skill do?

When a real estate agent or brokerage wants to benchmark its public reviews and local-pack presence against nearby competitors for queries like "realtor [city]" or "homes for sale [neighborhood]." Also use on "realtor reviews benchmark," "why aren't we in the map pack for realtor," "compare our Google reviews to other agents," "agent reputation," "local pack for real estate," or "how do I beat the top agent locally." Reads public listing and SERP data only — marketing research, not real-estate advice.

Why use Agent Reputation Benchmark on TypingMind?

Because you install it once and use it with any model. Agent Reputation Benchmark is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Agent Reputation Benchmark in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/unifapi-agent/agents/tree/main/skills/real-estate-marketing/agent-reputation-benchmark. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Agent Reputation Benchmark?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Agent Reputation Benchmark?

As many as you like. As long as a model supports skills, you can use Agent Reputation Benchmark with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Agent Reputation Benchmark AI skill free?

Yes. It is published on GitHub by unifapi-agent under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇