geo-guide

A guide to Generative Engine Optimization, or GEO, for Sumo Logic documentation. GEO means structuring documents so AI tools are more likely to understand and cite them.

In plain words
What is it for?
Rewriting headings as questions, adding FAQs, applying concise BLUF writing, and adding JSON-LD metadata to Docusaurus documentation.
Why use it?
It explains when and how to adapt documentation for AI answers while preserving the regular documentation rules for other work.

Skill for Claude CodeCodex

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/sumologic/sumologic-documentation/geo-guide
Any agent
npx skills add SumoLogic/sumologic-documentation --skill geo-guide
Clone the repo
git clone --depth 1 https://github.com/SumoLogic/sumologic-documentation

Made for: Claude Code, Codex.

Per session 139 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,965 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00139 $0.01965
Opus 5 $0.00069 $0.00983
Sonnet 5 $0.00028 $0.00393
Haiku 4.5 $0.00014 $0.00197

Measured yesterday against content hash d29bc5302c8e, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

geo-guide scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured yesterday.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/skills/geo-guide/SKILL.md · 160 lines

How it starts

The opening of the file, as written. The whole thing — 160 lines — stays where its author put it; the contents beside it link to each section on GitHub.

GEO Reference — Sumo Logic Docs

What is GEO?

GEO optimizes documentation so AI tools like ChatGPT, Perplexity, and Gemini cite your content in their answers. Unlike SEO which targets search rankings, GEO targets AI citation frequency.

Frontmatter Template (GEO-optimized)

GEO changes heading style, page structure, frontmatter fields, and content layout in ways that diverge from the standard Sumo Logic style guide. Apply it only when explicitly requested. Apply GEO when the prompt contains phrases like:

  • "optimize for AI citation"
  • "GEO optimize this page"
  • "make this doc AI-friendly"
  • "make this citable by AI tools"
  • "add FAQ schema"
  • "add JSON-LD"
  • "add structured metadata"
  • "apply BLUF"
  • "rewrite headings as questions"

Do not apply GEO for:

  • Routine documentation updates, bug fixes, or content corrections
  • Standard new page creation without an explicit AI-optimization request
  • Pull requests that mention SEO but not GEO or AI citation
  • Any task where the prompt does not specifically ask for GEO

Sumo Logic doc pages live under /docs/ and follow this frontmatter pattern:

---
id: my-page-name
title: How to [Task] with Sumo Logic
sidebar_label: Short Nav Label
description: One sentence answering the page question for AI crawlers and search engines.
keywords:
  - Sumo Logic
  - feature or product name
  - capability term
---

When generating GEO-optimized frontmatter, add # [GEO: Principle N] inline comments next to each GEO-specific field so reviewers can immediately distinguish GEO additions from standard frontmatter fields. Remove these comments only if the project's YAML linter rejects them.

Rules:

  • title is phrased as a "How to" task statement (or a What/Why/Which question for concept pages) and matches the H1 (generated from frontmatter). Use "How to X", not "How do I X".
  • description is one sentence describing what the feature does and what problem it solves.
  • keywords include: the integrated product name, Sumo Logic, and 2–3 capability terms (for example: security, monitoring, logs).

Read the full file on GitHub · 160 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. yesterday First seen · 160 lines · 139 tokens per session scan A d29bc5302c8e

Subscribe to this mod's changes

geo-guide is a skill published in the GitHub repository SumoLogic/sumologic-documentation (42 stars, last pushed 3d ago), licensed MIT. It adds 139 tokens to every session and 1,965 once invoked, about $0.0007 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

qa-cli-mcp-api

Select and run explicitly requested, risk-based QA for Anarlog's CLI, webhooks, stdio MCP, hosted Cloud API, and remote MCP. Test only affected lanes unless comprehensive coverage is requested.

fastrepl/anarlog · 47 tokens

product-update-newsletter

Draft, update, or audit a crisp, changelog-grounded Anarlog product-update newsletter in Loops (app.loops.so) for a desktop release. Use after the changelog is merged, when asked to draft, revise, or pre-send check the release announcement email.

fastrepl/anarlog · 62 tokens

sqlite-schema-design

Design or review schemas for crates/cloudsync using SQLite Sync constraints, not generic SQLite advice. Use when adding synced tables, changing synced columns, or planning CloudSync-safe migrations.

fastrepl/anarlog · 42 tokens

release-new-version

Release a new desktop stable version for Anarlog. Use when asked to cut, publish, or prepare a new stable desktop release after checking and merging the changelog.

fastrepl/anarlog · 38 tokens

fix-ready-prs

Inspect every open non-draft PR for CI failures and unresolved Cursor Bugbot findings, then fix them on the existing PR branches. Use when asked to check active PRs, triage ready PRs, fix CI, or address Bugbot comments.

fastrepl/anarlog · 55 tokens

reactive-sqlite-ui

Build SQLite-backed reactive UI in apps/desktop using stable patterns for reads, selection, forms, writes, and loading states. Use when implementing or reviewing screens built on useDrizzleLiveQuery and SQLite mutations.

fastrepl/anarlog · 53 tokens