agentleFS
GhanyteGhanyte/geo-seo-audit/geo/SKILL.md

geo

Skill9 starsChanged 7 months agoMITView on GitHub

GEO Audit Toolkit — evidence-based Generative Engine Optimization audit for websites. Diagnostic-only (no commercial framing): produces a multi-page audit with per-LLM presence assessment (ChatGPT/Google, Gemini/Google, Perplexity/multi, Claude/Brave, Le Chat/Brave), a unified action plan with per-LLM impact tags, and technical appendices. Use when the user says "geo", "audit", "AI search", "AI visibility", "schema", "BLUF", or provides a URL for analysis.

22 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use geo-report-pdf, geo-technical and 8 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • kennyolofsson23-netizenSkill

    geo-report-pdf

    Generate a professional PDF report from GEO audit data using ReportLab. Creates a polished, client-ready PDF with score gauges, bar charts, platform readiness visualizations, color-coded tables, and prioritized action plans.

    Also in 5 projects that use this

  • kennyolofsson23-netizenSkill

    geo-technical

    Technical SEO audit with GEO-specific checks — crawlability, indexability, security, performance, SSR, and AI crawler access

    Also in 5 projects that use this

  • +8 more from kennyolofsson23-netizen

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 0 are distinctive, and 3 are very specific to this project.

  • 0

    Common

    Most of the 17 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Every audit lands in site-client/<slug>/audits/<YYYY-MM-DD>-audit.md.

    line 90
  2. Very specific:

    Audit-only: no pricing tiers, no MRR projections, no "client-ready" framing.

    line 128
  3. Very specific:

    Evidence triage: every finding tagged with confidence (high → experimental).

    line 130

“Common” is measured: kept by at least 6 in 10 of the 17 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

GEO Audit Toolkit — Claude Code skill

Philosophy: audit-only, evidence-based, no sales framing. Findings are reported in severity × confidence × per-LLM impact, never in pricing tiers or revenue projections.


Single command

/geo audit <url> [--positioning "<query>"] [--vs comp1.com,comp2.com] [--output-lang fr|en]

Examples:

# Audit with positioning + 2 competitors, output in French
/geo audit https://example.com --positioning "agence powerpoint" --vs mprez.fr,laboiteaslides.fr --output-lang fr

# Audit without RRF measurement (on-page only)
/geo audit https://example.com

Internally calls python3 -m scripts.run_audit <url> .... The orchestrator is sequential (not parallel-subagent) and produces a single Markdown audit at site-client/<slug>/audits/<date>-audit.md.


Per-LLM retrieval map (rev. 2026-04-26)

LLM (in scope)BackendEngine in audit
ChatGPT / SearchGPTGoogle (OpenAI–Google deal 2025)google (Startpage proxy)
Gemini / Google AI OverviewsGooglegoogle
PerplexityMulti (Google + Brave)google + brave
ClaudeBrave (Anthropic–Brave 2025)brave
Le Chat (Mistral)Brave (Brave–Mistral 2025)brave

Bing Copilot, Meta AI, Grok are out of scope (user decision, 2026-04-26). Mapping validated empirically: 80–90% Google SERP similarity vs ~30% Bing when comparing ChatGPT citations to scraper-baseline. See docs/LLM_RETRIEVAL_ARCHITECTURE.md.


Audit pipeline (5 phases, sequential)

PhaseWhat runsOutput
1. Locale detectionscripts/site_locale.py (HTML lang → Content-Language → TLD → fallback)fr-FR, en-US, etc.
2. Multi-page samplingscripts/site_crawler.py (sitemap + strategic diversity: home + service + article + about + case-study)up to 8 pages
3. Crawler audit (site-level)scripts/checks/crawlers.py (robots.txt parse + 3-category bot taxonomy)findings
4. Per-page schema + content healthscripts/checks/schema.py + scripts/checks/content_health.pyfindings per page
5. RRF measurement (when --positioning)scripts/rrf.py + scripts/serp/{google,brave}.py (10 fan-out queries × 2 engines)per-LLM presence stats

Audit output structure

1. État des lieux par LLM        ← verdict table + 5 detail blocks
2. Plan d'action                  ← unified, per-LLM impact tags + experimental sub-bucket
3. Ce que l'audit ne mesure pas

Annexes techniques:
  A. RRF mesuré (détail)
  B. Politique des crawlers IA
  C. Données structurées (schema)
  D. Content health (BLUF, etc.)
  E. Findings — vue agrégée

Glossaire technique

Every audit lands in site-client/<slug>/audits/<YYYY-MM-DD>-audit.md. Path resolved via scripts/client_paths.py.


Active sub-skills (6)

#SkillWrapsPurpose
1geo-auditscripts/run_audit.pyMain orchestrator
2geo-schemascripts/checks/schema.pySchema.org + Enhanced Entity Pages audit
3geo-content-healthscripts/checks/content_health.pyBLUF + Mount AI anti-patterns
4geo-crawlersscripts/checks/crawlers.pyrobots.txt + 3-category bot taxonomy
5geo-rrfscripts/rrf.pyReciprocal Rank Fusion measurement
6geo-clientscripts/client_paths.pyPer-site folder manager (site-client/<slug>/)

The fork dropped 9 upstream skills that did not fit the audit-only pivot (geo-prospect, geo-proposal, geo-brand-mentions, geo-citability, geo-llmstxt, geo-platform-optimizer, geo-technical, geo-content, geo-report, geo-report-pdf, geo-compare). See tasks/lessons.md.


Local-only tooling

local/ is gitignored. Contains personal scripts that don't ship in the public toolkit:

  • local/docx_export.py — convert audit Markdown to a styled .docx (Google Docs ready). Usage:
    python3 local/docx_export.py site-client/<slug>/audits/<date>-audit.md

Quality gates

  • Audit-only: no pricing tiers, no MRR projections, no "client-ready" framing. Findings carry effort × score-gain × confidence.
  • Evidence triage: every finding tagged with confidence (high → experimental). Single-study correlations and emerging patterns are flagged, not promoted to critical.
  • Free, no-setup: pipeline runs without paid APIs or signup. SERP scraping uses public interfaces (Google via Startpage proxy, Brave HTML).
  • Output language follows audited site's locale (override with --output-lang fr|en).
  • Per-LLM retrieval map re-verified every 6 months — partnership deals change quickly. See tasks/lessons.md (2026-04-26 entry).

Reference docs

  • docs/LLM_RETRIEVAL_ARCHITECTURE.md — per-LLM backend mapping
  • docs/CRAWLERS_TAXONOMY.md — 29 AI bots catalogued
  • docs/STRUCTURED_DATA_BEST_PRACTICES.md — Schema.org / EEP methodology
  • docs/CONTENT_HEALTH_PATTERNS.md — Mount AI anti-patterns + BLUF
  • docs/BRAVE_GRAIL_SIGNALS.md — Brave-rooted LLM evidence (Test #1 result)
  • docs/sources/ — 8 archived methodology articles with critical-thinking triage

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.