geo-optimization
Generative Engine Optimization (GEO) for AI search visibility. Optimize content to appear in ChatGPT, Perplexity, Claude, and Google AI Overviews. Use when optimizing websites, pages, or content for LLM discoverability and citation.
What this skill does
# GEO: Generative Engine Optimization
Optimize content to appear in AI-powered search engines (ChatGPT, Perplexity, Claude, Google AI Overviews). GEO is about being **parseable, quotable, and authoritative** — not keyword stuffing.
---
## Quick Reference
| Goal | Tactic |
|------|--------|
| Get cited in AI answers | Add specific statistics, quotable facts |
| Appear in comparisons | Create definitive comparison tables |
| Answer user questions | Comprehensive FAQ sections |
| Establish entity | Clear first-paragraph definitions |
| Build authority | Third-party mentions, backlinks, freshness signals |
---
## GEO vs SEO: Key Differences
| Aspect | Traditional SEO | GEO |
|--------|-----------------|-----|
| Goal | Rank on SERPs | Get cited in AI responses |
| Keywords | Exact match matters | Semantic understanding |
| Content style | Can be promotional | Must be factual, neutral |
| Structure | Headers for scanning | Headers + parseable data |
| Links | Backlinks for authority | Citations + entity mentions |
| Freshness | Helpful | Critical (LLMs prefer recent) |
| Format | Long-form wins | Quotable chunks win |
---
## The GEO Audit Checklist
Score each page 0-2 points per item (0=missing, 1=partial, 2=excellent):
### 1. Entity Clarity (Max 10 pts)
- [ ] First paragraph clearly defines what/who the entity is
- [ ] Entity name used consistently throughout
- [ ] Clear category placement ("X is a [type of thing]")
- [ ] Relationship to other known entities stated
- [ ] Wikipedia-style objectivity in tone
### 2. Quotable Facts (Max 10 pts)
- [ ] Specific numbers present (not "many" or "fast")
- [ ] Statistics are current and sourced
- [ ] Claims are concrete and verifiable
- [ ] Key facts in standalone sentences (easy to extract)
- [ ] "By the numbers" or facts section exists
### 3. FAQ Coverage (Max 10 pts)
- [ ] FAQ section exists
- [ ] Questions match how users prompt LLMs
- [ ] Answers are direct and complete
- [ ] FAQ schema markup implemented
- [ ] Covers "what is", "how does", "why", "vs" questions
### 4. Comparison Positioning (Max 10 pts)
- [ ] Comparison tables exist
- [ ] Competitors named explicitly
- [ ] Factual differences highlighted (not just marketing)
- [ ] "Alternative to X" content exists
- [ ] Fair representation (not obviously biased)
### 5. Structural Clarity (Max 10 pts)
- [ ] Clear heading hierarchy (H1→H2→H3)
- [ ] Bullet points for lists
- [ ] Tables for comparisons
- [ ] Short paragraphs (2-4 sentences)
- [ ] Summary/TL;DR at top or bottom
### 6. Authority Signals (Max 10 pts)
- [ ] Author/company credentials stated
- [ ] Customer names/logos (social proof)
- [ ] Case studies with real numbers
- [ ] Third-party mentions/citations
- [ ] "Last updated" date present
### 7. Freshness (Max 10 pts)
- [ ] Page has recent update date
- [ ] Content reflects current year
- [ ] No outdated references
- [ ] Regular content updates
- [ ] News/changelog section exists
**Scoring:**
- 60-70: Excellent GEO readiness
- 45-59: Good, needs some optimization
- 30-44: Fair, significant gaps
- <30: Poor, major overhaul needed
---
## Content Optimization Templates
### Template 1: Entity Definition Page
```markdown
# [Entity Name]
**[Entity Name]** is a [category] that [primary function].
Unlike [alternative/competitor], [Entity Name] offers [key differentiator].
## [Entity Name] by the Numbers
- [Specific stat 1]
- [Specific stat 2]
- [Specific stat 3]
- [Specific stat 4]
## How [Entity Name] Works
[2-3 paragraphs explaining core functionality]
## Who Uses [Entity Name]
[Named customers with context]
## Frequently Asked Questions
### What is [Entity Name]?
[Direct answer in 2-3 sentences]
### How is [Entity Name] different from [Competitor]?
[Factual comparison]
### How much does [Entity Name] cost?
[Pricing info or guidance]
*Last updated: [Date]*
```
### Template 2: Comparison Page (Alternative To)
```markdown
# Best [Competitor] Alternative: [Your Product] (2026)
> **Summary:** [Your Product] is a [category] offering [key differentiators].
> [Customers] report [specific result] compared to [Competitor].
*Last updated: [Date]*
## Why [Users] Look for [Competitor] Alternatives
### Problem 1: [Specific Pain Point]
[Explanation with specifics]
### Problem 2: [Specific Pain Point]
[Explanation with specifics]
## [Your Product] vs [Competitor]: Comparison
| Feature | [Competitor] | [Your Product] |
|---------|--------------|----------------|
| [Feature 1] | [Their approach] | [Your approach] |
| [Feature 2] | [Their approach] | [Your approach] |
| [Feature 3] | [Their approach] | [Your approach] |
## Key Differences
### [Differentiator 1]
[Factual explanation with numbers]
### [Differentiator 2]
[Factual explanation with numbers]
## Customer Results
> "[Quote with specific result]"
> — [Name], [Title], [Company]
## Frequently Asked Questions
### Is [Your Product] a good alternative to [Competitor]?
[Direct answer]
### How does [Your Product] compare to [Competitor] on [key factor]?
[Specific comparison]
### Can I migrate from [Competitor] to [Your Product]?
[Migration info]
## Summary
[Your Product] is a [category] offering [key benefits]. [Customers]
using [Your Product] instead of [Competitor] report [specific results].
*[Your Product] has [credibility stat]. Learn more at [link].*
```
### Template 3: FAQ Page (LLM Optimized)
```markdown
# [Topic] FAQ
Answers to common questions about [topic].
*Last updated: [Date]*
## General Questions
### What is [thing]?
[Thing] is a [category] that [function]. It is used by [who] to [accomplish what].
### How does [thing] work?
[Thing] works by [process]. [Additional detail].
### Who uses [thing]?
[Thing] is used by [user types], including [specific examples like Company A, Company B].
## Comparison Questions
### How is [thing] different from [alternative]?
[Thing] differs from [alternative] in [specific ways]:
- [Difference 1]
- [Difference 2]
- [Difference 3]
### Is [thing] better than [alternative]?
[Thing] is better suited for [use cases] because [reasons].
[Alternative] may be better for [other use cases].
## Pricing & Access
### How much does [thing] cost?
[Pricing information or range]
### Is there a free trial?
[Trial information]
## Technical Questions
### What are the requirements for [thing]?
[Requirements list]
### How do I get started with [thing]?
1. [Step 1]
2. [Step 2]
3. [Step 3]
```
---
## Platform-Specific Optimization
### Perplexity AI
**How it works:** 3-layer reranking system
1. Initial retrieval from web index
2. Relevance scoring
3. Citation selection based on authority + recency
**Optimization tactics:**
- Strong domain authority matters
- Freshness signals critical (update dates)
- Direct answers to questions
- Being cited by other authoritative sources
- Structured data helps parsing
### ChatGPT / SearchGPT
**How it works:** Bing-powered search + LLM synthesis
**Optimization tactics:**
- Bing indexing matters (submit sitemap to Bing)
- E-E-A-T signals weighted heavily
- Conversational content structure
- FAQ format highly effective
- Named entities help recognition
### Google AI Overviews
**How it works:** Google's index + Gemini synthesis
**Optimization tactics:**
- Traditional SEO still matters (ranking helps)
- Featured snippet optimization
- Schema markup (FAQ, HowTo, Product)
- Clear, authoritative content
- Mobile-first indexing
### Claude
**How it works:** Training data + retrieval (when web-enabled)
**Optimization tactics:**
- Quality content in training sources
- Wikipedia mentions help entity recognition
- Technical accuracy valued
- Clear, well-structured prose
- Being cited in authoritative sources
---
## Technical Implementation
### Schema Markup for GEO
**Organization Schema:**
```json
{
"@context": "https://schema.org",
"@type": "Organization",
"name": "Company Name",
"description": "Clear description of what company does",
"url": "https://example.com",
"foundingDatRelated in AI Agents
skill-development
IncludedComprehensive meta-skill for creating, managing, validating, auditing, and distributing Claude Code skills and slash commands (unified in v2.1.3+). Provides skill templates, creation workflows, validation patterns, audit checklists, naming conventions, YAML frontmatter guidance, progressive disclosure examples, and best practices lookup. Use when creating new skills, validating existing skills, auditing skill quality, understanding skill architecture, needing skill templates, learning about YAML frontmatter requirements, progressive disclosure patterns, tool restrictions (allowed-tools), skill composition, skill naming conventions, troubleshooting skill activation issues, creating custom slash commands, configuring command frontmatter, using command arguments ($ARGUMENTS, $1, $2), bash execution in commands, file references in commands, command namespacing, plugin commands, MCP slash commands, Skill tool configuration, or deciding between skills vs slash commands. Delegates to docs-management skill for official documentation.
reprompter
IncludedTransform messy prompts into well-structured, effective prompts — single or multi-agent. Use when: "reprompt", "reprompt this", "clean up this prompt", "structure my prompt", rough text needing XML tags and best practices, "reprompter teams", "repromptception", "run with quality", "smart run", "smart agents", multi-agent tasks, audits, parallel work, anything going to agent teams. Don't use when: simple Q&A, pure chat, immediate execution-only tasks. See "Don't Use When" section for details. Outputs: Structured XML/Markdown prompt, quality score (before/after), optional team brief + per-agent sub-prompts, agent team output files. Success criteria: Single mode quality score ≥ 7/10; Repromptception per-agent prompt quality score 8+/10; all required sections present, actionable and specific.
adaptive-compaction
IncludedAdaptive add-on policy and recovery layer that decides WHEN to compact, prune, snapshot, or fork -- replacing fixed-percent auto-compaction across Claude Code, Codex, and MCP-capable hosts. Trigger on auto-compact timing or damage: "when should I compact", "is it safe to compact now or start a fresh session", "auto-compact fires too early/mid-task", "switching to an unrelated task but the window still has space", "context rot", "answers get worse the longer the session runs", "the agent forgot the plan or my decisions after it summarized", "add a layer on top that manages context without changing the agent", raising autoCompactWindow to give the policy room, or installing/tuning a cross-tool compaction policy or PreCompact hook -- even when "compaction" is never said but the problem is context-window pressure or post-summarization memory loss. Do NOT use to summarize a conversation, build RAG, write a summarization prompt (decides WHEN not HOW), or answer max-context-length trivia.
agent-skill-creator
IncludedCreate cross-platform agent skills from workflow descriptions. Activates when users ask to create an agent, automate a repetitive workflow, create a custom skill, or need advanced agent creation. Triggers on phrases like create agent for, automate workflow, create skill for, every day I have to, daily I need to, turn process into agent, need to automate, create a cross-platform skill, validate this skill, export this skill, migrate this skill. Supports single skills, multi-agent suites, transcript processing, template-based creation, interactive configuration, cross-platform export, and spec validation.
llm-wiki
IncludedUse when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.
skill-master
IncludedAgent Skills authoring, evaluation, and optimization. Create, edit, validate, benchmark, and improve skills following the agentskills.io specification. Use when designing SKILL.md files, structuring skill folders (references, scripts, assets), ingesting external documentation into skills, running trigger evals, benchmarking skill quality, optimizing descriptions, or performing blind A/B comparisons. Keywords: agentskills.io, SKILL.md, skill authoring, eval, benchmark, trigger optimization.