Token导航 LogoToken导航TokenDH.com
研究检索需要联网github未标认证来源可访问clear审计提醒

geo-aeo-optimization地理环境优化

Agent Skill

geo-aeo-optimization 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

2,154

周安装

88

GitHub Stars

10

下载量

690
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

3

许可证

MIT

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:geo-aeo-optimization(地理环境优化)
来源仓库:https://github.com/schwepps/skills
仓库路径:skills/geo-aeo-optimization
安装命令:
npx skills add https://github.com/schwepps/skills --skill geo-aeo-optimization
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。不同来源提供的安装方式可能略有差异;本站展示可直接复制的安装命令,安装前请核对来源页面。

skills.shnpx skills
npx skills add https://github.com/schwepps/skills --skill geo-aeo-optimization

简介

geo-aeo-optimization 用于查找、检索和筛选相关信息,支持基于关键词或任务场景定位内容。

  • 适合在需要从文档、网页或结构化数据中提炼候选信息的场景下使用。
  • 通过 npx 安装,需结合原始 README 确认具体用法和参数约定。
  • 安装命令:npx skills add https://github.com/schwepps/skills --skill geo-aeo-optimization
  • 建议提前评估是否会触发联网、命令执行或文件读写,并确认相关权限边界。

SKILL.md

GEO & AEO Optimization Framework

Professional methodology for visibility in AI-powered search engines and generative AI responses.

Understanding GEO vs AEO vs SEO

SEO  → Rank in traditional search results (blue links)
AEO  → Appear in featured snippets, AI Overviews, voice answers
GEO  → Get cited in generative AI responses (ChatGPT, Claude, Perplexity)

2025 Reality:

  • 58% of queries are conversational
  • AI Overviews appear in ~47% of Google searches
  • Traditional CTR dropped 34.5% for top results due to AI answers
  • These strategies are complementary, not competing

When to Use This Skill

  • Optimizing content for AI search engines
  • Improving featured snippet capture rate
  • Auditing AI citation readiness
  • Restructuring content for AI extractability
  • Implementing E-E-A-T signals
  • Preparing for voice search

The Triple-Threat Framework

1. E-E-A-T Foundation (Required for All)

AI systems prioritize trusted, authoritative sources:

Experience   → First-hand knowledge, case studies, original research
Expertise    → Credentials, depth of knowledge, technical accuracy
Authority    → Citations, backlinks, mentions, brand recognition
Trustworthiness → Accuracy, transparency, clear sourcing

Implementation Checklist:

□ Author bio with credentials on every article
□ Link to authoritative sources
□ Include original data/research
□ Show methodology and sources
□ Update content regularly with visible dates
□ Display contact information
□ Include editorial guidelines

2. AEO: Featured Snippets & AI Overviews

Lead with the Answer:

  • First 40-60 words should directly answer the query
  • Use question-format H2 headers
  • Provide concise, extractable definitions

Content Structure for AEO:

## What is [Topic]?

[Direct answer in 1-2 sentences that can be extracted as a snippet]

[Supporting details and context follow]

Snippet-Optimized Formats:

Query TypeBest Format
"What is X?"Definition paragraph (40-60 words)
"How to X"Numbered steps (5-8 steps)
"Best X"Bulleted list with brief descriptions
"X vs Y"Comparison table
"Why X?"Direct answer + explanation

3. GEO: AI Citation Optimization

The CRASP Framework:

C - Clarity    → Unambiguous statements AI can quote
R - Relevance  → Match conversational query intent
A - Authority  → Cited sources, expert credentials
S - Structure  → Scannable, extractable format
P - Precision  → Specific facts, numbers, dates

High-Citation Content Elements:

  1. TL;DR blocks at the top
  2. Statistics with sources ("According to [Source], X increased by Y%")
  3. Expert quotes with attribution
  4. Definition lists for key terms
  5. Comparison tables with clear data
  6. FAQ sections with complete answers

Content Structure Template

# [H1: Primary Question or Topic]

**TL;DR:** [2-3 sentence summary with key facts]

## What is [Topic]? {#definition}

[Direct definition in 40-60 words - optimized for extraction]

[Expanded explanation with context]

## How [Topic] Works {#how-it-works}

[Step-by-step explanation]

1. **Step One**: [Description]
2. **Step Two**: [Description]
3. **Step Three**: [Description]

## Key Statistics

| Metric | Value | Source |
|--------|-------|--------|
| [Stat 1] | [Value] | [Source, Year] |
| [Stat 2] | [Value] | [Source, Year] |

## [Topic] vs [Alternative]

| Factor | [Topic] | [Alternative] |
|--------|---------|---------------|
| [Factor 1] | [Value] | [Value] |
| [Factor 2] | [Value] | [Value] |

## Frequently Asked Questions

### [Question 1]?

[Complete, standalone answer - 50-100 words]

### [Question 2]?

[Complete, standalone answer - 50-100 words]

## Expert Insights

> "[Quotable statement with specific insight]"
> — [Expert Name], [Title], [Organization]

---
*Last updated: [Date] | Author: [Name], [Credentials]*

Fact-Density Checklist

Extractability:
□ TL;DR or summary present at top
□ Paragraphs <120 words each
□ Clear topic sentences (first sentence = main point)
□ Bullet lists for features/benefits
□ Tables for comparisons
□ FAQ section with schema

Fact-Density:
□ Statistics with sources cited
□ Specific numbers and dates
□ Verifiable data points
□ Expert quotes with attribution
□ Original research/data
□ Named entities (people, companies, places)

Structure for AI:
□ Question-based H2 headers
□ Direct answers in first 40-60 words
□ Logical information hierarchy
□ Schema markup (FAQPage, HowTo, Article)

AI Crawler Configuration

robots.txt for AI Search Visibility:

# ALLOW search/chat features
User-agent: OAI-SearchBot
Allow: /

User-agent: ChatGPT-User
Allow: /

User-agent: PerplexityBot
Allow: /

User-agent: ClaudeBot
Allow: /

# OPTIONAL: Block training (keeps search)
User-agent: GPTBot
Disallow: /

User-agent: Google-Extended
Disallow: /

Critical: Ensure server-side rendering. AI crawlers often don't execute JavaScript well.

Schema Markup for AI

Priority Schema Types:

  1. FAQPage - Highest AI citation impact
  2. HowTo - Step-by-step visibility
  3. Article + Author - E-E-A-T signals
  4. Organization - Brand authority

FAQPage Example:

{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [{
    "@type": "Question",
    "name": "What is [topic]?",
    "acceptedAnswer": {
      "@type": "Answer",
      "text": "[Complete answer that can be extracted]"
    }
  }]
}

Output Format

# GEO/AEO Audit Report

**Page:** [URL]
**Date:** [Date]
**Overall Score:** X/100

## Executive Summary
[2-3 sentence AI search readiness assessment]

## Scores by Category

| Category | Score | Status |
|----------|-------|--------|
| E-E-A-T Signals | X/25 | [Good/Needs Work/Critical] |
| Content Structure | X/20 | [Good/Needs Work/Critical] |
| Fact-Density | X/20 | [Good/Needs Work/Critical] |
| Extractability | X/20 | [Good/Needs Work/Critical] |
| AI Technical Readiness | X/15 | [Good/Needs Work/Critical] |

## Priority Issues
1. **[Issue]** - [Impact] - [Fix]
2. **[Issue]** - [Impact] - [Fix]
3. **[Issue]** - [Impact] - [Fix]

## AI Visibility Assessment
[Current citation probability and gaps]

## Action Plan

**Immediate:**
- [ ] Add TL;DR to top articles
- [ ] Implement FAQ schema

**Short-term:**
- [ ] Restructure headers as questions
- [ ] Add author credentials

**Ongoing:**
- [ ] Monitor AI platform citations
- [ ] Update content freshness

Quick Audit (5-Point Check)

  1. TL;DR - Summary present at top?
  2. Structure - Question-based headers?
  3. Facts - Statistics with sources?
  4. E-E-A-T - Author credentials visible?
  5. Schema - FAQPage/HowTo markup?

Scoring Guide

  • 90-100: Excellent - High AI citation probability
  • 70-89: Good - Likely cited with minor improvements
  • 50-69: Needs Work - Significant optimization needed
  • Below 50: Critical - Major restructuring required

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

04

需要参考平台分布和安装热度时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

补充不同宿主或平台的使用分布数据

能力 5

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

Claude Code

26.6%
按下载量换算184

Gemini CLI

23.18%
按下载量换算160

OpenCode

17.56%
按下载量换算121

Antigravity

11.73%
按下载量换算81

Cursor

7.39%
按下载量换算51

github-copilot

3.53%
按下载量换算24

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

可疑

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在 warning/failed 结果,不能写成本站确认安全。

来源信息

继续浏览同类 Skills