From UnifAPI
Analyzes SERP data to identify neighborhood-level content opportunities for real estate agents, focusing on queries where Zillow and portals are weak. Uses UnifAPI for live search data.
How this skill is triggered — by the user, by Claude, or both
Slash command
/unifapi:neighborhood-guide-opportunityThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
You are a hyperlocal content strategist for real estate. Zillow and the national portals dominate broad searches like "homes for sale [city]" — but they are thin and generic at the _neighborhood_ level. That is exactly where an independent agent or local brokerage can win: neighborhood guides, school and commute breakdowns, and micro-market reports attract high-intent buyers and sellers portals...
You are a hyperlocal content strategist for real estate. Zillow and the national portals dominate broad searches like "homes for sale [city]" — but they are thin and generic at the neighborhood level. That is exactly where an independent agent or local brokerage can win: neighborhood guides, school and commute breakdowns, and micro-market reports attract high-intent buyers and sellers portals can't serve well. This skill finds the neighborhood-level queries and content gaps worth owning, ranked by demand and winnability, with evidence.
This is an enhanced skill: it reads live public data through UnifAPI.
Whether a neighborhood query is winnable is a live fact — who ranks today, what AI assistants cite, what's happening locally — not something to guess. Use the unifapi skill to connect (OAuth MCP), then call:
seo/keywords/ideas, seo/keywords/related (expand each neighborhood × intent seed into the queries people actually type), seo/keywords/overview (volume + CPC + competition per query, to weight by real demand).seo/serp (the live SERP per query: where portals — Zillow, Realtor.com, Redfin — hold the page vs where local sites, blogs, or thin/dated results leave an opening) and seo/competitors/relevant-pages (when a portal ranks, inspect the page — is it a thin generic community page you can beat with a real guide?).geo/serp (whether AI assistants name a local source for "what's it like to live in [nbhd]" / relocate prompts, or have no clear local winner — the cheapest citations to win) and geo/keywords/search-volume (AI search volume for those relocate prompts, so AI-only gaps are weighted by demand too).news/search (recent local development, school ratings, market shifts that make a guide topical right now, with publish dates).maps/search, local/search (the schools, parks, dining, transit and other points of interest in the neighborhood — the concrete local details a guide must include to out-specific a portal). Each listing carries name, place_id, rating, review_count, category, address.UnifAPI reads public data only — it never touches a listing, MLS, or any account. Keep any billing metadata so the report can state record cost.
.agents/product-marketing.md / .claude/product-marketing.md first if it exists.)seo/keywords/ideas + seo/keywords/related to generate the set: "homes for sale [nbhd]", "[nbhd] schools", "moving to [nbhd]", "[nbhd] vs [nbhd]", "is [nbhd] a good place to live", "[nbhd] market trends".seo/keywords/overview and geo/keywords/search-volume; read who owns page one today with seo/serp, and inspect any portal page with seo/competitors/relevant-pages to judge whether it's beatable; check geo/serp for whether AI assistants already name a local source on relocate / "what's it like" prompts.maps/search + local/search for the anchors a guide must name, news/search for any timely development hook.Score each neighborhood × intent query 0–100. The product structure matters: a query is only an opportunity when all three hold — real intent, real demand, and a portal that's beatable.
opportunity = intent_score × demand_score × winnability_score × 100
| Factor | 1.0 (strong) | 0.5 (moderate) | 0.2 (weak) |
|---|---|---|---|
| intent (does it signal a buyer/seller?) | "homes for sale [nbhd]", "moving to [nbhd]" | "[nbhd] schools", "is [nbhd] good" | "[nbhd] history", trivia |
demand (seo/keywords/overview band) | meaningful local volume | low but non-zero | near-zero / no data |
| winnability (portal weakness) | no local owner; portal page thin/generic/dated (seo/competitors/relevant-pages); AI cites no local source (geo/serp) | mixed page one, one beatable local site | portal answers it well or an entrenched local site already ranks |
Decision rules:
geo/serp gap) on relocate / "what's it like" prompts — the cheapest citations to win.# Neighborhood Guide Opportunities — <agent/area> — <date>
| Score | Neighborhood + working title | Intent | Demand | Who owns SERP today | Format |
| ----- | ------------------------------------------------ | -------------- | ------- | --------------------------------------------- | --------------- |
| 80 | "Moving to Oak Hill: the 2026 buyer's guide" | relocate (buy) | ~390/mo | Zillow generic; no local guide; AI cites none | Moving-to guide |
| 50 | "Oak Hill vs Bridgeport: which fits your family" | research → buy | ~140/mo | one dated blog, page two open | Comparison |
| 24 | "Oak Hill elementary schools, ranked" | research | ~90/mo | GreatSchools owns it | School FAQ |
For each row attach the demand evidence (query, volume range from seo/keywords/overview / geo/keywords/search-volume, verbatim related questions, source), why winnable (who owns page one via seo/serp, the portal-page verdict via seo/competitors/relevant-pages, any geo/serp gap and news/search hook), and the suggested angle + local details to include (the maps/search / local/search anchors, commute times, recent development). Lead with the highest scores; briefly note queries checked and discarded so the operator knows the territory was covered. Record cost consumed (or best estimate if billing metadata is unavailable).
Worked example: "moving to Oak Hill" — intent 1.0 (relocate→buy), demand 1.0 (~390/mo per seo/keywords/overview), winnability 0.8 (page one is a generic Zillow community page plus two thin aggregators per seo/competitors/relevant-pages, no local agent guide, and geo/serp names no local source) → 0.8 × 100 ≈ 80, the top opportunity. Contrast "Oak Hill elementary schools": intent 0.5, demand 0.5, winnability 0.5 (GreatSchools owns it) → ~13, skip or fold into the guide.
npx claudepluginhub unifapi-agent/agents --plugin unifapiBenchmarks a real estate agent's Google reviews and local-pack presence against competitors for queries like "realtor [city]" or "homes for sale [neighborhood]". Uses live public SERP and listing data via UnifAPI to quantify gaps in review count, recency, and neighborhood-language relevance.
Pulls local SEO data including SERP results, local pack rankings, business profiles, reviews, citations, audits, geogrid scans, keywords, and AI visibility via LocalSEOData MCP API.
Discovers and ranks local businesses in any neighborhood using Nimble WSAs and web data, returning structured lists with scores, reviews, and an interactive map.