Token导航 LogoToken导航

Agent Skill · 研究检索

geo-audit(地理审计)

用于辅助安全审计、权限检查、凭据风险、认证流程和常见漏洞排查。它适合让 Agent 梳理敏感配置、检查依赖风险、分析鉴权逻辑或生成安全复核清单。使用时不能把工具输出直接当最终结论,涉及密钥、令牌、用户数据或生产系统时,应先确认最小权限、脱敏方式和操作边界。

geo-audit 是研究检索类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为需要联网;许可证信息还不明确,第三方扫描有提醒项,按安装量在研究检索类的 73,675 个 Skill 里排第 21,733。

总安装 4,774周安装 195GitHub Stars 6,909下载 1,544核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
unknown

安装方式

通过对话安装

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

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

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/zubair-trabzada/geo-seo-claude --skill geo-audit

这个 Skill 是做什么的

研究检索类 Skill 主要解决「找资料、核对事实、把来源整理清楚」的问题,通常会让助手先检索再总结。

geo-audit 用于辅助安全审计、权限检查和凭据风险排查。适合梳理敏感配置、分析鉴权逻辑或生成安全复核清单。通过 npx skills add 命令从指定 GitHub 仓库安装使用。不能将工具输出直接作为最终结论,涉及密钥或生产系统时应确认最小权限和操作边界。建议结合原始 README 核验具体用法和功能边界。

来源仓库内路径:skills/geo-audit

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/zubair-trabzada/geo-seo-claude --skill geo-aud…;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它需要需要联网,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

geo-audit 怎么安装?

在终端执行 npx skills add https://github.com/zubair-trabzada/geo-seo-claude --skill geo-audit。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

geo-audit 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

geo-audit 需要什么权限?

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

geo-audit 是免费的吗?

公开资料没有标注明确许可证,收费和商用限制都无法确认。正式使用前请到来源仓库核对授权说明。

geo-audit 用的人多吗?

公开数据是累计安装 4,774 次,近一周安装 195 次,下载 1,544 次,GitHub 6,909 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

geo-audit 安全吗?

第三方扫描有提醒项,说明存在需要人工确认的行为。安装前请打开源码看清它读了什么、联网到哪里。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 来源仓库有 6,909 星,维护活跃度相对可查。

先想清楚的地方

  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方扫描存在提醒项或未通过项,需要人工逐条确认。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理研究检索类任务、又不想每次都手写提示词的人。

不太适合

  • 需要明确授权才能用到公司项目里的场景。
  • 需要厂商级技术支持和 SLA 的生产系统。

研究检索类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
find-skills

寻找技能 · Codex、Claude

31,199,81316,486操作浏览器MIT有提醒
self-improving-agent

自我改进 Agent · OpenClaw

16,464,0023,396接触敏感数据MIT-0通过
soultrace

灵魂追踪 · Codex、Claude

7,588,94412需要联网未明确有提醒
self-improving

自我完善 · OpenClaw

6,829,2841,046需要联网MIT-0通过
microsoft-foundry

微软代工厂 · Codex、Claude

6,614,144764调用外部服务未明确有提醒
geo-audit

地理审计 · 本页

4,7746,909需要联网未明确有提醒

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

GEO Audit Orchestration Skill

Purpose

This skill performs a comprehensive Generative Engine Optimization (GEO) audit of any website. GEO is the practice of optimizing web content so that AI systems (ChatGPT, Claude, Perplexity, Gemini, etc.) can discover, understand, cite, and recommend it. This audit measures how well a site performs across all GEO dimensions and produces an actionable improvement plan.

Key Insight

Traditional SEO optimizes for search engine rankings. GEO optimizes for AI citation and recommendation. Sites that score high on GEO metrics see 30-115% more visibility in AI-generated responses (Georgia Tech / Princeton / IIT Delhi 2024 study). The two disciplines overlap but have distinct requirements.


Audit Workflow

Phase 1: Discovery and Reconnaissance

Step 1: Fetch Homepage and Detect Business Type

  1. Use WebFetch to retrieve the homepage at the provided URL.
  2. Extract the following signals:

- Page title, meta description, H1 heading - Navigation menu items (reveals site structure) - Footer content (reveals business info, location, legal pages) - Schema.org markup on homepage (Organization, LocalBusiness, etc.) - Pricing page link (SaaS indicator) - Product listing patterns (E-commerce indicator) - Blog/resource section (Publisher indicator) - Service pages (Agency indicator) - Address/phone/Google Maps embed (Local business indicator)

  1. Classify the business type using these patterns:
Business TypeDetection Signals
SaaSPricing page, "Sign up" / "Free trial" CTAs, app.domain.com subdomain, feature comparison tables, integration pages
Local BusinessPhysical address on homepage, Google Maps embed, "Near me" content, LocalBusiness schema, service area pages
E-commerceProduct listings, shopping cart, product schema, category pages, price displays, "Add to cart" buttons
PublisherBlog-heavy navigation, article schema, author pages, date-based archives, RSS feeds, high content volume
Agency/ServicesCase studies, portfolio, "Our Work" section, team page, client logos, service descriptions
HybridCombination of above signals -- classify by dominant pattern

Step 2: Crawl Sitemap and Internal Links

  1. Attempt to fetch /sitemap.xml and /sitemap_index.xml.
  2. If sitemap exists, extract up to 50 unique page URLs prioritized by:

- Homepage (always include) - Top-level navigation pages - High-value pages (pricing, about, contact, key service/product pages) - Blog posts (sample 5-10 most recent) - Category/landing pages

  1. If no sitemap exists, crawl internal links from the homepage:

- Extract all <a href> links pointing to the same domain - Follow up to 2 levels deep - Prioritize pages linked from main navigation

  1. Respect robots.txt directives -- do not fetch disallowed paths.
  2. Enforce a maximum of 50 pages and a 30-second timeout per fetch.

Step 3: Collect Page-Level Data

For each page in the crawl set, record:

  • URL, title, meta description, canonical URL
  • H1-H6 heading structure
  • Word count of main content
  • Schema.org types present
  • Internal/external link counts
  • Images with/without alt text
  • Open Graph and Twitter Card meta tags
  • Response status code
  • Whether the page has structured data

Phase 2: Parallel Subagent Delegation

Delegate analysis to 5 specialized subagents. Each subagent operates on the collected page data and produces a category score (0-100) plus findings.

Subagent 1: AI Visibility Analysis (geo-ai-visibility)

  • Analyze content blocks for quotability by AI systems (citability scoring)
  • Check AI crawler access via robots.txt and llms.txt presence
  • Scan brand presence across YouTube, Reddit, Wikipedia, LinkedIn
  • Score brand authority signals that AI models use for entity recognition

Subagent 2: Platform Optimization (geo-platform-analysis)

  • Assess readiness for Google AI Overviews, ChatGPT, Perplexity, Gemini, Bing Copilot
  • Check platform-specific ranking factors and optimization opportunities

Subagent 3: Technical GEO Infrastructure (geo-technical)

  • Analyze robots.txt for AI crawler access
  • Verify meta tags, headers, and technical accessibility for AI systems
  • Check page speed, server-side rendering, and Core Web Vitals
  • Assess security headers and mobile optimization

Subagent 4: Content E-E-A-T Quality (geo-content)

  • Evaluate Experience, Expertise, Authoritativeness, Trustworthiness signals
  • Check author bios, credentials, source citations
  • Assess content freshness, depth, and originality
  • Verify "About" page quality and team credentials

Subagent 5: Schema & Structured Data (geo-schema)

  • Validate all schema.org markup
  • Check for GEO-critical schema types (FAQ, HowTo, Organization, Product, Article)
  • Assess schema completeness and accuracy
  • Identify missing schema opportunities

Phase 3: Score Aggregation and Report Generation

Composite GEO Score Calculation

The overall GEO Score (0-100) is a weighted average of six category scores:

CategoryWeightWhat It Measures
AI Citability25%How quotable/extractable content is for AI systems
Brand Authority20%Third-party mentions, entity recognition signals
Content E-E-A-T20%Experience, Expertise, Authoritativeness, Trustworthiness
Technical GEO15%AI crawler access, llms.txt, rendering, speed
Schema & Structured Data10%Schema.org markup quality and completeness
Platform Optimization10%Presence on platforms AI models train on and cite

Formula:

GEO_Score = (Citability * 0.25) + (Brand * 0.20) + (EEAT * 0.20) + (Technical * 0.15) + (Schema * 0.10) + (Platform * 0.10)
Score Interpretation
Score RangeRatingInterpretation
90-100ExcellentTop-tier GEO optimization; site is highly likely to be cited by AI
75-89GoodStrong GEO foundation with room for improvement
60-74FairModerate GEO presence; significant optimization opportunities exist
40-59PoorWeak GEO signals; AI systems may struggle to cite or recommend
0-39CriticalMinimal GEO optimization; site is largely invisible to AI systems

Issue Severity Classification

Every issue found during the audit is classified by severity:

Critical (Fix Immediately)

  • All AI crawlers blocked in robots.txt
  • No indexable content (JavaScript-rendered only with no SSR)
  • Domain-level noindex directive
  • Site returns 5xx errors on key pages
  • Complete absence of any structured data
  • Brand not recognized as an entity by any AI system

High (Fix Within 1 Week)

  • Key AI crawlers (GPTBot, ClaudeBot, PerplexityBot) blocked
  • No llms.txt file present
  • Zero question-answering content blocks on key pages
  • Missing Organization or LocalBusiness schema
  • No author attribution on content pages
  • All content behind login/paywall with no preview

Medium (Fix Within 1 Month)

  • Partial AI crawler blocking (some allowed, some blocked)
  • llms.txt exists but is incomplete or malformed
  • Content blocks average under 50 citability score
  • Missing FAQ schema on pages with FAQ content
  • Thin author bios without credentials
  • No Wikipedia or Reddit brand presence

Low (Optimize When Possible)

  • Minor schema validation errors
  • Some images missing alt text
  • Content freshness issues on non-critical pages
  • Missing Open Graph tags
  • Suboptimal heading hierarchy on some pages
  • LinkedIn company page exists but is incomplete

Output Format

Generate a file called GEO-AUDIT-REPORT.md with the following structure:

# GEO Audit Report: [Site Name]

**Audit Date:** [Date]
**URL:** [URL]
**Business Type:** [Detected Type]
**Pages Analyzed:** [Count]

---

## Executive Summary

**Overall GEO Score: [X]/100 ([Rating])**

[2-3 sentence summary of the site's GEO health, biggest strengths, and most critical gaps.]

### Score Breakdown

| Category | Score | Weight | Weighted Score |
|---|---|---|---|
| AI Citability | [X]/100 | 25% | [X] |
| Brand Authority | [X]/100 | 20% | [X] |
| Content E-E-A-T | [X]/100 | 20% | [X] |
| Technical GEO | [X]/100 | 15% | [X] |
| Schema & Structured Data | [X]/100 | 10% | [X] |
| Platform Optimization | [X]/100 | 10% | [X] |
| **Overall GEO Score** | | | **[X]/100** |

---

## Critical Issues (Fix Immediately)

[List each critical issue with specific page URLs and recommended fix]

## High Priority Issues

[List each high-priority issue with details]

## Medium Priority Issues

[List each medium-priority issue]

## Low Priority Issues

[List each low-priority issue]

---

## Category Deep Dives

### AI Citability ([X]/100)
[Detailed findings, examples of good/bad passages, rewrite suggestions]

### Brand Authority ([X]/100)
[Platform presence map, mention volume, sentiment]

### Content E-E-A-T ([X]/100)
[Author quality, source citations, freshness, depth]

### Technical GEO ([X]/100)
[Crawler access, llms.txt, rendering, headers]

### Schema & Structured Data ([X]/100)
[Schema types found, validation results, missing opportunities]

### Platform Optimization ([X]/100)
[Presence on YouTube, Reddit, Wikipedia, etc.]

---

## Quick Wins (Implement This Week)

1. [Specific, actionable quick win with expected impact]
2. [Another quick win]
3. [Another quick win]
4. [Another quick win]
5. [Another quick win]

## 30-Day Action Plan

### Week 1: [Theme]
- [ ] Action item 1
- [ ] Action item 2

### Week 2: [Theme]
- [ ] Action item 1
- [ ] Action item 2

### Week 3: [Theme]
- [ ] Action item 1
- [ ] Action item 2

### Week 4: [Theme]
- [ ] Action item 1
- [ ] Action item 2

---

## Appendix: Pages Analyzed

| URL | Title | GEO Issues |
|---|---|---|
| [url] | [title] | [issue count] |

Quality Gates

  • Page Limit: Never crawl more than 50 pages per audit. Prioritize high-value pages.
  • Timeout: 30-second maximum per page fetch. Skip pages that exceed this.
  • Robots.txt: Always check and respect robots.txt before crawling. Note any AI-specific directives.
  • Rate Limiting: Wait at least 1 second between page fetches to avoid overloading the server.
  • Error Handling: Log failed fetches but continue the audit. Report fetch failures in the appendix.
  • Content Type: Only analyze HTML pages. Skip PDFs, images, and other binary content.
  • Deduplication: Canonicalize URLs before crawling. Skip duplicate content (e.g., HTTP vs HTTPS, www vs non-www, trailing slashes).

Business-Type-Specific Audit Adjustments

SaaS Sites

  • Extra weight on: Feature comparison tables (high citability), integration pages, documentation quality
  • Check for: API documentation structure, changelog pages, knowledge base organization
  • Key schema: SoftwareApplication, FAQPage, HowTo

Local Businesses

  • Extra weight on: NAP consistency, Google Business Profile signals, local schema
  • Check for: Service area pages, location-specific content, review markup
  • Key schema: LocalBusiness, GeoCoordinates, OpeningHoursSpecification

E-commerce Sites

  • Extra weight on: Product descriptions (citability), comparison content, buying guides
  • Check for: Product schema completeness, review aggregation, FAQ sections on product pages
  • Key schema: Product, AggregateRating, Offer, BreadcrumbList

Publishers

  • Extra weight on: Article quality, author credentials, source citation practices
  • Check for: Article schema, author pages, publication date freshness, original research
  • Key schema: Article, NewsArticle, Person (author), ClaimReview

Agency/Services

  • Extra weight on: Case studies (citability), expertise demonstration, thought leadership
  • Check for: Portfolio schema, team credentials, industry-specific expertise signals
  • Key schema: Organization, Service, Person (team), Review

平台分布

Codex

34.94%
按下载量换算539

Claude

29.76%
按下载量换算459

Cursor

17.9%
按下载量换算276

Gemini CLI

9.59%
按下载量换算148

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

可疑

权限和风险

需要联网

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

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在提醒或未通过项,安装前请自行复核。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills