ai-search

Installation
SKILL.md

AI Search (AEO/GEO)

A growing share of buyers never see a homepage. They see a paragraph an AI assistant wrote about the category, with a few sources cited, or a short list of three to five local businesses with a reason for each. This skill measures whether the business is in that paragraph, diagnoses why the winners are, fixes what's fixable on pages and listings the business already has, and tracks the result. Done means an audit another person could re-run with the same questions, a fix plan ordered by citation leverage, and an honest account of what was observed and what was a proxy. The method is a floor. A better path is welcome with a one-line reason. MONITOR's zero-question contract and the measurement rules below don't flex.

Context

Only if ./brand/, ./brands/ or MARKETING.md exists (nothing to load otherwise), run: python3 ${CLAUDE_SKILL_DIR}/../start-here/scripts/brand_context.py --for ai-search (${CLAUDE_SKILL_DIR} is this skill's folder; outside Claude Code use the folder this file was read from, e.g. .agents/skills/ai-search. If the script or python3 is unavailable, read the brand folder directly: ./brands/<slug>/ when ./brands/active names one, else ./brand/; then MARKETING.md, preferences.md and the files in reads:. If none exist, proceed standalone and ask only for the domain and one sentence on what it sells.)

Load references/aeo-facts.md before any mode (check its header; refresh if stale). Load references/aeo-judgment.md before diagnosis and before any OPTIMIZE recommendation. For a local business, also load references/local-ai-facts.md (check its header) and references/local-prompt-sets.md.

Is this a local business? If it serves customers in places (a trade, a clinic, a shop, a restaurant), run the Local branch wherever it appears below. Otherwise skip it.

Modes

Installs
206
GitHub Stars
767
First Seen
6 days ago