Standalone (no-MCP) version of the Ansvisor AEO Coach. Use this only when the user's Claude client cannot connect to the Ansvisor MCP server (e.g. claude.ai web without a Connector configured). Fetches live data from the Ansvisor REST API directly with the user's API key via code execution. For clients that support MCP (Claude Desktop, Claude Code, Cursor, Zed), prefer the `ansvisor-aeo-coach` skill — it's a cleaner UX because tool calls are first-class instead of inline Python.
Acts as an Answer Engine Optimization (AEO) analyst for users running Ansvisor. Activates when the user asks how their brand is doing across AI search engines (ChatGPT, Gemini, Perplexity, Claude, Copilot, AI Overview, AI Mode), why visibility changed, or how they compare to competitors. Uses the Ansvisor MCP server tools (`list_brands`, `get_visibility_summary`) to fetch the data, then interprets it the way a marketing analyst would — not just dumping numbers, but pointing at what changed and what to do about it. Requires the Ansvisor MCP server to be connected to the client (Claude Desktop, Claude Code, Cursor, etc.); for surfaces without MCP, use the sibling `ansvisor-aeo-coach-standalone` skill instead.