← Plugin catalog
Data & Analytics

Advan Research REI

Advan Research v1.0.0

Real Estate Location Intel

Create a free account to save this plugin.

From the developer

Not specified in the available declarations: capabilities, limitations, pricing & account requirements.

Sources & dates

Developer declarations; not independently tested. Listing last checked Nov 21, 2026. Package observed Nov 20, 2026.

View package source →

Description

From the marketplace listing

Turn foot traffic and demographic data into actionable real estate insights. Analyze property performance, compare locations and competitors, understand trade areas and customer profiles, evaluate tenant opportunities, and identify strong sites for retail brands. Built for brokers, landlords, and site selectors who want data-backed answers for leasing, acquisition, renewal, and location decisions.

Language: English · Automatically detected from descriptions.

What changed

Similar plugins

Finding similar plugins… Results will appear here automatically.

Browse plugins →

Files & skills

File archives

Plugin package10 files · 34.9 KBBrowse files →
Skill instructions
advan-rei-design-system12.3 KB

View saved version →

---
name: advan-rei-design-system
description: >
  The authoritative design token reference for all Advan REI visual output —
  color palette, typography, spacing, border radius, widget structure, and
  component patterns. Read this skill before writing any HTML, CSS, or chart
  code for Reina. The rei-data-visualization skill references this skill as a
  prerequisite. Do not invent colors, font sizes, or layout patterns that
  aren't defined here — always derive from these tokens, which are extracted
  directly from the Advan REI design library.
---

# Advan REI Design System

This document defines every design token and structural pattern used in the
REI platform. All visual output Reina produces — charts, tables, widgets,
HTML artifacts — must conform to these specifications. All tokens are
extracted from the official Advan REI design library HTML.

---

## Foundation: Dark Theme

The REI interface is a dark navy application. Every visual artifact must use
this palette as its base — never white or light backgrounds.

| Token | Hex | Use |
|-------|-----|-----|
| `--bg-deepest` | `#0E1847` | Page / app background (outermost) |
| `--bg-deep` | `#101B4D` | Deep layer behind widgets, export drawers |
| `--bg-widget` | `#162465` | Widget body, data table cells |
| `--bg-section-hd` | `#1B2B7A` | Section heading rows within widgets |
| `--bg-table-hd` | `#26326E` | Table header rows |
| `--bg-subtle` | `#28325F` | Row dividers, subtle borders |

---

## Color Tokens

### Brand Blues (UI Structure)

| Token | Hex | Use |
|-------|-----|-----|
| `--blue-primary` | `#0061F3` | Interactive elements, modal nav, CTA buttons |
| `--blue-dark` | `#0F53C7` | Hover state for blue-primary |
| `--blue-light` | `#3F8CFD` | Highlighted button states |
| `--blue-lighter` | `#428AF5` | Secondary highlights |
| `--blue-ghost` | `#DBECFF` | Very subtle tint backgrounds |

### Extended Blues (Demographics / Panels)

| Token | Hex | Use |
|-------|-----|-----|
| `--bg-panel` | `#0B41AB` | Panel backgrounds |
| `--bg-panel-hd` | `#0E3894` | Panel header areas |
| `--bg-panel-deep` | `#112369` | Deep panel layers |
| `--bg-demo-cat` | `#1A2B7B` | Demographics category header rows |
| `--bg-demo-row` | `#131E58` | Demographics odd rows |
| `--bg-demo-alt` | `#132C61` | Demographics even rows (alternating) |

### Modal / Settings Shell

| Token | Hex | Use |
|-------|-----|-----|
| `--modal-nav` | `#0061F3` | Left nav column + right action column |
| `--modal-body` | `#0256D4` | Center content area |
| `--modal-btn` | `#3180F6` | Apply / Save / Reset buttons |

---

## Property Colors

Each property in a multi-property comparison is assigned one color track.
Always assign in order: P1 → cyan, P2 → violet, P3 → green, P4 → pink.
Never swap these assignments — cyan always means the first/primary property.

### Property 1 — Cyan

| Shade | Token | Hex |
|-------|-------|-----|
| Primary | `--cyan-primary` | `#17AAB3` |
| Dark | `--cyan-dark` | `#12888F` |
| Bright | `--cyan-bright` | `#00EEFA` |
| Muted | `--cyan-muted` | `#509EAA` |
| Bar / accent | `--cyan-bar` | `#46E2EF` |
| S1 (lightest) | `--cyan-s1` | `#A5F7FC` |
| S2 | `--cyan-s2` | `#39DBE3` |
| S3 | `--cyan-s3` | `#07A5AD` |
| S4 (darkest) | `--cyan-s4` | `#0B4D6D` |

Widget header background: `--cyan-primary` (`#17AAB3`), white text.
Value box background: `#17AAB3`.

### Property 2 — Violet

| Shade | Token | Hex |
|-------|-------|-----|
| Primary | `--violet-primary` | `#713DC5` |
| Dark | `--violet-dark` | `#4E2A89` |
| Bright | `--violet-bright` | `#AB7DF6` |
| Muted | `--violet-muted` | `#8240EA` |
| Bar / accent | `--violet-bar` | `#CAA8FF` |
| S1 | `--violet-s1` | `#D7C0FD` |
| S2 | `--violet-s2` | `#AB8AE1` |
| S3 | `--violet-s3` | `#8055C4` |
| S4 | `--violet-s4` | `#541FA8` |

### Property 3 — Green

| Shade | Token | Hex |
|-------|-------|-----|
| Primary | `--green-primary` | `#17B36A` |
| Dark | `--green-dark` | `#107D4A` |
| Bright | `--green-bright` | `#44E298` |
| Muted | `--gre

Preview of the first 4,000 characters. Read full instructions →

foot-traffic-analysis7.17 KB

View saved version →

---
name: foot-traffic-analysis
description: >
  Step-by-step workflow for analyzing foot traffic at a single retail property
  using Advan REI MCP data. Use this skill whenever Reina is asked about a
  property's traffic performance, visit trends, dwell time, visit frequency,
  or general location performance. Trigger on phrases like "how is [property]
  performing", "show me traffic for [location]", "what's the foot traffic at
  [address]", "how have visits trended", "is this center busy", "pull the
  traffic data for", or any request that centers on understanding a specific
  property's visitor activity — even if the user doesn't say "foot traffic"
  explicitly. When in doubt, use this skill before answering.
---

# Foot Traffic Analysis Workflow

A single-property traffic analysis has four stages: resolve the property,
pull core metrics, benchmark against the market, and synthesize. The stages
build on each other — don't skip ahead or collapse them into one big query.

---

## Stage 1: Resolve the Property

Properties in the REI platform are identified by three fields: **ALI** (the
primary unique identifier), **location name**, and **company name**. If the
user has referenced any of these — or if they've been established earlier in
the conversation — use them directly and proceed to Stage 2.

If the property is ambiguous — a partial name, an address, or a loose
description like "the Target on Route 9" — use `search` to find it. Present
the top results concisely and ask the user to confirm before pulling data.
Don't guess and proceed; a misidentified property produces confidently wrong
analysis.

Once confirmed, carry the ALI, location name, and company name forward. You'll
reuse them across every tool call in this workflow.

---

## Stage 2: Pull Core Metrics

Call these three tools in order. Each one adds a layer to the story.

**Date range:** Use whatever date range the user has selected in the UI, or
whatever period they've specified in their question. Only ask about the date
range if it's genuinely ambiguous from context.

### 2a. Traffic Summary — the volume story

Call `traffic-summary` with the resolved property identifiers.

Key outputs to capture:
- Total visit count for the period
- Month-over-month and year-over-year trend
- Any notable spikes or drops

### 2b. Dwell Time — the engagement story

Call `dwell-time` for the same property and date range.

Dwell time tells you whether visitors are spending meaningful time or just
passing through. A high-traffic property with low dwell time often signals
convenience-oriented shopping or a pass-through layout; higher dwell suggests
destination behavior or a strong tenant mix.

### 2c. Visit Frequency — the loyalty story

Call `visit-frequency` for the same property and date range.

Visit frequency distinguishes properties that draw the same loyal customers
repeatedly from those that rely on a constant stream of new visitors. A
grocery-anchored center will typically show higher frequency than a fashion
or home goods property — keep that in mind when interpreting the result.

---

## Stage 3: Benchmark Against the Market

A traffic number without context is just a number. Call `ranking` to place
the property within its submarket or category using the same date range.

The ranking result gives you where this property sits relative to peers and
whether it's gaining or losing ground. Weight this step based on what the
user actually asked — if they want to know if the property is strong, lead
with rank; if they're just asking how busy it is, one sentence is enough.

---

## Stage 4: Synthesize and Present

### Search for real-world context

Before writing the narrative, do a targeted web search for anything that
could explain or color what the data is showing. You're looking for things
like: recent anchor tenant changes or closures, new competition that opened
nearby, local economic conditions, a major employer moving in or out, weather
events or regional disruptions, renova

Preview of the first 4,000 characters. Read full instructions →

rei-data-visualization12.4 KB

View saved version →

---
name: rei-data-visualization
description: >
  Guidance for visualizing Advan REI data as charts, graphs, and maps within
  Reina's responses. Use this skill whenever Reina is about to produce any
  chart, graph, or visual representation of REI data — traffic trends, demographic
  breakdowns, rankings, visit patterns by hour or day, or trade area maps.
  Also use when the user explicitly asks to "chart", "graph", "visualize",
  "show me a chart of", or "map" any REI data. Always read this skill before
  writing visualization code or choosing a chart type for REI data.
---

# REI Data Visualization

This skill governs how Reina visualizes data from REI queries. It covers
when to visualize, what format to produce, how to style output, and which
chart type fits each data type.

---

## Step 1: Read the Design System

Before writing any visualization code, read the `advan-rei-design-system`
skill. It defines the color palette, typography, dark theme, component
patterns, and spacing that all REI visualizations must follow. This skill
adds chart-specific guidance on top of that foundation — it does not
replace it.

---

## Step 2: Decide Whether to Visualize

Not everything warrants a chart. Use this as a guide:

**Visualize when:**
- Showing a trend over time (traffic by month, YoY comparison)
- Comparing a property or tenant across multiple peers simultaneously
- Displaying a distribution (demographics by income band, visits by hour)
- The pattern or shape of the data is the point — not just a single number
- The user explicitly asks for a chart or visualization

**Use a table instead when:**
- Exact values matter more than the pattern (a benchmarking summary, a
  ranked list of properties with specific metrics)
- There are fewer than four data points — a chart adds visual overhead for
  little gain
- The user is likely to copy figures into another document or report

**Use prose instead when:**
- The finding can be stated in one clear sentence
- There is only one data point or metric being communicated
- A chart would slow the user down, not help them

When in doubt, lead with the answer in prose and offer to chart it.

---

## Step 3: Choose the Output Format

**HTML artifact (interactive):** Use when the user is exploring data in a
conversation, the chart benefits from hover states or tooltips showing exact
values, or the output is a standalone deliverable they'll reference during
the session.

**Static image (SVG or PNG):** Use when the user asks to export, wants to
include the chart in a report or presentation, or the context is clearly
a one-time view rather than an interactive reference.

When the request is ambiguous, default to HTML. If the user later wants to
export, offer the static version.

---

## Step 4: Chart Type by Data Type

### Traffic Trend Lines

**Use:** Line chart with time on the x-axis and visit count on the y-axis.

- Plot monthly data points as the default granularity. Offer weekly if the
  user wants a more granular view or is analyzing a short date range.
- If showing YoY, use two lines (current period vs. prior period) in
  distinct colors from the design system palette.
- Mark notable events directly on the chart when they're known — anchor
  closures, renovations, seasonal peaks — as labeled vertical reference lines.
- Always show the data range in the chart subtitle, not just the title.
- Don't start the y-axis at zero if the variation is small relative to the
  absolute level — truncate to show the trend clearly, but label the axis
  origin so the user knows.

### Demographic Breakdowns

**Use:** Horizontal bar chart for ranked categories (income bands, age
cohorts, lifestyle segments). Donut or pie chart only for simple two- or
three-part compositions (e.g., a dominant segment vs. all others) — never
for more than five slices.

- Order bars by value descending unless the categories have a natural order
  (age cohorts, income bands) — in those cases preserve the natural order.
- For income and

Preview of the first 4,000 characters. Read full instructions →

rei-methodology24.1 KB

View saved version →

---
name: rei-methodology
description: >
  Reference for explaining Advan REI's data methodologies consistently and
  accurately. Use this skill whenever a user asks how any REI metric is
  calculated, what a term means, how the underlying data is collected, what
  the data's limitations are, how accurate the panel is, how trade areas are
  built, how demographics are attributed, how rankings are scored, or anything
  about how the data works rather than what it shows. Trigger on phrases
  like "how is this calculated", "what does [metric] mean", "how do you define
  a visit", "where does this data come from", "how accurate is this", "what's
  the methodology", "how are trade areas defined", "how current is the data", "what's the
  difference between [X] and [Y]", or any question that is fundamentally about
  the data and method rather than the data and a specific property. Also
  trigger when a user challenges or questions the validity of a result —
  methodology context is often the right response before escalating to support.
---

# REI Methodology Reference

This skill exists to ensure Reina explains Advan's methodologies consistently,
accurately, and at the right level of depth for each user. The core principle:
answer from this reference first, calibrate depth to the audience, and
escalate to support when a question goes beyond what's here.

---

## Calibrating to the Audience

Before explaining a methodology, read the user's question for signals about
their technical depth.

**Non-technical (broker, leasing agent, asset manager):** Lead with a plain-
language analogy or one-sentence explanation. Skip the statistical detail
unless they ask. The goal is enough understanding to trust and use the data,
not to replicate the methodology.

**Technical (data scientist, research analyst, GIS professional):** Go deeper.
Cover the underlying measurement approach, known limitations, and where to
find further documentation. These users will ask follow-up questions and want
precise language.

**Mixed audience or unknown:** Lead with the plain-language version, then
offer to go deeper: *"Want me to walk through the technical details of how
that's measured?"*

---

## The Data Foundation: Advan's Mobile Device Panel

All REI metrics derive from the same underlying source: a panel of opted-in
mobile devices whose location signals are collected, processed, and aggregated
to generate insights about physical locations.

**Panel composition:** Advan observes over 100 million U.S. devices. After
applying strict data quality filters to remove noise and suspect signals, the
working panel represents approximately 20% of the U.S. population and is
demographically diverse across geography, age, and income. The panel is
sourced via SDK partnerships and collects signals through a combination of
GPS, Wi-Fi, and SDK-based location data.

**Privacy and compliance:** All data is aggregated and anonymized before
delivery. No individual device is identifiable in any REI output. Advan
complies with applicable opt-in requirements — devices are included only
where users have consented to location data collection through the apps
on their devices.

**Plain-language explanation for non-technical users:**
> "Advan's data comes from a large panel of mobile devices whose owners have
> opted in to share their location through the apps on their phones. After
> filtering out low-quality signals, the panel represents about 1 in 5 U.S.
> consumers and is structured to reflect the broader population across
> geography and demographics."

---

## Data Quality and Accuracy

When users ask how Advan ensures its data is accurate or how it's been
tested, this is a selling point — answer it directly and confidently.

**Independent signals, not calibrated to a benchmark:** Advan's data
produces its own independent signals rather than being calibrated against
a single external ground truth source. This means the data reflects what
the panel actually observes, without being sh

Preview of the first 4,000 characters. Read full instructions →

retailer-footprint14.6 KB

View saved version →

---
name: retailer-footprint
description: >
  Workflow for comparing a subject property to a retailer's or category's
  existing location footprint using Advan REI's retailer footprint endpoint.
  The endpoint aggregates all of a retailer's or category's locations within
  a defined radius of the subject site and compares them across foot traffic
  variables, demographics, shared customers, and demographic match score.
  Use this skill whenever a user wants to know how a property compares to a
  retailer's typical location, whether a site fits a retailer's footprint,
  how similar a candidate site is to where a retailer already succeeds, or
  wants to evaluate a retailer's presence in a market area. Trigger on
  phrases like "how does this site compare to [retailer]'s locations",
  "does this fit [retailer]'s footprint", "retailer footprint", "how does
  this property benchmark against [retailer]", or any request that involves
  comparing a site to a specific retailer's or category's existing locations.
  Also trigger as part of site selection when a specific retailer is named.
---

# Retailer Footprint Workflow

This skill has two modes depending on whether the user has a subject site:

- **Site comparison mode:** A subject site is provided. Compare it against
  the retailer's or category's nearby locations to assess fit.
- **Nationwide profile mode:** No subject site. Summarize the retailer's or
  category's footprint nationally, with the option to compare across
  geographies.

Determine the mode from context before proceeding. If a subject site has been
established earlier in the conversation, default to site comparison mode. If
the user is asking about a retailer's footprint generally — "what does
[Retailer]'s typical location look like?", "how does [Retailer] perform
nationally?", "walk me through [Retailer]'s footprint" — use nationwide
profile mode.

---

## Mode A: Site Comparison

### Step 1: Confirm the Inputs

Two inputs are required before calling the endpoint. If either is missing,
ask — don't proceed with assumptions.

**Subject site:** Resolve using ALI, location name, and company name as usual.

**Retailer or category:** Who are we comparing against? This could be a
specific brand (Trader Joe's, TJ Maxx) or a broader category (grocery,
off-price apparel, fitness). If the user named one, use it. If the request
is ambiguous — "how does this compare to similar retailers" — ask them to
specify before proceeding.

**Date range:** Use the UI selection or whatever the user specified.

**Distance:** Default is 100 miles. Don't change it yet — Step 2 will
determine whether an adjustment is warranted after seeing how many locations
the endpoint returns.

---

## Step 2: Call the Endpoint and Assess the Footprint Size

Call the retailer footprint endpoint with the subject site, retailer/category,
100-mile radius, and date range.

Before interpreting the results, check how many locations were returned.
Footprint size directly affects how reliable the aggregate comparison is.

### Too few locations (fewer than 5)

A comparison built on fewer than 5 locations is statistically fragile — one
unusual store can skew the entire aggregate. Flag this to the user and
recommend widening the radius before drawing conclusions.

> "The 100-mile radius only captured 3 [Retailer] locations, which may not
> give a reliable picture of their typical footprint. I'd suggest widening
> to 150 or 200 miles for a more stable comparison — want me to rerun it?"

Don't present the comparison results as meaningful if the location count is
this low unless the user explicitly wants to proceed anyway.

### Healthy footprint (5–30 locations)

This is the reliable range. Proceed to interpretation.

### Large footprint (more than 30 locations)

A large footprint isn't necessarily a problem — a national retailer with
dense coverage may legitimately have 50+ locations in range. But it's worth
flagging that the aggregate is averaging across a wide geography 

Preview of the first 4,000 characters. Read full instructions →

site-selection12.2 KB

View saved version →

---
name: site-selection
description: >
  Structured workflow for evaluating one or more candidate retail locations
  using Advan REI foot traffic, trade area, competitive, and cross-shopping
  data. Use this skill whenever a user is assessing whether a site is a good
  fit for a retailer or tenant, comparing multiple candidate locations,
  evaluating market demand at a specific address, or analyzing cannibalization
  risk from a nearby existing store. Trigger on phrases like "should we open
  here", "evaluate this site", "compare these locations", "is this market
  viable", "how does this site stack up", "would this cannibalize our
  existing store", "what's the co-tenancy like", or any request that frames
  a location decision. Also trigger when a broker, retailer, or developer
  asks about a site's potential without using explicit site selection language.
---

# Site Selection Workflow

Site selection answers a decision question: is this a good location, and for
whom? The workflow is data-driven but ends with a directional take — not just
a data dump, but a read on what the numbers mean for the decision at hand.

The workflow has two modes depending on what the user is evaluating:

- **Single site:** Full analysis of one candidate location.
- **Multi-site comparison:** Run the same analysis for each site, then
  synthesize a side-by-side at the end.

Both modes follow the same stages. For multi-site, run all stages for each
location before moving to synthesis.

---

## Before You Start: Orient the Request

Before pulling data, make sure you understand three things. You may already
have them from context — if so, proceed. If not, ask one focused question
rather than a list.

1. **What location(s) are being evaluated?** An address, a named property, a
   market area?
2. **Is there a specific retailer or tenant in mind?** This drives the
   co-tenancy and cannibalization steps. If no retailer is specified, those
   steps are still useful but framed more generally.
3. **What's the decision?** Opening a new store, evaluating a lease, advising
   a client, underwriting a development? The answer shapes what you emphasize
   in the synthesis.

---

## Stage 1: Resolve the Location(s)

If the user named a specific existing property, use ALI, location name, and
company name as usual. If they provided an address or a general description
of a candidate site, use `search` to find the closest matching property or
reference location. Confirm before proceeding if there's any ambiguity.

For multi-site comparisons, resolve all locations before moving to Stage 2.

---

## Stage 2: Subject Site Performance

If the candidate site is an existing property with traffic data (an occupied
center, a current tenant location), pull `traffic-summary` for it. This
establishes baseline performance at this specific location and gives the user
a sense of what the site has historically attracted.

If the site is vacant, a raw address, or a new development with no existing
traffic history, skip this step and note it. The trade area and competitive
context in later stages will carry the location assessment.

Use the date range from the UI or as specified by the user.

---

## Stage 3: Trade Area

Call `trade-area` using the same parameters established in any current session
trade area settings, or default to the closest 70% of visitors if no setting
is available and the user hasn't specified otherwise.

This tells you who is realistically accessible from this location. Capture:
- Approximate size (radius or drive time)
- The geographic shape — is it symmetric, or constrained by highways, water,
  or dense competition on one side?

You don't need to run the full demographic deep-dive here unless the user
asked for it — that's covered in a standalone trade-area-analysis. For site
selection, the key output is the catchment footprint and a top-line
demographic read (median HHI, dominant age cohort) to assess fit with the
intended tenant.

---

## Stage 4: Competi

Preview of the first 4,000 characters. Read full instructions →

trade-area-analysis7.1 KB

View saved version →

---
name: trade-area-analysis
description: >
  Workflow for defining and analyzing the trade area of a retail property using
  Advan REI mobile visitor origin data. Use this skill whenever a user asks
  where a property's customers are coming from, how far people travel to visit
  a location, what the catchment area looks like, or anything about the
  geographic reach of a property. Also trigger when a user asks about trade
  area as part of a site selection, leasing, or competitive analysis — even if
  they don't use the phrase "trade area" explicitly. Phrases like "where are
  visitors coming from", "how far do customers drive", "what's the catchment",
  "customer origin", or "who is in the surrounding area" should all trigger
  this skill. Works equally well as a standalone analysis or as a follow-on
  to foot traffic data.
---

# Trade Area Analysis Workflow

The trade area analysis answers a different question than foot traffic: not
how many people visit, but *where they come from*. The output is geographic —
a picture of the real catchment area built from actual visitor origin data,
not assumed drive-time rings.

The workflow has four stages: resolve the property, pull the trade area and
characterize its size, layer in a demographic snapshot, and synthesize with
real-world context.

---

## Stage 1: Resolve the Property

Same as foot traffic. If the user has already provided or confirmed an ALI,
location name, and company name — or if these were established earlier in the
conversation — carry them forward and proceed.

If the property is ambiguous, use `search` to find it, present the top
results, and confirm before pulling data.

---

## Stage 2: Pull the Trade Area

Call `trade-area` with the resolved property identifiers.

**Parameters:** Determine the threshold in this order:

1. **User specified it in the conversation** (e.g., "show me the 50% trade
   area", "use the 80% catchment") → use that, regardless of app settings.
2. **User is in the REI app and hasn't specified** → use whatever threshold
   they have configured in their trade area settings.
3. **No app, no specification** → default to the closest 70% of visitors.

**Date range:** Use the period the user has selected in the UI, or whatever
they've specified. Only ask if it's genuinely unclear.

### Characterize the size

The trade area is defined by where visitors actually originate, not by an
artificial ring — but users need a tangible sense of scale. From the returned
data, derive and report the approximate size in one of these terms, whichever
is most natural given the geography:

- **Radius:** "The trade area extends roughly X miles from the property"
- **Drive time:** "Most visitors are within a Y-minute drive"
- **Both:** Use both when the shape is notably asymmetric or the market
  warrants it (e.g., a coastal or highway-adjacent location where drive time
  and radius diverge meaningfully)

If the trade area is unusually compact or unusually large relative to what
you'd expect for the property type, flag it — it may reflect a dense urban
setting, strong competition nearby, or a destination-oriented tenant mix.

---

## Stage 3: Demographic Snapshot

Call `demography` for the trade area using the same property and date range.

By default, surface a concise top-line snapshot — enough to characterize
who's in the catchment without overwhelming the response. Focus on the
signals most relevant to a real estate or retail professional:

- Median household income (and whether it skews upper/lower relative to
  the metro)
- Dominant age cohort(s)
- One or two standout lifestyle or psychographic segments if they're
  meaningfully concentrated

End the snapshot with a natural offer to go deeper:

> "Want me to break this down further by income band, age distribution, or
> lifestyle segment?"

Don't pull `demography-categories` unless the user asks for the full
breakdown — it's there for drill-down, not the default view.

---

## Stage 4: Synthesize and Present

Preview of the first 4,000 characters. Read full instructions →

void-analysis7.21 KB

View saved version →

---
name: void-analysis
description: >
  Workflow for identifying tenant candidates that would fit a vacancy or
  underrepresented category at a retail center, using Advan REI's void
  analysis endpoint enriched with traffic health and expansion signal data.
  Use this skill whenever a user asks what tenants would work at a center,
  what's missing from a property's tenant mix, who should fill a vacancy,
  what categories are underrepresented, or whether a specific retailer type
  would be a good fit. Trigger on phrases like "what tenants would work here",
  "who should fill this space", "what's missing from this center", "void
  analysis", "tenant candidates", "what categories make sense here", or any
  request about filling a vacancy or improving a center's tenant mix.
---

# Void Analysis Workflow

The void analysis endpoint does the core analytical work — it returns tenant
candidates ranked by dynamic distance, cannibalization risk, and demographic
match. This skill's job is to gather the right parameters before calling it,
filter out candidates that don't belong in a retail center context, enrich
the top results with real-world health and expansion data, and present the
output in a way that's actually useful for a leasing decision.

---

## Step 1: Gather Parameters

Before calling the endpoint, confirm two things. If either is missing from
the conversation, ask — these directly affect the quality of the results.

**Vacancy size:** What is the approximate square footage of the space? This
is the most important filter. A 1,200 sq ft inline space and a 45,000 sq ft
anchor box should return completely different candidate sets. If the user
hasn't specified, ask before proceeding.

**Category preferences or exclusions (optional):** Has the user indicated
they're looking for a specific category (food & beverage, fitness, soft
goods) or want to exclude something? If so, note it — you'll apply it when
filtering results. If no preference is stated, proceed with the full results
and apply the standard retail center filter described in Step 3.

Also confirm the property using ALI, location name, and company name as
usual.

---

## Step 2: Call the Void Analysis Endpoint

Call `void-analysis-api` with the resolved property identifiers and vacancy
size parameter. Use the date range from the UI or as specified by the user.

The endpoint returns a ranked list of tenant candidates scored on:
- **Dynamic distance** — how far the candidate's typical locations are from
  this trade area's profile
- **Cannibalization risk** — likelihood of pulling from an existing nearby
  location of the same brand
- **Demographic match** — how well the trade area's visitor profile aligns
  with the candidate's typical customer base

---

## Step 3: Filter for Retail Center Appropriateness

The endpoint returns candidates across a broad range of categories. Before
presenting results, remove any candidates that don't belong in a traditional
retail center context. Categories to omit by default:

- Auto dealers, car washes, and auto service
- Hotels and lodging
- Hospitals, urgent care, and large medical facilities (small-format urgent
  care or dental that fits inline retail is fine)
- Gas stations and fuel retailers
- Industrial, warehouse, or self-storage uses
- Large-format government or civic uses

Use judgment for edge cases. A drive-through-only concept with no inline
presence, for example, may not fit a traditional center even if it scores
well on demographics. If the user has specified a category preference,
apply that filter here too — prioritize their stated criteria over the
default list.

---

## Step 4: Filter by Vacancy Size

From the filtered results, narrow to candidates whose average store footprint
is compatible with the vacancy. A reasonable match range is ±30% of the
vacancy size unless the user specifies otherwise.

Flag if the vacancy size is unusual — a very large anchor box or a very
small kiosk-scale space may return a thin candidate 

Preview of the first 4,000 characters. Read full instructions →

Package details

Publisher declarations from the archived package. These are separate from our research and the live service's terms.

Package author
Advan Research

Package observed Nov 20, 2026.

Technical details
First seen
Oct 1, 2026 · 18:00 UTC
Last seen
Nov 21, 2026 · 06:00 UTC
Collection status
Collected

plugin_asdk_app_6aa8203d5a04819195420ba31e115000

Download plugin data (JSON)

Plugin details: freshly prepared. Prepared . Refreshed when plugin data changes or after 6 hours. Your account and Follow status are live.