Skill Pack

SKILL.md · Claude Code, Cursor, Codex

aeo-answer-surface-playbook

description

Use when the goal is to own the answer unit on a named results/answer surface (featured snippet, PAA, AI Overview, Copilot, Perplexity), especially when the site already ranks and still loses the box. Not for brand-level engine mentions (geo-citation-playbook) or a keyword-to-brief content pipeline.

What it does
Wins a specific answer box (featured snippet, PAA, AI Overview, Copilot, Perplexity) with the right answer format, eligibility checks, and a measurement method that fits that surface.
Where it stops
Not for brand-level engine mentions (geo-citation-playbook) or a keyword-to-brief content pipeline.

One-time payment. The zip has all 11 skill folders with their references.

agent-skills-pack/aeo-answer-surface-playbook/SKILL.md
  1. ---
  2. name: aeo-answer-surface-playbook
  3. description: Use when the goal is to own the answer unit on a named results/answer surface (featured snippet, PAA, AI Overview, Copilot, Perplexity), especially when the site already ranks and still loses the box. Not for brand-level engine mentions (geo-citation-playbook) or a keyword-to-brief content pipeline.
  4. ---
  5. # AEO answer-surface playbook
  6. Design the visible answer unit for a **specific surface**, confirm snippet eligibility, and measure box ownership separately from rank.
  7. This skill owns surface mechanics and SERP / answer packaging, not generic extractability templates or JSON-LD recipes. For 2026 schema overrides (FAQ rich results dead, commerce still live) also run the `technical-seo-2026-delta` skill.
  8. Facts here are dated (current as of early November 2026). If they are more than 14 days old, run the `search-change-triage` skill first, against your own dated watchlist of official sources.
  9. No "AI-only" page variants. No micro-chunking "for RAG" (Google advises against both). No promise of FAQ rich-result dropdowns (gone 7 May 2026).
First 14 lines · real file

The other 10 skills in the pack

  • technical-seo-2026-delta

    Use when a site needs only the 2025–2026 Google/Bing technical changes checked (generative eligibility, snippet controls, dead rich results, crawler split, new Search Console reports and measurement caveats, EEA site-reputation split, regional SERP units, emergency crawl-rate controls).

  • geo-citation-playbook

    Use when a brand needs to be retrieved and cited inside generative answers (ChatGPT Search, Copilot, Perplexity, Claude, Gemini, Google AI Mode) — per-engine eligibility, citation measurement, third-party corroboration.

  • programmatic-seo-gate

    Use when someone wants template, location, integration, comparison, directory, or other pages at scale (programmatic SEO) and needs a 2026 allow/refuse decision with a page cap.

  • site-ia-map

    Use for a hub/spoke, cannibalization, one-URL-per-intent, internal-links, or site information-architecture job (live remap or greenfield).

  • search-change-triage

    Use every Monday, or when traffic / rankings / AI Overviews / AI citations moved, to classify the external search change and then choose wait, watch, or act.

  • gsc-growth-review

    Use when the ask is a Google Search Console period review and a qualitative SEO growth judgment for a named property.

  • seo-agent-design

    Use when someone asks you to build an SEO / AEO / GEO agent or content bot and you need its safety contract (tools, approve path, refuse list) before any code.

  • how-to-site-factory

    Use when building or rebuilding a vertical how-to / niche publisher site with a coding agent (repo, stack defaults, SEO defaults, image, accuracy and byline rules).

  • linkedin-post-system

    Use when designing a repeatable LinkedIn publishing system (topics, formats, cadence, review) that stays inside LinkedIn's 2026 rules, e.g. for building in public.

  • skill-review

    Use when auditing, tightening, or deciding whether to keep one agent SKILL.md.

Back to the pack overview