generative-engine-optimization
When the user wants to optimize for AI search visibility (ChatGPT, Claude, Perplexity, AI Overviews). Also use when the user mentions "GEO," "AEO," "generative engine optimization," "AI search visibility," "LLM optimization," "GitHub GEO," "Grokipedia," "optimize for ChatGPT," "AI Overviews," "Bing Copilot," "Yandex AI," "Perplexity optimization," "GEO strategy," or "AI search optimization." For third-party publishing strategy (which platforms to use), use parasite-seo. For GitHub repos, README, and Awesome lists, use github. For Medium.com only, use medium-posts. For Grokipedia edits, use gro
npx skills add kostja94/marketing-skills --skill geo --agent cursor
Same command for any agent — swap --agent for claude-code, codex, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Strategies: GEO (Generative Engine Optimization) Guides GEO/AEO strategy for AI search visibility. GEO optimizes content for ChatGPT, Claude, Perplexity, and AI search summaries (Google AI Overviews, Bing Copilot, Yandex Search with AI)—getting cited in AI-generated answers rather than ranking in traditional SERPs. See **serp-features** for AI search as SERP features; **featured-snippet** for snippet optimization that overlaps with AI Overviews. **When invoking**: On **first use**, if helpful, open with 1-2 sentences on what this skill covers and why it matters, then provide the main output. On **subsequent use** or when the user asks to skip, go directly to the main output. ## Scope - **GEO** = Generative Engine Optimization - **AEO** = Answer Engine Optimization - **LLMO** = Large Language Model Optimization - **AIO** = Artificial Intelligence Optimization All refer to the same goal: visibility in AI assistant responses. ## GEO vs. SEO | Dimension | SEO | GEO | |-----------|-----|-----| | **Goal** | Rankings in search results | Citations in AI answers | | **User path** | Click → visit → convert | Answer in-place; may not visit | | **Content** | Full page optimization | Clear, c
- Scope
- GEO vs. SEO
- AI Search Platforms (SERP Features + Standalone)
- How GEO Works (RAG & Search Supply)
- Retrieval Supply Types
- Platform Retrieval & Implications
- AI Crawlers & Discovery
- Content Best Practices
- Article-Level GEO
- Parasite SEO & High-Authority Platforms
- Tools
- Key Insight
- Output Format
- Related Skills
What does the generative-engine-optimization skill do?
When the user wants to optimize for AI search visibility (ChatGPT, Claude, Perplexity, AI Overviews). Also use when the user mentions "GEO," "AEO," "generative engine optimization," "AI search visibility," "LLM optimization," "GitHub GEO," "Grokipedia," "optimize for ChatGPT," "AI Overviews," "Bing Copilot," "Yandex AI," "Perplexity optimization," "GEO strategy," or "AI search optimization." For third-party publishing strategy (which platforms to use), use parasite-seo. For GitHub repos, README, and Awesome lists, use github. For Medium.com only, use medium-posts. For Grokipedia edits, use gro
How do I install it?
Run `npx skills add kostja94/marketing-skills --skill geo --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From kostja94/marketing-skills, a repository with 848 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.