Individual skill

local-ai-visibility

Use this skill when a business serves specific towns or suburbs and needs to know where AI recommends it — "do we show up in this suburb," "named in one city and invisible in the next," "which service areas are the gap." Measures AI answers town by town, records map-pack and written-answer presence separately, and produces a ranked gap map of where rivals get named instead.

skills/huxley-peckham/local-ai-visibility/SKILL.md

Read pinned source

Source commit 5d786aad0c7b2ca59b1abf1f601f9407ca261996

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Not checked yet
Last checked
Nov 11, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
237
Repository last updated
Oct 20, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

Use when a business serves specific towns, suburbs, or service areas and needs to know where AI recommends it. Produces a town-by-engine presence grid and a ranked list of the gaps where rivals get named instead.

## Build the town matrix

List every town the business genuinely serves, not just the head city. Phrase each test question the way a local buyer types it — the service plus the place, in plain words. Ask per town, per engine. Results from the head city predict nothing about the suburb next to it: answer engines assemble local answers from thin, hyper-local evidence, and a brand can be the answer in one postcode and absent one over.

## Record the local pack separately

For engines that lean on map results, capture presence in the map pack and presence in the written answer as two signals. They move for different reasons: the pack follows profile completeness, reviews, and proximity; the prose follows mentions, citations, and content. A brand can hold one and not the other, and the fix for each is different work.

## Make the gap map

For every town-and-engine cell where the brand is absent, record who is named instead, in the engine's own words. Rank the gaps by demand — the search volume behind the question where it is known, population as the proxy where it is not. The output is a ranked list: town, question, who wins it now, and the quoted evidence.
Back to top