aeo-pack-local-services
Skill13 starsChanged 6 months agoMITView on GitHub
Curated prompt pack for local service businesses (plumbers, dentists, lawyers, mechanics, restaurants, contractors, etc.) tracking AEO visibility. 16 prompts covering near-me searches, ratings/reviews, pricing, emergency, trust signals, and specialty filtering. Template variables (service, city, specialty, neighborhood) are filled per workspace. Use when a user is setting up AEO tracking for a local service business, wants a starter prompt set for geographic queries, or asks for prompt ideas for a brick-and-mortar service provider.
In this repository22 other files it gives its agents.
- aeo-ai-overview-simulatorSkill
- aeo-analytics-freeSkill
- aeo-baselineSkill
- aeo-cannibalization-detectorSkill
- aeo-citation-gap-finderSkill
- aeo-competitor-monitorSkill
- aeo-content-freeSkill
- aeo-entity-extractorSkill
- aeo-freshness-decay-trackerSkill
- aeo-grounding-query-mapperSkill
- aeo-initSkill
- aeo-multi-prompt-strategySkill
- aeo-optimizeSkill
- aeo-pack-ai-toolsSkill
- aeo-pack-b2b-saasSkill
- aeo-prompt-frequency-analyzerSkill
- aeo-prompt-question-finderSkill
- aeo-prompt-research-freeSkill
- aeo-reportSkill
- aeo-schemaSkill
- aeo-source-authority-profilerSkill
- aeo-trackSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 58
Add LocalBusiness JSON-LD via aeo-schema to improve machine-readability of the business page.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
AEO Pack: Local Services
Source: github.com/psyduckler/aeo-skills Part of: AEO Skills Suite (v2 prompt packs) Schema: prompt-pack-v1
16 ready-to-track prompts for local service business visibility, covering the journey from "find a provider near me" to "is this one trustworthy?"
Template variables
| Variable | Required | Example |
service | yes | plumber, dentist, lawyer, mechanic, restaurant, electrician |
city | yes | Austin, San Francisco, Brooklyn |
specialty | no | emergency, family, criminal, pediatric |
neighborhood | no | South Congress, Mission District |
How to use this pack
npx skills add psyduckler/aeo-skills --skill aeo-pack-local-servicesThen merge the filled-in prompts from prompts.json into your aeo.config.json. Example for an Austin-area emergency plumbing service:
| Template | Filled |
Best {{service}} in {{city}} | Best plumber in Austin |
Emergency {{service}} {{city}} | Emergency plumber Austin |
{{service}} reviews {{city}} | plumber reviews Austin |
How much does a {{service}} cost in {{city}}? | How much does a plumber cost in Austin? |
Why these prompts
Local-service AI search splits differently than B2B:
- Proximity + service is the dominant pattern. "best plumber in Austin" is the canonical query.
- Trust signals (reviews, licensure, "trustworthy") matter more than in B2B — high cost of choosing wrong.
- Urgency matters (emergency / open now) — Gemini's grounding behavior shifts for time-sensitive intent.
- Educational queries ("what to expect from a {{service}} visit") drive top-of-funnel awareness even when the user isn't actively shopping.
Notes
- This pack pairs with local SEO best practices: Google Business Profile, NAP (Name/Address/Phone) consistency, review acquisition. AEO visibility tracks the AI-Overview side; classical local SEO drives the citations Gemini surfaces.
- Add
LocalBusinessJSON-LD via aeo-schema to improve machine-readability of the business page. - Suggested first-baseline scope: 8–10 prompts × 20 samples = ~$0.05 estimated cost.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.