[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6DQGJCMJZX552HBYQ0FNMDM":3,"skill-same:01M6DQGJCMJZX552HBYQ0FNMDM":101},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":31,"publishedAt":52,"linkOnly":53,"markdownContent":54,"markdownBody":55,"frontMatter":56,"refName":63,"commitSha":64,"skillDirectory":65,"forksCount":66,"repositoryHtmlUrl":67,"repositoryHomepageUrl":6,"ownerHtmlUrl":68,"ownerBlogUrl":69,"ownerDescription":70,"updatedAt":71,"install":72,"resources":84},"01M6DQGJCMJZX552HBYQ0FNMDM","seo-geo",null,"Optimize content for AI Overviews (formerly SGE), ChatGPT web search, Perplexity, and other AI-powered search experiences. Generative Engine Optimization (GEO) analysis including brand mention signals, AI crawler accessibility, llms.txt compliance, passage-level citability scoring, and platform-specific optimization. Use when user says \"AI Overviews\", \"SGE\", \"GEO\", \"AI search\", \"LLM optimization\", \"Perplexity\", \"AI citations\", \"ChatGPT search\", or \"AI visibility\".","robomotionio\u002Frobomotion-skills","robomotionio","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F49553031?v=4","01M6DNT9VFKCCTN41ZX2AJAKF6","Robomotion RPA","01M6DNTA04HHCEWE175YJ41Q1M",3,"MIT","https:\u002F\u002Fgithub.com\u002Frobomotionio\u002Frobomotion-skills\u002Fblob\u002Fmain\u002Fclaude-seo\u002Fskills\u002Fseo-geo\u002FSKILL.md",[18,23,26],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000015","视觉设计","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000019","营销推广",{"categoryNo":27,"categoryName":28,"taxonomyType":29,"taxonomyTypeDesc":30},"01JBSEEDCAT000000000000035","市场营销","PROFESSION","适用职业",[32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51],"geo","seo geo","seo","web search","platform","signals","scoring","optimize","use","brand","engine","llms","analysis","Citations","Optimization","compliance","search","chatgpt","accessibility","web","2026-11-10 10:12:30",false,"---\nname: seo-geo\ndescription: >\n  Optimize content for AI Overviews (formerly SGE), ChatGPT web search,\n  Perplexity, and other AI-powered search experiences. Generative Engine\n  Optimization (GEO) analysis including brand mention signals, AI crawler\n  accessibility, llms.txt compliance, passage-level citability scoring, and\n  platform-specific optimization. Use when user says \"AI Overviews\", \"SGE\",\n  \"GEO\", \"AI search\", \"LLM optimization\", \"Perplexity\", \"AI citations\",\n  \"ChatGPT search\", or \"AI visibility\".\nuser-invocable: true\nargument-hint: \"[url]\"\nlicense: MIT\nmetadata:\n  author: AgriciDaniel\n  version: \"2.3.1\"\n  category: seo\n---\n\n# AI Search \u002F GEO Optimization (May 2026)\n\n## Primary Source: Google's AI Optimization Guide\n\nGoogle's official position, published under Search Central docs:\n\n> \"Optimizing for generative AI search is **still SEO** from Google's\n> perspective. AEO and GEO are rebranded labels for the same work.\"\n\nRead `references\u002Fgoogle-ai-optimization-guide.md` for the full synthesis,\nmyth-busting list (`llms.txt`, chunking, AI-rephrasing, mention-farming,\nall rejected by Google as ineffective), and the Who\u002FHow\u002FWhy test for\ncontent quality.\n\nAudits should frame GEO findings as **SEO fundamentals applied to AI-search\nsurfaces**, not as a separate optimization discipline. When community\nrecommendations contradict Google's primary source, defer to Google and note\nthe contradiction in the report.\n\n## Key Statistics\n\n| Metric | Value | Source |\n|--------|-------|--------|\n| AI Overviews reach | 2.5 billion+ monthly active users, reported from Google I\u002FO 2026 keynote coverage; not confirmed on a Google-owned source; 200+ countries | Third-party I\u002FO reporting |\n| AI Overviews query coverage | ~50% of queries (third-party measurement; varies by country) | Industry data |\n| AI Mode monthly users | 1B+, reported from Google I\u002FO 2026 keynote coverage; not confirmed on a Google-owned source | Third-party I\u002FO reporting |\n| AI Mode model | custom version of Gemini 2.5 | Google |\n| AI-referred sessions growth | 527% (Jan-May 2025) | SparkToro |\n| ChatGPT weekly active users | 900 million | OpenAI |\n| Perplexity monthly queries | 500+ million | Perplexity |\n\n## Critical Insight: Brand Mentions > Backlinks\n\n**Brand mentions correlate 3x more strongly with AI visibility than backlinks.**\n(Ahrefs December 2025 study of 75,000 brands)\n\n| Signal | Correlation with AI Citations |\n|--------|------------------------------|\n| YouTube mentions | ~0.737 (strongest) |\n| Reddit mentions | High |\n| Wikipedia presence | High |\n| LinkedIn presence | Moderate |\n| Domain Rating (backlinks) | ~0.266 (weak) |\n\n**Only 11% of domains** are cited by both ChatGPT and Google AI Overviews for the same query, so platform-specific optimization is essential.\n\n---\n\n## GEO Analysis Criteria (Updated)\n\n### 1. Citability Score (25%)\n\n**Optimal passage length: 134-167 words** for AI citation. And **~44% of AI\ncitations come from the first 30% of a page** (SE Ranking study), front-load\nyour most citable, self-contained answer rather than burying it below the fold.\n\n**Strong signals:**\n- Clear, quotable sentences with specific facts\u002Fstatistics\n- Self-contained answer blocks (can be extracted without context)\n- Direct answer in first 40-60 words of section\n- Claims attributed with specific sources\n- Definitions following \"X is...\" or \"X refers to...\" patterns\n- Unique data points not found elsewhere\n\n**Weak signals:**\n- Vague, general statements\n- Opinion without evidence\n- Buried conclusions\n- No specific data points\n\n### 2. Structural Readability (20%)\n\n**92% of AI Overview citations come from top-10 ranking pages**, but 47% come from pages ranking below position 5, demonstrating different selection logic.\n\n**Strong signals:**\n- Clean H1->H2->H3 heading hierarchy\n- Question-based headings (matches query patterns)\n- Short paragraphs (2-4 sentences)\n- Tables for comparative data\n- Ordered\u002Funordered lists for step-by-step or multi-item content\n- FAQ sections with clear Q&A format\n\n**Weak signals:**\n- Wall of text with no structure\n- Inconsistent heading hierarchy\n- No lists or tables\n- Information buried in paragraphs\n\n### 3. Multi-Modal Content (15%)\n\nContent with multi-modal elements sees **156% higher selection rates**.\n\n**Check for:**\n- Text + relevant images\n- Video content (embedded or linked)\n- Infographics and charts\n- Interactive elements (calculators, tools)\n- Structured data supporting media\n\n### 4. Authority & Brand Signals (20%)\n\n**Strong signals:**\n- Author byline with credentials\n- Publication date and last-updated date\n- **Recency**, content under 3 months old is ~3x more likely to be cited in AI answers; pages left stale 6+ months lose citation eligibility (SE Ranking, 1.3M-citation study). A scheduled refresh program is one of the highest-leverage GEO plays.\n- Citations to primary sources (studies, official docs, data)\n- Organization credentials and affiliations\n- Expert quotes with attribution\n- Entity presence in Wikipedia, Wikidata\n- Mentions on Reddit, YouTube, LinkedIn\n\n**Weak signals:**\n- Anonymous authorship\n- No dates\n- No sources cited\n- No brand presence across platforms\n\n### 5. Technical Accessibility (20%)\n\n**AI crawlers do NOT execute JavaScript.** Server-side rendering is critical.\n\n**Check for:**\n- Server-side rendering (SSR) vs client-only content\n- AI crawler access in robots.txt\n- llms.txt file presence and configuration\n- RSL 1.0 licensing terms\n\n---\n\n## AI Crawler Detection\n\nCheck `robots.txt` for these AI crawlers:\n\n| Crawler | Owner | Purpose | Obeys robots.txt? |\n|---------|-------|---------|---|\n| GPTBot | OpenAI | **Model training only** (NOT ChatGPT Search) | yes |\n| OAI-SearchBot | OpenAI | **ChatGPT Search citability** (the crawler that decides it) | yes |\n| ChatGPT-User | OpenAI | ChatGPT browsing (user-triggered) | no (user-triggered) |\n| ClaudeBot | Anthropic | **Model training only** (NOT Claude's search features) | yes |\n| Claude-SearchBot | Anthropic | **Claude\u002FClaude.ai search-result citability** (the crawler that decides it) | yes |\n| Claude-User | Anthropic | Claude browsing on a user's behalf (user-triggered) | no (user-triggered) |\n| PerplexityBot | Perplexity | Perplexity AI search | yes |\n| CCBot | Common Crawl | Training data (often blocked) | yes |\n| Bytespider | ByteDance | TikTok\u002FDouyin AI | yes |\n| cohere-ai | Cohere | Cohere models | yes |\n| Google-Extended | Google | **Gemini\u002FVertex training & grounding only** (NOT Google Search) | yes |\n| Google-CloudVertexBot | Google | Site-owner-requested Vertex AI Agent crawls | yes |\n| Google-Agent | Google | Agentic browsing (Project Mariner), acts for a user | **no (user-triggered)** |\n| Google-NotebookLM | Google | Fetches individual user-added source URLs | **no (user-triggered)** |\n| Google Messages | Google | User-triggered fetch | **no (user-triggered)** |\n| Applebot-Extended | Apple | **Apple Intelligence \u002F generative-AI training data opt-out only** (NOT Siri, Spotlight, or Safari search; does not itself crawl, it labels content already fetched by Applebot) | yes |\n\nSources: [OpenAI crawlers](https:\u002F\u002Fplatform.openai.com\u002Fdocs\u002Fbots),\n[Google crawlers overview](https:\u002F\u002Fdevelopers.google.com\u002Fsearch\u002Fdocs\u002Fcrawling-indexing\u002Foverview-google-crawlers),\n[Anthropic crawler support article](https:\u002F\u002Fsupport.anthropic.com\u002Fen\u002Farticles\u002F8896518-does-anthropic-crawl-data-from-the-web-and-how-can-site-owners-block-the-crawler),\n[Apple Applebot-Extended support article](https:\u002F\u002Fsupport.apple.com\u002Fen-us\u002F119829).\nAnthropic's current crawler support article documents only ClaudeBot, Claude-User,\nand Claude-SearchBot; it does not list `anthropic-ai`, so the previously-unverified\n`anthropic-ai` row has been removed rather than kept as a guess.\n\n**Recommendation:** Allow OAI-SearchBot, Claude-SearchBot, and PerplexityBot for AI\nsearch visibility. GPTBot, ClaudeBot, CCBot, and Applebot-Extended are training-only\nsignals -- allow or block them on licensing preference, not on search-visibility\ngrounds.\n\n### Check the right bot for the claim you are making\n\nTwo pairs are routinely conflated. **Each claim below may only be supported by its own\nbot's robots.txt status** -- check them separately and report them separately.\n\n| Claim you want to make | Bot to check | Bot that does NOT support this claim |\n|---|---|---|\n| \"Content is citable in ChatGPT Search\" | `OAI-SearchBot` | `GPTBot` |\n| \"Content is available for OpenAI model training\" | `GPTBot` | `OAI-SearchBot` |\n| \"Content can be used for Gemini\u002FVertex training & grounding\" | `Google-Extended` | `Googlebot` |\n| \"Content is eligible for Google Search \u002F AI Overviews\" | `Googlebot` | `Google-Extended` |\n| \"Content is citable in Claude's search features\" | `Claude-SearchBot` | `ClaudeBot` |\n| \"Content is available for Anthropic model training\" | `ClaudeBot` | `Claude-SearchBot` |\n| \"Content can be used for Apple Intelligence training\" | `Applebot-Extended` | `Applebot` |\n| \"Content is discoverable via Siri, Spotlight, or Safari search\" | `Applebot` | `Applebot-Extended` |\n\n- **`Google-Extended` governs Gemini and Vertex AI training and grounding use only.\n  It does not affect inclusion in ordinary Google Search, or in AI Overviews and AI\n  Mode, both of which are served from the `Googlebot` index.** Never score\n  `Google-Extended` as a \"Google Search readiness\" signal, and never cite a blocked\n  `Google-Extended` as evidence that a site is missing from Google Search.\n- **`OAI-SearchBot` is the crawler that determines ChatGPT Search citability.\n  `GPTBot` is OpenAI's separate training crawler.** Checking `GPTBot` access tells\n  you nothing about whether ChatGPT Search can cite the page. A site that blocks\n  `GPTBot` and allows `OAI-SearchBot` is fully citable in ChatGPT Search.\n- **`Claude-SearchBot` is the crawler that determines citability in Claude's own\n  search features. `ClaudeBot` is Anthropic's separate training crawler** (per\n  Anthropic's crawler support article). Checking `ClaudeBot` access tells you\n  nothing about Claude search citability, and vice versa; report each separately.\n- **`Applebot-Extended` is a training-data opt-out signal, not a crawler that\n  fetches pages itself.** Per Apple's support article, disallowing\n  `Applebot-Extended` opts a site out of Apple Intelligence \u002F generative-model\n  training use, but the page remains discoverable through Siri, Spotlight, and\n  Safari as long as `Applebot` itself is allowed. Never cite a blocked\n  `Applebot-Extended` as evidence a site is missing from Apple's search surfaces.\n\nDo not use these names interchangeably in report prose. When reporting crawler access,\nname the specific user-agent that was checked and the specific capability it governs.\n\n> **User-triggered fetchers ignore robots.txt by design** (Google-Agent, Google-NotebookLM, Google Messages, ChatGPT-User). robots.txt cannot block them, use server-side access controls. Google's canonical crawling\u002Frobots reference moved to **developers.google.com\u002Fcrawling** (migrated 2025-11-20); IP-range files now live at `\u002Fcrawling\u002Fipranges\u002F` and `googlebot.json` was renamed `common-crawlers.json`. Emerging: **Web Bot Auth** (RFC 9421) lets bots authenticate via a `Signature-Agent` header + key directory (used by Google-Agent); reverse-DNS verification remains the fallback.\n\n---\n\n## llms.txt Standard\n\nRead `references\u002Fllmstxt-evidence.md` for the primary-source evidence (Mueller, Illyes, SE Ranking 300k-domain study, OtterlyAI server-log audit) on why `\u002Fllms.txt` is not currently a citation lever for major AI search systems. claude-seo reports presence but assigns no citation-ranking weight.\n\n> **Google now states this explicitly.** Google's AI optimization guide, introduced\n> 2026-05-15 and clarified 2026-06-15, says `llms.txt` and other AI-text files are\n> not needed for Google Search and do not help or hurt visibility or rankings.\n> They may still serve non-Google systems. Never recommend `llms.txt` as a Google\n> ranking or citation lever. Source:\n> developers.google.com\u002Fsearch\u002Fdocs\u002Ffundamentals\u002Fai-optimization-guide\n\nThe emerging **llms.txt** standard provides AI crawlers with structured content guidance.\n\n**Location:** `\u002Fllms.txt` (root of domain)\n\n**Format:**\n```\n# Title of site\n> Brief description\n\n## Main sections\n- [Page title](url): Description\n- [Another page](url): Description\n\n## Optional: Key facts\n- Fact 1\n- Fact 2\n```\n\n**Check for:**\n- Presence of `\u002Fllms.txt`\n- Structured content guidance\n- Key page highlights\n- Contact\u002Fauthority information\n\n---\n\n## RSL 1.0 (Really Simple Licensing)\n\nNew standard (December 2025) for machine-readable AI licensing terms.\n\n**Backed by:** Reddit, Yahoo, Medium, Quora, Cloudflare, Akamai, Creative Commons\n\n**Check for:** RSL implementation and appropriate licensing terms.\n\n---\n\n## Platform-Specific Optimization\n\n| Platform | Key Citation Sources | Optimization Focus |\n|----------|---------------------|-------------------|\n| **Google AI Overviews** | Strongly ranking-correlated, cites pages that already rank well | Traditional SEO + passage optimization |\n| **Google AI Mode** (custom version of Gemini 2.5) | Weakly ranking-correlated; broader pool (~9 domains cited\u002Fquery, Ahrefs) | Distinct surface: freshness, entity authority, citable passages beyond position 5 |\n| **ChatGPT** | Wikipedia (47.9%), Reddit (11.3%) | Entity presence, authoritative sources |\n| **Perplexity** | Reddit (46.7%), Wikipedia | Community validation, discussions |\n| **Bing Copilot** | Bing index, authoritative sites | Bing SEO, IndexNow |\n\n> **Two Google citation engines, not one.** AI Mode and AI Overviews reach the\n> same conclusion ~86% of the time but cite the same URLs only **13.7%** of the\n> time (Ahrefs study, 540K query pairs). Treat them as separate surfaces: ranking\n> well in classic Search feeds AI Overviews, but AI Mode draws from a broader pool\n> where freshness and entity authority outweigh raw position. Score both.\n>\n> **AI Mode is also a booking surface (2026-08-27).** Flight price tracking\n> with email alerts (180+ countries and territories), hotel booking through\n> integrated partners, and fares shown in points or miles now happen inside\n> AI Mode. Travel and hospitality clients should check partner eligibility;\n> nothing here is a documented ranking change.\n>\n> **UX is now unified, surfaces still distinct.** At Google I\u002FO 2026 (2026-05-19)\n> Google merged AI Overviews and AI Mode into \"one seamless AI Search experience\"\n> (question → AI Overview → follow-up in AI Mode) with a new intelligent Search\n> box. The *experience* is one flow, but the two citation engines remain\n> technically distinct (different models\u002Flink sets), keep scoring both.\n\n### Citation surfaces & controls in AI Search (2026)\n\nGoogle added many AI citation\u002Fsource surfaces across AI Overviews **and** AI Mode (May 2026):\n\n- **Preferred Sources**, an eligible domain or subdomain can be selected by a\n  user, making its content more likely to appear in that user's Top Stories and\n  eligible for a preferred badge in AI Mode or AI Overviews. This is a\n  **per-user preference**, not a documented general ranking signal. Publishers\n  may offer Google's interactive button or a deeplink, but should not promise a\n  site-wide ranking lift. Source:\n  developers.google.com\u002Fsearch\u002Fdocs\u002Fappearance\u002Fpreferred-sources\n- **\"Highly Cited\" badges**, earned via original primary reporting that other articles cite.\n- **Community Perspectives**, elevates Reddit\u002Fforum\u002Ffirsthand content.\n- Inline links, desktop hover **Link Previews**, and prominent link carousels.\n\n**Controlling AI-feature appearance:** there is **no AI-specific opt-out file**. Appearance in AI Overviews and AI Mode is governed by standard preview\u002Findex directives, `nosnippet`, `data-nosnippet`, `max-snippet`, `noindex` (distinct from the third-party AI-crawler robots controls above). Source: developers.google.com\u002Fsearch\u002Fdocs\u002Fappearance\u002Fai-features\n\n**Search agents (live, not just WebMCP):** Google's \"Information Agents\" run in the background to monitor topics, plus agentic booking\u002Fcalling for select categories (rolling out to US users, summer 2026), so agent-friendly-page optimization (real interactive elements, accessibility tree, layout stability) now matters for actions, not only citations.\n\n---\n\n## Output\n\nGenerate `GEO-ANALYSIS.md` with:\n\n1. **GEO Readiness Score: XX\u002F100**\n2. **Platform breakdown** (Google AIO, ChatGPT, Perplexity scores)\n3. **AI Crawler Access Status** -- report each crawler separately with the\n   capability it governs. Training access (`GPTBot`, `Google-Extended`, `CCBot`,\n   `ClaudeBot`, `Applebot-Extended`) and search citability (`OAI-SearchBot`,\n   `Googlebot`, `PerplexityBot`, `Claude-SearchBot`, `Applebot`) are distinct\n   findings and must never be merged into one line.\n4. **llms.txt Status** (present, missing, recommendations)\n5. **Brand Mention Analysis** (presence on Wikipedia, Reddit, YouTube, LinkedIn)\n6. **Passage-Level Citability** (optimal 134-167 word blocks identified)\n7. **Server-Side Rendering Check** (JavaScript dependency analysis)\n8. **Top 5 Highest-Impact Changes**\n9. **Schema Recommendations** (for AI discoverability)\n10. **Content Reformatting Suggestions** (specific passages to rewrite)\n\n---\n\n## Quick Wins\n\n1. Add \"What is [topic]?\" definition in first 60 words\n2. Create 134-167 word self-contained answer blocks\n3. Add question-based H2\u002FH3 headings\n4. Include specific statistics with sources\n5. Add publication\u002Fupdate dates\n6. Implement Person schema for authors\n7. Allow key AI crawlers in robots.txt\n\n## Medium Effort\n\n1. Create `\u002Fllms.txt` file (optional: ignored by Google Search; may help other AI crawlers)\n2. Add author bio with credentials + Wikipedia\u002FLinkedIn links\n3. Ensure server-side rendering for key content\n4. Build entity presence on Reddit, YouTube\n5. Add comparison tables with data\n6. Implement FAQ sections (structured, not schema for commercial sites)\n\n## High Impact\n\n1. Create original research\u002Fsurveys (unique citability)\n2. Build Wikipedia presence for brand\u002Fkey people\n3. Establish YouTube channel with content mentions\n4. Implement comprehensive entity linking (sameAs across platforms)\n5. Develop unique tools or calculators\n\n## DataForSEO Integration (Optional)\n\nIf DataForSEO MCP tools are available, use `ai_optimization_chat_gpt_scraper` to check what ChatGPT web search returns for target queries (real GEO visibility check) and `ai_opt_llm_ment_search` with `ai_opt_llm_ment_top_domains` for LLM mention tracking across AI platforms.\n\n## Error Handling\n\n| Scenario | Action |\n|----------|--------|\n| URL unreachable (DNS failure, connection refused) | Report the error clearly. Do not guess site content. Suggest the user verify the URL and try again. |\n| AI crawlers blocked by robots.txt | Report exactly which crawlers are blocked and which are allowed. Provide specific robots.txt directives to add for enabling AI search visibility. |\n| No llms.txt found | Note the absence (optional file; Google Search ignores it) and provide a ready-to-use llms.txt template for non-Google AI crawlers. |\n| No structured data detected | Report the gap and provide specific schema recommendations (Article, Organization, Person) for improving AI discoverability. |\n\n## FLOW Framework Integration\n\nFor prompt-guided AI content optimization, use `\u002Fseo flow optimize \u003Curl>`, FLOW's 21 optimize-stage prompts complement GEO's citability and structure analysis with evidence-led AI prompts.\n","# AI Search \u002F GEO Optimization (May 2026)\n\n## Primary Source: Google's AI Optimization Guide\n\nGoogle's official position, published under Search Central docs:\n\n> \"Optimizing for generative AI search is **still SEO** from Google's\n> perspective. AEO and GEO are rebranded labels for the same work.\"\n\nRead `references\u002Fgoogle-ai-optimization-guide.md` for the full synthesis,\nmyth-busting list (`llms.txt`, chunking, AI-rephrasing, mention-farming,\nall rejected by Google as ineffective), and the Who\u002FHow\u002FWhy test for\ncontent quality.\n\nAudits should frame GEO findings as **SEO fundamentals applied to AI-search\nsurfaces**, not as a separate optimization discipline. When community\nrecommendations contradict Google's primary source, defer to Google and note\nthe contradiction in the report.\n\n## Key Statistics\n\n| Metric | Value | Source |\n|--------|-------|--------|\n| AI Overviews reach | 2.5 billion+ monthly active users, reported from Google I\u002FO 2026 keynote coverage; not confirmed on a Google-owned source; 200+ countries | Third-party I\u002FO reporting |\n| AI Overviews query coverage | ~50% of queries (third-party measurement; varies by country) | Industry data |\n| AI Mode monthly users | 1B+, reported from Google I\u002FO 2026 keynote coverage; not confirmed on a Google-owned source | Third-party I\u002FO reporting |\n| AI Mode model | custom version of Gemini 2.5 | Google |\n| AI-referred sessions growth | 527% (Jan-May 2025) | SparkToro |\n| ChatGPT weekly active users | 900 million | OpenAI |\n| Perplexity monthly queries | 500+ million | Perplexity |\n\n## Critical Insight: Brand Mentions > Backlinks\n\n**Brand mentions correlate 3x more strongly with AI visibility than backlinks.**\n(Ahrefs December 2025 study of 75,000 brands)\n\n| Signal | Correlation with AI Citations |\n|--------|------------------------------|\n| YouTube mentions | ~0.737 (strongest) |\n| Reddit mentions | High |\n| Wikipedia presence | High |\n| LinkedIn presence | Moderate |\n| Domain Rating (backlinks) | ~0.266 (weak) |\n\n**Only 11% of domains** are cited by both ChatGPT and Google AI Overviews for the same query, so platform-specific optimization is essential.\n\n---\n\n## GEO Analysis Criteria (Updated)\n\n### 1. Citability Score (25%)\n\n**Optimal passage length: 134-167 words** for AI citation. And **~44% of AI\ncitations come from the first 30% of a page** (SE Ranking study), front-load\nyour most citable, self-contained answer rather than burying it below the fold.\n\n**Strong signals:**\n- Clear, quotable sentences with specific facts\u002Fstatistics\n- Self-contained answer blocks (can be extracted without context)\n- Direct answer in first 40-60 words of section\n- Claims attributed with specific sources\n- Definitions following \"X is...\" or \"X refers to...\" patterns\n- Unique data points not found elsewhere\n\n**Weak signals:**\n- Vague, general statements\n- Opinion without evidence\n- Buried conclusions\n- No specific data points\n\n### 2. Structural Readability (20%)\n\n**92% of AI Overview citations come from top-10 ranking pages**, but 47% come from pages ranking below position 5, demonstrating different selection logic.\n\n**Strong signals:**\n- Clean H1->H2->H3 heading hierarchy\n- Question-based headings (matches query patterns)\n- Short paragraphs (2-4 sentences)\n- Tables for comparative data\n- Ordered\u002Funordered lists for step-by-step or multi-item content\n- FAQ sections with clear Q&A format\n\n**Weak signals:**\n- Wall of text with no structure\n- Inconsistent heading hierarchy\n- No lists or tables\n- Information buried in paragraphs\n\n### 3. Multi-Modal Content (15%)\n\nContent with multi-modal elements sees **156% higher selection rates**.\n\n**Check for:**\n- Text + relevant images\n- Video content (embedded or linked)\n- Infographics and charts\n- Interactive elements (calculators, tools)\n- Structured data supporting media\n\n### 4. Authority & Brand Signals (20%)\n\n**Strong signals:**\n- Author byline with credentials\n- Publication date and last-updated date\n- **Recency**, content under 3 months old is ~3x more likely to be cited in AI answers; pages left stale 6+ months lose citation eligibility (SE Ranking, 1.3M-citation study). A scheduled refresh program is one of the highest-leverage GEO plays.\n- Citations to primary sources (studies, official docs, data)\n- Organization credentials and affiliations\n- Expert quotes with attribution\n- Entity presence in Wikipedia, Wikidata\n- Mentions on Reddit, YouTube, LinkedIn\n\n**Weak signals:**\n- Anonymous authorship\n- No dates\n- No sources cited\n- No brand presence across platforms\n\n### 5. Technical Accessibility (20%)\n\n**AI crawlers do NOT execute JavaScript.** Server-side rendering is critical.\n\n**Check for:**\n- Server-side rendering (SSR) vs client-only content\n- AI crawler access in robots.txt\n- llms.txt file presence and configuration\n- RSL 1.0 licensing terms\n\n---\n\n## AI Crawler Detection\n\nCheck `robots.txt` for these AI crawlers:\n\n| Crawler | Owner | Purpose | Obeys robots.txt? |\n|---------|-------|---------|---|\n| GPTBot | OpenAI | **Model training only** (NOT ChatGPT Search) | yes |\n| OAI-SearchBot | OpenAI | **ChatGPT Search citability** (the crawler that decides it) | yes |\n| ChatGPT-User | OpenAI | ChatGPT browsing (user-triggered) | no (user-triggered) |\n| ClaudeBot | Anthropic | **Model training only** (NOT Claude's search features) | yes |\n| Claude-SearchBot | Anthropic | **Claude\u002FClaude.ai search-result citability** (the crawler that decides it) | yes |\n| Claude-User | Anthropic | Claude browsing on a user's behalf (user-triggered) | no (user-triggered) |\n| PerplexityBot | Perplexity | Perplexity AI search | yes |\n| CCBot | Common Crawl | Training data (often blocked) | yes |\n| Bytespider | ByteDance | TikTok\u002FDouyin AI | yes |\n| cohere-ai | Cohere | Cohere models | yes |\n| Google-Extended | Google | **Gemini\u002FVertex training & grounding only** (NOT Google Search) | yes |\n| Google-CloudVertexBot | Google | Site-owner-requested Vertex AI Agent crawls | yes |\n| Google-Agent | Google | Agentic browsing (Project Mariner), acts for a user | **no (user-triggered)** |\n| Google-NotebookLM | Google | Fetches individual user-added source URLs | **no (user-triggered)** |\n| Google Messages | Google | User-triggered fetch | **no (user-triggered)** |\n| Applebot-Extended | Apple | **Apple Intelligence \u002F generative-AI training data opt-out only** (NOT Siri, Spotlight, or Safari search; does not itself crawl, it labels content already fetched by Applebot) | yes |\n\nSources: [OpenAI crawlers](https:\u002F\u002Fplatform.openai.com\u002Fdocs\u002Fbots),\n[Google crawlers overview](https:\u002F\u002Fdevelopers.google.com\u002Fsearch\u002Fdocs\u002Fcrawling-indexing\u002Foverview-google-crawlers),\n[Anthropic crawler support article](https:\u002F\u002Fsupport.anthropic.com\u002Fen\u002Farticles\u002F8896518-does-anthropic-crawl-data-from-the-web-and-how-can-site-owners-block-the-crawler),\n[Apple Applebot-Extended support article](https:\u002F\u002Fsupport.apple.com\u002Fen-us\u002F119829).\nAnthropic's current crawler support article documents only ClaudeBot, Claude-User,\nand Claude-SearchBot; it does not list `anthropic-ai`, so the previously-unverified\n`anthropic-ai` row has been removed rather than kept as a guess.\n\n**Recommendation:** Allow OAI-SearchBot, Claude-SearchBot, and PerplexityBot for AI\nsearch visibility. GPTBot, ClaudeBot, CCBot, and Applebot-Extended are training-only\nsignals -- allow or block them on licensing preference, not on search-visibility\ngrounds.\n\n### Check the right bot for the claim you are making\n\nTwo pairs are routinely conflated. **Each claim below may only be supported by its own\nbot's robots.txt status** -- check them separately and report them separately.\n\n| Claim you want to make | Bot to check | Bot that does NOT support this claim |\n|---|---|---|\n| \"Content is citable in ChatGPT Search\" | `OAI-SearchBot` | `GPTBot` |\n| \"Content is available for OpenAI model training\" | `GPTBot` | `OAI-SearchBot` |\n| \"Content can be used for Gemini\u002FVertex training & grounding\" | `Google-Extended` | `Googlebot` |\n| \"Content is eligible for Google Search \u002F AI Overviews\" | `Googlebot` | `Google-Extended` |\n| \"Content is citable in Claude's search features\" | `Claude-SearchBot` | `ClaudeBot` |\n| \"Content is available for Anthropic model training\" | `ClaudeBot` | `Claude-SearchBot` |\n| \"Content can be used for Apple Intelligence training\" | `Applebot-Extended` | `Applebot` |\n| \"Content is discoverable via Siri, Spotlight, or Safari search\" | `Applebot` | `Applebot-Extended` |\n\n- **`Google-Extended` governs Gemini and Vertex AI training and grounding use only.\n  It does not affect inclusion in ordinary Google Search, or in AI Overviews and AI\n  Mode, both of which are served from the `Googlebot` index.** Never score\n  `Google-Extended` as a \"Google Search readiness\" signal, and never cite a blocked\n  `Google-Extended` as evidence that a site is missing from Google Search.\n- **`OAI-SearchBot` is the crawler that determines ChatGPT Search citability.\n  `GPTBot` is OpenAI's separate training crawler.** Checking `GPTBot` access tells\n  you nothing about whether ChatGPT Search can cite the page. A site that blocks\n  `GPTBot` and allows `OAI-SearchBot` is fully citable in ChatGPT Search.\n- **`Claude-SearchBot` is the crawler that determines citability in Claude's own\n  search features. `ClaudeBot` is Anthropic's separate training crawler** (per\n  Anthropic's crawler support article). Checking `ClaudeBot` access tells you\n  nothing about Claude search citability, and vice versa; report each separately.\n- **`Applebot-Extended` is a training-data opt-out signal, not a crawler that\n  fetches pages itself.** Per Apple's support article, disallowing\n  `Applebot-Extended` opts a site out of Apple Intelligence \u002F generative-model\n  training use, but the page remains discoverable through Siri, Spotlight, and\n  Safari as long as `Applebot` itself is allowed. Never cite a blocked\n  `Applebot-Extended` as evidence a site is missing from Apple's search surfaces.\n\nDo not use these names interchangeably in report prose. When reporting crawler access,\nname the specific user-agent that was checked and the specific capability it governs.\n\n> **User-triggered fetchers ignore robots.txt by design** (Google-Agent, Google-NotebookLM, Google Messages, ChatGPT-User). robots.txt cannot block them, use server-side access controls. Google's canonical crawling\u002Frobots reference moved to **developers.google.com\u002Fcrawling** (migrated 2025-11-20); IP-range files now live at `\u002Fcrawling\u002Fipranges\u002F` and `googlebot.json` was renamed `common-crawlers.json`. Emerging: **Web Bot Auth** (RFC 9421) lets bots authenticate via a `Signature-Agent` header + key directory (used by Google-Agent); reverse-DNS verification remains the fallback.\n\n---\n\n## llms.txt Standard\n\nRead `references\u002Fllmstxt-evidence.md` for the primary-source evidence (Mueller, Illyes, SE Ranking 300k-domain study, OtterlyAI server-log audit) on why `\u002Fllms.txt` is not currently a citation lever for major AI search systems. claude-seo reports presence but assigns no citation-ranking weight.\n\n> **Google now states this explicitly.** Google's AI optimization guide, introduced\n> 2026-05-15 and clarified 2026-06-15, says `llms.txt` and other AI-text files are\n> not needed for Google Search and do not help or hurt visibility or rankings.\n> They may still serve non-Google systems. Never recommend `llms.txt` as a Google\n> ranking or citation lever. Source:\n> developers.google.com\u002Fsearch\u002Fdocs\u002Ffundamentals\u002Fai-optimization-guide\n\nThe emerging **llms.txt** standard provides AI crawlers with structured content guidance.\n\n**Location:** `\u002Fllms.txt` (root of domain)\n\n**Format:**\n```\n# Title of site\n> Brief description\n\n## Main sections\n- [Page title](url): Description\n- [Another page](url): Description\n\n## Optional: Key facts\n- Fact 1\n- Fact 2\n```\n\n**Check for:**\n- Presence of `\u002Fllms.txt`\n- Structured content guidance\n- Key page highlights\n- Contact\u002Fauthority information\n\n---\n\n## RSL 1.0 (Really Simple Licensing)\n\nNew standard (December 2025) for machine-readable AI licensing terms.\n\n**Backed by:** Reddit, Yahoo, Medium, Quora, Cloudflare, Akamai, Creative Commons\n\n**Check for:** RSL implementation and appropriate licensing terms.\n\n---\n\n## Platform-Specific Optimization\n\n| Platform | Key Citation Sources | Optimization Focus |\n|----------|---------------------|-------------------|\n| **Google AI Overviews** | Strongly ranking-correlated, cites pages that already rank well | Traditional SEO + passage optimization |\n| **Google AI Mode** (custom version of Gemini 2.5) | Weakly ranking-correlated; broader pool (~9 domains cited\u002Fquery, Ahrefs) | Distinct surface: freshness, entity authority, citable passages beyond position 5 |\n| **ChatGPT** | Wikipedia (47.9%), Reddit (11.3%) | Entity presence, authoritative sources |\n| **Perplexity** | Reddit (46.7%), Wikipedia | Community validation, discussions |\n| **Bing Copilot** | Bing index, authoritative sites | Bing SEO, IndexNow |\n\n> **Two Google citation engines, not one.** AI Mode and AI Overviews reach the\n> same conclusion ~86% of the time but cite the same URLs only **13.7%** of the\n> time (Ahrefs study, 540K query pairs). Treat them as separate surfaces: ranking\n> well in classic Search feeds AI Overviews, but AI Mode draws from a broader pool\n> where freshness and entity authority outweigh raw position. Score both.\n>\n> **AI Mode is also a booking surface (2026-08-27).** Flight price tracking\n> with email alerts (180+ countries and territories), hotel booking through\n> integrated partners, and fares shown in points or miles now happen inside\n> AI Mode. Travel and hospitality clients should check partner eligibility;\n> nothing here is a documented ranking change.\n>\n> **UX is now unified, surfaces still distinct.** At Google I\u002FO 2026 (2026-05-19)\n> Google merged AI Overviews and AI Mode into \"one seamless AI Search experience\"\n> (question → AI Overview → follow-up in AI Mode) with a new intelligent Search\n> box. The *experience* is one flow, but the two citation engines remain\n> technically distinct (different models\u002Flink sets), keep scoring both.\n\n### Citation surfaces & controls in AI Search (2026)\n\nGoogle added many AI citation\u002Fsource surfaces across AI Overviews **and** AI Mode (May 2026):\n\n- **Preferred Sources**, an eligible domain or subdomain can be selected by a\n  user, making its content more likely to appear in that user's Top Stories and\n  eligible for a preferred badge in AI Mode or AI Overviews. This is a\n  **per-user preference**, not a documented general ranking signal. Publishers\n  may offer Google's interactive button or a deeplink, but should not promise a\n  site-wide ranking lift. Source:\n  developers.google.com\u002Fsearch\u002Fdocs\u002Fappearance\u002Fpreferred-sources\n- **\"Highly Cited\" badges**, earned via original primary reporting that other articles cite.\n- **Community Perspectives**, elevates Reddit\u002Fforum\u002Ffirsthand content.\n- Inline links, desktop hover **Link Previews**, and prominent link carousels.\n\n**Controlling AI-feature appearance:** there is **no AI-specific opt-out file**. Appearance in AI Overviews and AI Mode is governed by standard preview\u002Findex directives, `nosnippet`, `data-nosnippet`, `max-snippet`, `noindex` (distinct from the third-party AI-crawler robots controls above). Source: developers.google.com\u002Fsearch\u002Fdocs\u002Fappearance\u002Fai-features\n\n**Search agents (live, not just WebMCP):** Google's \"Information Agents\" run in the background to monitor topics, plus agentic booking\u002Fcalling for select categories (rolling out to US users, summer 2026), so agent-friendly-page optimization (real interactive elements, accessibility tree, layout stability) now matters for actions, not only citations.\n\n---\n\n## Output\n\nGenerate `GEO-ANALYSIS.md` with:\n\n1. **GEO Readiness Score: XX\u002F100**\n2. **Platform breakdown** (Google AIO, ChatGPT, Perplexity scores)\n3. **AI Crawler Access Status** -- report each crawler separately with the\n   capability it governs. Training access (`GPTBot`, `Google-Extended`, `CCBot`,\n   `ClaudeBot`, `Applebot-Extended`) and search citability (`OAI-SearchBot`,\n   `Googlebot`, `PerplexityBot`, `Claude-SearchBot`, `Applebot`) are distinct\n   findings and must never be merged into one line.\n4. **llms.txt Status** (present, missing, recommendations)\n5. **Brand Mention Analysis** (presence on Wikipedia, Reddit, YouTube, LinkedIn)\n6. **Passage-Level Citability** (optimal 134-167 word blocks identified)\n7. **Server-Side Rendering Check** (JavaScript dependency analysis)\n8. **Top 5 Highest-Impact Changes**\n9. **Schema Recommendations** (for AI discoverability)\n10. **Content Reformatting Suggestions** (specific passages to rewrite)\n\n---\n\n## Quick Wins\n\n1. Add \"What is [topic]?\" definition in first 60 words\n2. Create 134-167 word self-contained answer blocks\n3. Add question-based H2\u002FH3 headings\n4. Include specific statistics with sources\n5. Add publication\u002Fupdate dates\n6. Implement Person schema for authors\n7. Allow key AI crawlers in robots.txt\n\n## Medium Effort\n\n1. Create `\u002Fllms.txt` file (optional: ignored by Google Search; may help other AI crawlers)\n2. Add author bio with credentials + Wikipedia\u002FLinkedIn links\n3. Ensure server-side rendering for key content\n4. Build entity presence on Reddit, YouTube\n5. Add comparison tables with data\n6. Implement FAQ sections (structured, not schema for commercial sites)\n\n## High Impact\n\n1. Create original research\u002Fsurveys (unique citability)\n2. Build Wikipedia presence for brand\u002Fkey people\n3. Establish YouTube channel with content mentions\n4. Implement comprehensive entity linking (sameAs across platforms)\n5. Develop unique tools or calculators\n\n## DataForSEO Integration (Optional)\n\nIf DataForSEO MCP tools are available, use `ai_optimization_chat_gpt_scraper` to check what ChatGPT web search returns for target queries (real GEO visibility check) and `ai_opt_llm_ment_search` with `ai_opt_llm_ment_top_domains` for LLM mention tracking across AI platforms.\n\n## Error Handling\n\n| Scenario | Action |\n|----------|--------|\n| URL unreachable (DNS failure, connection refused) | Report the error clearly. Do not guess site content. Suggest the user verify the URL and try again. |\n| AI crawlers blocked by robots.txt | Report exactly which crawlers are blocked and which are allowed. Provide specific robots.txt directives to add for enabling AI search visibility. |\n| No llms.txt found | Note the absence (optional file; Google Search ignores it) and provide a ready-to-use llms.txt template for non-Google AI crawlers. |\n| No structured data detected | Report the gap and provide specific schema recommendations (Article, Organization, Person) for improving AI discoverability. |\n\n## FLOW Framework Integration\n\nFor prompt-guided AI content optimization, use `\u002Fseo flow optimize \u003Curl>`, FLOW's 21 optimize-stage prompts complement GEO's citability and structure analysis with evidence-led AI prompts.\n",{"name":5,"license":15,"metadata":57,"description":60,"argument-hint":61,"user-invocable":62},{"author":58,"version":59,"category":34},"AgriciDaniel","2.3.1","Optimize content for AI Overviews (formerly SGE), ChatGPT web search, Perplexity, and other AI-powered search experiences. Generative Engine Optimization (GEO) analysis including brand mention signals, AI crawler accessibility, llms.txt compliance, passage-level citability scoring, and platform-specific optimization. Use when user says \"AI Overviews\", \"SGE\", \"GEO\", \"AI search\", \"LLM optimization\", \"Perplexity\", \"AI citations\", \"ChatGPT search\", or \"AI visibility\".\n","[url]",true,"main","255bc92da499b24be3950e91bf3fd2f84adc6246","claude-seo\u002Fskills\u002Fseo-geo",0,"https:\u002F\u002Fgithub.com\u002Frobomotionio\u002Frobomotion-skills","https:\u002F\u002Fgithub.com\u002Frobomotionio","https:\u002F\u002Fwww.robomotion.io","A web-based and cloud-native Robotic Process Automation (RPA) platform","2026-11-09 21:54:14",{"source":8,"skillName":5,"commands":73,"prompt":83,"zipAvailable":62},[74,77,80],{"tool":75,"command":76},"npx","npx skills add robomotionio\u002Frobomotion-skills --skill seo-geo",{"tool":78,"command":79},"bunx","bunx skills add robomotionio\u002Frobomotion-skills --skill seo-geo",{"tool":81,"command":82},"pnpm","pnpm dlx skills add robomotionio\u002Frobomotion-skills --skill seo-geo","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Frobomotionio\u002Frobomotion-skills\u002Fblob\u002Fmain\u002Fclaude-seo\u002Fskills\u002Fseo-geo\u002FSKILL.md",[85,91,97],{"path":86,"resourceType":87,"resourceTypeDesc":88,"sizeBytes":89,"sourceHtmlUrl":90},"LICENSE.txt","LICENSE","许可证",143,"https:\u002F\u002Fgithub.com\u002Frobomotionio\u002Frobomotion-skills\u002Fblob\u002Fmain\u002Fclaude-seo\u002Fskills\u002Fseo-geo\u002FLICENSE.txt",{"path":92,"resourceType":93,"resourceTypeDesc":94,"sizeBytes":95,"sourceHtmlUrl":96},"references\u002Fgoogle-ai-optimization-guide.md","REFERENCE","参考文档",6619,"https:\u002F\u002Fgithub.com\u002Frobomotionio\u002Frobomotion-skills\u002Fblob\u002Fmain\u002Fclaude-seo\u002Fskills\u002Fseo-geo\u002Freferences\u002Fgoogle-ai-optimization-guide.md",{"path":98,"resourceType":93,"resourceTypeDesc":94,"sizeBytes":99,"sourceHtmlUrl":100},"references\u002Fllmstxt-evidence.md",3010,"https:\u002F\u002Fgithub.com\u002Frobomotionio\u002Frobomotion-skills\u002Fblob\u002Fmain\u002Fclaude-seo\u002Fskills\u002Fseo-geo\u002Freferences\u002Fllmstxt-evidence.md",[102,132,161,182,206,235],{"skillNo":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":106,"categories":107,"keywords":112,"publishedAt":52},"01M6DVHBXN0KDNGD4H9DSWTTCG","ckm:ui-styling","Create beautiful, accessible user interfaces with shadcn\u002Fui components (built on Radix UI + Tailwind), Tailwind CSS utility-first styling, and canvas-based visual designs. Use when building user interfaces, implementing design systems, creating responsive layouts, adding accessible components (dialogs, dropdowns, forms, tables), customizing themes and colors, implementing dark mode, generating visual designs and posters, or establishing consistent styling patterns across applications.","https:\u002F\u002Fgithub.com\u002Frobomotionio\u002Frobomotion-skills\u002Fblob\u002Fmain\u002Fui-ux-pro-max-skill\u002F.claude\u002Fskills\u002Fui-styling\u002FSKILL.md",[108,109],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":110,"categoryName":111,"taxonomyType":29,"taxonomyTypeDesc":30},"01JBSEEDCAT000000000000032","设计师",[113,114,115,116,117,118,119,120,121,122,123,124,125,126,127,40,128,129,130,131],"ui styling","ui","styling","ckm:ui styling","design","css","canvas","components","component","create","design systems","applications","first","Tailwind","radix ui","visual","across","dark mode","ui components",{"skillNo":133,"name":134,"nameZh":6,"description":135,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":136,"categories":137,"keywords":146,"publishedAt":52},"01M6DVH17X0AE8DN1QYVG0RC16","ckm:design","Comprehensive design skill: brand identity, design tokens, UI styling, logo generation (55 styles, Gemini AI), corporate identity program (50 deliverables, CIP mockups), HTML presentations (Chart.js), banner design (22 styles, social\u002Fads\u002Fweb\u002Fprint), icon design (15 styles, SVG, Gemini 3.1 Pro), social photos (HTML→screenshot, multi-platform). Actions: design logo, create CIP, generate mockups, build slides, design banner, generate icon, create social photos, social media images, brand identity, design system. Platforms: Facebook, Twitter, LinkedIn, YouTube, Instagram, Pinterest, TikTok, Threads, Google Ads.","https:\u002F\u002Fgithub.com\u002Frobomotionio\u002Frobomotion-skills\u002Fblob\u002Fmain\u002Fui-ux-pro-max-skill\u002F.claude\u002Fskills\u002Fdesign\u002FSKILL.md",[138,141,142,145],{"categoryNo":139,"categoryName":140,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000003","演示文稿",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":143,"categoryName":144,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":110,"categoryName":111,"taxonomyType":29,"taxonomyTypeDesc":30},[117,134,147,113,148,149,122,150,151,114,152,153,154,155,115,156,157,158,159,160],"google","design system","presentations","generate","screenshot","actions","Media","logo","ads","images","youtube","tiktok","social","chart",{"skillNo":162,"name":163,"nameZh":6,"description":164,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":165,"categories":166,"keywords":169,"publishedAt":52},"01M6DVGVP1W8D53EFXNCCVQMFC","ckm:design-system","Token architecture, component specifications, and slide generation. Three-layer tokens (primitive→semantic→component), CSS variables, spacing\u002Ftypography scales, component specs, strategic slide creation. Use for design tokens, systematic design, brand-compliant presentations.","https:\u002F\u002Fgithub.com\u002Frobomotionio\u002Frobomotion-skills\u002Fblob\u002Fmain\u002Fui-ux-pro-max-skill\u002F.claude\u002Fskills\u002Fdesign-system\u002FSKILL.md",[167,168],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":110,"categoryName":111,"taxonomyType":29,"taxonomyTypeDesc":30},[117,148,170,171,134,118,121,172,149,41,40,173,174,175,176,177,178,179,180,181],"system","ckm:design system","architecture","typography","design tokens","three","token","generation","tokens","creation","systematic","css variables",{"skillNo":183,"name":184,"nameZh":6,"description":185,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":186,"categories":187,"keywords":193,"publishedAt":52},"01M6DVGK91P01C99NQ5Z83VN7S","ckm:banner-design","Design banners for social media, ads, website heroes, creative assets, and print. Multiple art direction options with AI-generated visuals. Actions: design, create, generate banner. Platforms: Facebook, Twitter\u002FX, LinkedIn, YouTube, Instagram, Google Display, website hero, print. Styles: minimalist, gradient, bold typography, photo-based, illustrated, geometric, retro, glassmorphism, 3D, neon, duotone, editorial, collage. Uses ui-ux-pro-max, frontend-design, ai-artist, ai-multimodal skills.","https:\u002F\u002Fgithub.com\u002Frobomotionio\u002Frobomotion-skills\u002Fblob\u002Fmain\u002Fui-ux-pro-max-skill\u002F.claude\u002Fskills\u002Fbanner-design\u002FSKILL.md",[188,191,192],{"categoryNo":189,"categoryName":190,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":110,"categoryName":111,"taxonomyType":29,"taxonomyTypeDesc":30},[117,194,195,196,197,122,150,198,152,153,199,155,200,201,202,157,159,203,204,205],"banner design","ckm:banner design","banner","frontend","website","3D","generated","Art","ui-ux","dimensions","options","neon",{"skillNo":207,"name":208,"nameZh":6,"description":209,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":210,"categories":211,"keywords":218,"publishedAt":52},"01M6DVC00Y6MH20TM98KVDHQB1","supabase-postgres-best-practices","Postgres best practices maintained by Supabase, for Postgres running anywhere. Load this skill BEFORE writing or changing anything that lives in a Postgres database: creating or altering tables and columns (including choosing column types), schema design, migrations and declarative schema files, RLS policies and the tests that verify them, indexes, triggers, database functions, queues and scheduled jobs (pg_cron, pgmq), vector\u002Fsemantic search (pgvector), and restoring dumps (pg_restore) or importing data. Also load it when diagnosing slow queries, high CPU, timeouts, EXPLAIN plans, connection exhaustion, locking, bloat, or rows visible to the wrong user or tenant. This is not just a performance guide — schema, migration, security, and SQL authoring tasks need these rules too, even for a one-column change or a single query.","https:\u002F\u002Fgithub.com\u002Frobomotionio\u002Frobomotion-skills\u002Fblob\u002Fmain\u002Fsupabase-skills\u002Fskills\u002Fsupabase-postgres-best-practices\u002FSKILL.md",[212,215],{"categoryNo":213,"categoryName":214,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":216,"categoryName":217,"taxonomyType":29,"taxonomyTypeDesc":30},"01JBSEEDCAT000000000000033","数据分析师",[219,220,221,222,223,117,224,225,226,227,228,48,229,44,230,231,232,129,233,234],"best practices","supabase postgres best practices","supabase","postgres best practices","postgres","writing","performance","tasks","code","database","vector","plan","files","query","critical","impact",{"skillNo":236,"name":237,"nameZh":6,"description":238,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":239,"licenseFileUrl":6,"sourceHtmlUrl":240,"categories":241,"keywords":245,"publishedAt":52},"01M6DV40GRQ962SZH6C252N34A","scrapedo-search","Search Google and read web pages (as Markdown) through Scrape.do, keeping each result's link so every finding can be cited. Use for account and company research, competitor and pricing checks, finding a page that answers a question, or reading a page a search turned up.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Frobomotionio\u002Frobomotion-skills\u002Fblob\u002Fmain\u002Frobomotion-web\u002Fskills\u002Fscrapedo-search\u002FSKILL.md",[242],{"categoryNo":243,"categoryName":244,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000021","资料检索与研究",[48,246,247,248,51,249,250,251,252,253,254,40,255,256,257,258,259,260,261,262],"scrapedo search","research","pricing","api","scrape","markdown","access","page","question","only","up","do","outbound","pages","read web","as","link"]