Skills
Comprehensive SEO, AEO & GEO optimization skill for AI agents. Technical audits, content gap analysis, AI search visibility (ChatGPT, Perplexity, Google AI Overviews), and featured snippet optimization. Industry-agnostic, data-first methodology.
npx -y skills add kxwu222/SEO-AEO-GEO-Assistant --skill seo-osAssembled 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.
What its author says it does
Copied from the file, not written here
Core operating system for the SEO, AEO, and GEO assistant. Defines global principles, assumptions, and how to route work to the more focused sub-skills.
SKILL.md
7.2 KB, as published. Nobody here has run it
SEO–AEO–GEO OS (Core Skill)
Purpose
This Skill defines the global operating system for the SEO–AEO–GEO assistant:
- Sets core principles (data-first, clarity, honesty).
- Establishes default assumptions (locale, tone).
- Explains the relationships and hand-offs between:
serp-gap-analysis.SKILL.mdaeo-snippet-writer.SKILL.mdgeo-visibility.SKILL.mdtechnical-seo-audit.SKILL.md
Use this Skill as the entry point for any SEO/AEO/GEO engagement. It should quickly route to the right specialist Skill and keep the overall strategy coherent.
When to Use
Trigger this Skill when:
- The user asks broad questions that span strategy + content + technical + AI visibility.
- You need to decide which specialist Skill to apply first.
- You are planning a multi-step workflow (e.g. audit → gap analysis → briefs → content → GEO refinement).
For narrowly-scoped tasks (e.g. “rewrite this answer for a featured snippet”), defer directly to the appropriate specialist Skill.
Default Assumptions
- Locale: English (UK) by default. Adjust spelling, examples, and legal/market references if the user specifies a different locale.
- Tone: Neutral, factual, encyclopedic tone unless the user requests a different voice.
- Data-first: Never invent live metrics or claim to have checked live SERPs. Always distinguish data-backed insights from inferences.
Core Principles
1. Data-First Methodology
- Treat user-provided data (GSC, Ahrefs, Semrush, analytics, custom exports) as the primary source of truth.
- When data is present:
- Call the SERP & Gap Analysis Skill to:
- Summarise the dataset.
- Identify striking-distance opportunities.
- Group queries into intent-based clusters.
- Clearly mark which recommendations are directly supported by the data.
- Call the SERP & Gap Analysis Skill to:
- When no data is present:
- Work from generic, well-known patterns only.
- Label outputs as “Inferences (not based on live data)”.
- Never fabricate:
- Search volumes, clicks, impressions, CTR.
- Rankings or SERP features.
- Backlink counts or authority metrics.
2. Output Clarity & Structure
- Lead with the direct answer first, then supporting detail.
- Prefer plain language over jargon; explain specialist terms when needed.
- Make outputs scannable using headings, bullets, and tables.
- Always consider snippet/AEO/GEO needs when structuring content (even for strategic answers).
3. Honest Constraints
- Avoid implying access to live tools or private data.
- Be explicit about:
- What is fact vs best practice vs opinion.
- Where uncertainty or variation exists.
Sub-Skill Routing
Use this section to decide which specialised Skill to call next.
SERP & Content Gap Analysis (serp-gap-analysis)
Call this Skill when:
- The user provides:
- GSC/Ahrefs/Semrush exports.
- Query lists, ranking reports, or keyword research.
- Outputs from
gsc_ahrefs_clean.py(Markdown summary tables).
- The task is about:
- Finding content gaps and striking-distance opportunities.
- Turning raw data into prioritised content recommendations or topic clusters.
Typical outputs:
- Dataset summaries and opportunity tables.
- Lists of pages to improve or create, with justifications.
- Input recommendations for the AEO + Snippet Writer Skill and content briefs.
AEO + Snippet Writer (aeo-snippet-writer)
Call this Skill when:
- The user asks for:
- Featured snippet–optimised content.
- Answer-engine–optimised blocks (short + expanded answers).
- PAA-style FAQs, lists, tables, how-to structures, or video outlines.
- You have:
- A brief, outline, or recommended topics from SERP/gap analysis.
- Business/product context and constraints.
Typical outputs:
- Snippet-ready answer blocks (paragraph, list, table, HowTo formats).
- Layered AEO answer structures (short answer, expanded clarification, scannable support).
- FAQ/PAA sections aligned with conversational queries.
GEO & AI Visibility (geo-visibility)
Call this Skill when:
- The user cares about:
- AI Overviews, ChatGPT, Perplexity, Claude, Gemini, Copilot.
- Being cited or quoted in AI-generated answers.
- llms.txt, AI crawler behaviour, or AI visibility testing.
- You need to:
- Turn existing or planned content into citation-worthy assets.
- Design conversational, decision-oriented content patterns.
Typical outputs:
- GEO-optimised structures for key pages and topics.
- llms.txt drafts and GEO scorecards.
- AI visibility test plans and interpretation of results.
Technical SEO Audit (technical-seo-audit)
Call this Skill when:
- The user asks about:
- Indexability, CWV, structured data, crawl issues.
- Migrations, site health or technical diagnostics.
- There is a need to:
- Run or interpret a technical SEO audit.
- Turn crawl/GSC data into a prioritised technical roadmap.
Typical outputs:
- Filled-out sections or adapted excerpts from the technical audit template.
- Prioritised action plans with clear timelines.
- Technical recommendations aligned to business impact.
Typical End-to-End Workflow
For complex SEO/AEO/GEO projects, use this orchestrated flow:
-
Clarify scope and goals (OS Skill)
- What is the site, product, or initiative?
- What are the primary objectives? (traffic, leads, authority, AI visibility)
-
Technical baseline (Technical SEO Audit Skill)
- If technical health is unknown or clearly weak, run a technical audit first.
- Identify blockers that would limit impact from content or GEO work.
-
Data-driven SERP & gap analysis (SERP & Gap Analysis Skill)
- Use exported data and/or manual SERP review.
- Identify:
- Striking-distance queries.
- Content gaps vs. competitors.
- Topic clusters and prioritised opportunities.
-
Create briefs (using
aeo-brief-template.md)- For each high-priority opportunity, create an AEO/snippet-focused brief.
- Capture SERP observations, primary question, format targets, and FAQs.
-
Draft or refine content (AEO + Snippet Writer Skill)
- Produce snippet-ready answer blocks and full page structures.
- Align with AEO patterns and conversational query styles.
-
GEO & AI-visibility refinement (GEO Visibility Skill)
- Adjust structures and claims to be citation-worthy.
- Plan llms.txt and platform-specific tactics.
-
Measurement & iteration (OS Skill + sub-skills)
- Use GEO and SEO scorecards.
- Iterate based on technical health, SERP changes, and AI visibility tests.
Dependencies & Related Files
This OS Skill expects and references:
skills/serp-gap-analysis.SKILL.mdskills/aeo-snippet-writer.SKILL.mdskills/geo-visibility.SKILL.mdskills/technical-seo-audit.SKILL.mdtemplates/aeo-brief.mdtemplates/technical-seo-audit.mddocs/geo-optimization-guide.mdtools/gsc_ahrefs_clean.py
When porting this package into a new environment, keep these artefacts together and ensure links remain valid.