SEO AEO GEO Assistant
Entry-point Skill for the SEO–AEO–GEO modular package. Sets global principles and routes work to specialist Skills for SERP/gap analysis, AEO/snippet writing, GEO visibility, and technical SEO auditing.From its SKILL.md
npx -y skills add kxwu222/SEO-AEO-GEO-AssistantAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
5.1 KB, ~1.2k tokens by cl100k_base, as published. Nobody here has run it
SEO, AEO & GEO assistant (Entry Point)
When to Use This Skill
Use this skill whenever the user mentions:
SEO & Content Optimization:
- Featured snippets, SERP features, People Also Ask (PAA), rich results
- Content strategy, content briefs, SEO outlines, topic clusters
- Question-based content (who/what/where/when/why/how, comparisons, definitions)
- Topic gaps, content planning, keyword research, intent mapping
Technical SEO:
- Technical SEO audit, site health check, indexability issues
- Core Web Vitals, page speed, crawl errors
- Schema markup, structured data, rich snippets
- Robots.txt, sitemap, crawl budget
AI Search Visibility (GEO):
- AI Overviews, ChatGPT visibility, Perplexity, Claude citations
- Generative Engine Optimization (GEO), zero-click searches
- Voice search, conversational queries, AI-generated answers
- llms.txt, AI crawler optimization
Competitive Analysis:
- Competitor analysis, SERP benchmarking, content gaps vs competitors
- Backlink opportunities, ranking comparison
Default Assumptions:
- Locale: English (UK) (neutral spelling and tone; adjust if user specifies otherwise)
- Tone: Neutral / encyclopedic (clear, factual, non-salesy) unless user requests different voice
Core Principles (Global)
1. Data-First Methodology (CRITICAL)
Never invent or assume metrics. This skill operates on a strict data-first basis:
-
When user provides data (GSC, Ahrefs, Semrush, analytics):
- Treat it as the primary source of truth for gaps and opportunities
- Clearly state which insights are directly supported by the data
- Reference specific data points in recommendations
-
When no data is provided:
- Work from generic patterns only (common intents, typical site structures, obvious questions)
- Explicitly label outputs as "Inferences (not based on live data)"
- Never claim to have checked "current rankings" or "live SERPs"
-
What never to invent:
- Search volume, clicks, impressions, CTR, ranking positions
- Traffic estimates, conversion rates, bounce rates
- Backlink counts, domain authority scores
- Specific SERP feature presence (unless user confirms)
-
When user mentions tools:
- First ask for a small table or export to ground the analysis
- Exception: If they explicitly say they have no access to data
2. Output Clarity
Always prioritize:
- Directness: Lead with the answer, not with throat-clearing
- Plain language: Avoid jargon where not needed; explain specialized terms
- Scannability: Use headings, lists, and tables where they improve clarity
How to use this package (routing)
This file is intentionally lightweight. For execution, use the specialist Skills:
- Core OS (entry point for complex work):
skills/seo-os.SKILL.md - SERP + content gap analysis:
skills/serp-gap-analysis.SKILL.md - Featured snippets + AEO writing:
skills/aeo-snippet-writer.SKILL.md - GEO + AI visibility:
skills/geo-visibility.SKILL.md - Technical SEO audits:
skills/technical-seo-audit.SKILL.md
Recommended flow (typical):
skills/seo-os.SKILL.mdtools/gsc_ahrefs_clean.py(optional, if you have CSV exports)skills/serp-gap-analysis.SKILL.mdtemplates/aeo-brief.mdskills/aeo-snippet-writer.SKILL.mdskills/geo-visibility.SKILL.md(if AI visibility matters)skills/technical-seo-audit.SKILL.md+templates/technical-seo-audit.md(as needed)
This skill comes with supporting templates and tools:
templates/aeo-brief.md: Structured brief template for planning new content with clear snippet and AEO goals, SERP observations, headings, and success criteriatemplates/technical-seo-audit.md: Comprehensive technical audit checklist and reporting templatedocs/geo-optimization-guide.md: Deep-dive guide on AI search visibility optimizationdocs/skill-usage.md: Short guide explaining how to combine the modular Skillstools/gsc_ahrefs_clean.py: Helper script to clean and summarise CSV exports into Markdown tables for analysis
Refer to these templates when user requests specific deliverables.
Security & scope
- This Skill file is purely declarative guidance written in Markdown; it contains no executable code, secrets, or API keys.
- It only routes requests to internal specialist Skills (such as
seo-os,serp-gap-analysis,aeo-snippet-writer,geo-visibility, andtechnical-seo-audit). - It does not make direct network calls or connect to third-party services; any such integrations must be implemented and reviewed in the underlying tools or Skills.
- Maintain awareness of any future integration with external data sources or third-party APIs, and review those components separately for security impact.
What ships with it: 12 files
102.2 KB alongside SKILL.md, 1 of them executable
docs/
- geo-optimization-guide.md28.7 KB
- skill-usage.md2.1 KB
skills/
- aeo-snippet-writer.SKILL.md7.6 KB
- geo-visibility.SKILL.md6.0 KB
- seo-os.SKILL.md7.2 KB
- serp-gap-analysis.SKILL.md6.7 KB
- technical-seo-audit.SKILL.md5.1 KB
templates/
- aeo-brief.md4.1 KB
- technical-seo-audit.md17.7 KB
tools/
- gsc_ahrefs_clean.pyruns6.8 KB
Gives 0 of the 12 instructions most marketing audience skills give in ~1.2k tokens
Counted across 690 of the 894 authors here whose files we hold, read 2026-08-07
- Apply Poppins font to headingsin 41 of 690, across 6 files
- Apply Lora font to body textin 41 of 690, across 6 files
- Use Arial fallback for headingsin 39 of 690, across 4 files
- Use Georgia fallback for body textin 39 of 690, across 4 files
- Maintain text hierarchy and formattingin 39 of 690, across 4 files
- Use accent colors for non-text shapesin 38 of 690, across 3 files
- Use RGB values for precise color matchingin 38 of 690, across 3 files
- Use brand colors for primary text and backgroundsin 36 of 690, across 1 file
- Read product marketing context file before asking questions, starting, or auditingin 35 of 690, across 23 files
- Use active voice instead of passive voicein 26 of 690, across 10 files
- Implement or generate appropriate JSON-LD structured datain 24 of 690, across 17 files
- Prioritize clarity over clevernessin 22 of 690, across 8 files
Said here and by no other author read
- Label unsupported outputs as inferences
- Use default UK English and neutral tone unless instructed
- Reference specific data points in recommendations
- Ask for data exports when the user mentions tools
- Lead answers with direct facts
- Use headings, lists, and tables to improve clarity
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.