القائمة
Plan AI Overview readiness improvements — RAG retrievability, E-E-A-T signals, query fan-out coverage, semantic HTML, schema markup, agentic channel setup.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | ai-optimization-planner |
| alias | /ai-optimization-planner |
| description | Plan AI Overview readiness improvements — RAG retrievability, E-E-A-T signals, query fan-out coverage, semantic HTML, schema markup, agentic channel setup. |
| version | 1.0.0 |
| disallowedTools | Bash |
When my site or content exists and I want to improve its eligibility for Google AI Overviews, I want a structured AIO readiness plan, so I can address the specific signal gaps that affect whether my content is retrieved and cited in AI-generated answers.
copy-planner for that.seo-advisor for that.llms.txt, AI-specific markup, or keyword variants for AI modes — Google's AIO guide explicitly states these are not AIO signals.| User Situation | What Happens | What They Leave With |
|---|---|---|
| Content exists, not in AI Overviews | AIO planner audits E-E-A-T, fan-out, schema, and RAG eligibility | Tiered improvement plan with acceptance criteria |
| Preparing for agentic channels | Phase 3e assesses Merchant Center, GBP, UCP readiness | Agentic Channel Readiness report with Tier 3 tasks |
| Schema markup confusion | Phase 3d maps expected vs actual Schema.org types | Specific schema property list to implement |
| Discovery before planning | Phase 2 surfaces community tools and MCPs | Tooling survey with availability table |
seo-advisor before or in parallel — structural SEO is a prerequisite for AIO eligibility, not a substitute.copy-planner + copy-critic when Phase 3b (E-E-A-T) identifies MAJOR commodity content gaps.web-design-planner or design-partner when Phase 3d identifies MAJOR semantic HTML landmark or layout gaps.a11y-planner when semantic HTML improvements overlap with accessibility compliance needs.Google's AI Overviews are powered by RAG (Retrieval-Augmented Generation). Content that appears in AI Overviews satisfies a different signal set than content that ranks in traditional search:
seo-advisor covers the structural layer (headings, meta, intent, internal linking). This skill covers the AIO-specific layer above it.
llms.txt or AI-specific markup (not AIO signals per Google)These tools enhance the plan's accuracy when available. The planner degrades gracefully when they are not available but flags assumptions as FRAGILE.
| Tool | Purpose | Impact If Unavailable |
|---|---|---|
Search Console MCP / gsc-cli | Verify indexing status and snippet eligibility | Indexing assumed; flagged FRAGILE |
| Playwright MCP | Inspect as-rendered DOM, schema markup, landmark elements | Source-only HTML review |
| Web search MCP (Exa, Brave, Tavily) | Test current AIO appearance; validate fan-out query coverage | Manual testing instructions provided |
| Lighthouse CLI / PageSpeed Insights API | Core Web Vitals as indirect indexing quality signal | CWV noted as out-of-scope |
| Schema.org Validator | Validate schema markup before deployment | Manual validation instructions |
Phase 2 of the planning protocol uses these discovery mechanisms to surface community tools:
discover-skills.sh (meta-router repo): Run with keywords "AIO", "Search Console", "E-E-A-T" to find relevant community skills"Search Console" site:github.com skill SKILL.md and "E-E-A-T" OR "AI Overviews" site:github.com claude skillDiscovery is surfaced as options for the user. External skills are never auto-invoked.
copy-plannerseo-advisorllms.txt or AI-specific markup → read Google's AIO guide first; these are not signalscopy-planner then return here for AIO reviewai-optimization-critic: Companion reviewer — invoke at review checkpoints 1 (post-audit) and 3 (post-content-investment)seo-advisor: Structural SEO complement — run first or in parallel; invoke at checkpoint 2 (post-Tier-1)copy-planner: When E-E-A-T audit identifies MAJOR commodity content gaps requiring original writingcopy-critic: After Tier 2 content investment, before final ai-optimization-critic reviewweb-design-planner / design-partner: When semantic HTML or multimedia gaps require layout/component restructuringa11y-planner: When semantic HTML improvements overlap with accessibility complianceWhen invoked with /ai-optimization-planner [site or content URL/samples]:
These headings must appear in the output (load-bearing for parsers):
## Feature Overview
## Tooling Survey
## RAG Retrievability Report
## E-E-A-T Signal Matrix
## Query Fan-Out Coverage Matrix
## Semantic HTML Signal Map
## Agentic Channel Readiness
## Assumption Register
## Implementation Plan
## Test Strategy
## Review Checkpoint Plan
## Agentic Channel Readiness must be present for all outputs — use "N/A: non-transactional content" for informational sites.
Version: 1.0.0 Last Updated: 2026-05-19 Standalone Ready: Yes Perspective Module: No
Use when you have an existing component, flow, or interface and need an evidence-backed accessibility design review after basic checks pass. Best for focus management, ARIA pattern quality, semantics, and state communication gaps automated tools miss.
Use when you know what component, flow, or interface you need but not yet the right accessibility approach. Best for turning requirements into an accessible implementation plan before code hardens bad interaction and state patterns.
Review content for Google AI Overview eligibility — RAG retrievability, E-E-A-T signal completeness, fan-out coverage, semantic HTML for agent parsability, schema markup quality.
Assess organizational AI readiness — capabilities, gaps, adoption roadmap for strategic planning.
Alex Urevick-Ackelsberg's personal writing voice and style. Use this skill whenever writing AS Alex or ghostwriting content that should sound like him — emails to clients, community posts, conference session descriptions, proposals, LinkedIn posts, listserv replies, internal strategy docs, or any communication where Alex is the named author. Also use when Alex asks you to 'write this up,' 'draft a response,' 'help me write,' or when the output needs his voice rather than a generic professional tone. This is Alex's PERSONAL voice — for Zivtech brand/marketing content, use zivtech-writing-style instead (though both can apply when Alex is writing on behalf of Zivtech).
Define brand voice standards — tone, vocabulary, style rules for aligning content teams.