yao-geo-page-audit

yao-geo-page-audit is a skill for Claude Code, Codex from yaojingang/yao-geo-skills. It costs 41 tokens per session (1,001 once invoked), scanned A, original, MIT.

A GEO readiness review for a website page or a small group of pages. It checks whether public content can be discovered, extracted, understood, supported by evidence, and cited in AI-generated answers.

In plain words
What is it for?
It helps assess a homepage and representative pages, improve their structure and evidence, and produce a Chinese report with fixes for developers and content teams. It does not estimate AI rankings or recall without supplied platform samples.
Why use it?
A page can look correct to visitors but still be hard for search-driven AI systems to parse or trust. The review turns those problems into specific content, HTML, schema, and development recommendations.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit It helps assess a homepage and representative pages, improve their structure and evidence, and produce a Chinese report with fixes for developers and content teams. It does not estimate AI rankings or recall without supplied platform samples.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/yaojingang/yao-geo-skills/yao-geo-page-audit
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.

Any agent
npx skills add yaojingang/yao-geo-skills --skill yao-geo-page-audit
Clone the repo
git clone --depth 1 https://github.com/yaojingang/yao-geo-skills

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for yao-geo-page-audit

README.md
[![agentmods](https://agentmods.dev/badge/skills/yaojingang/yao-geo-skills/yao-geo-page-audit/github.svg)](https://agentmods.dev/skills/yaojingang/yao-geo-skills/yao-geo-page-audit)
Your own site
<a href="https://agentmods.dev/skills/yaojingang/yao-geo-skills/yao-geo-page-audit"><img src="https://agentmods.dev/badge/skills/yaojingang/yao-geo-skills/yao-geo-page-audit/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for yao-geo-page-audit

Your own site · 80×15
<a href="https://agentmods.dev/skills/yaojingang/yao-geo-skills/yao-geo-page-audit"><img src="https://agentmods.dev/badge/skills/yaojingang/yao-geo-skills/yao-geo-page-audit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 41 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,001 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.1 $0.00041 $0.01001
Opus 5.5 $0.00016 $0.00400
Sonnet 5.5 $0.00008 $0.00200
Haiku 4.5 $0.00004 $0.00100

Measured 2mo ago against content hash a8308fc3b954, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

yao-geo-page-audit 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 2mo ago.

The scan reads SKILL.md. This mod also ships 2 executable files (scripts/polish_docx.py, scripts/review_report_layout.py), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

skills/yao-geo-page-audit/SKILL.md · 60 lines

How it starts

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

yao-geo-page-audit

Use this skill when the user wants a GEO Page Audit, website/page GEO diagnosis, page technical audit, AI extractability audit, schema/HTML module advice, or code/content repair list for a URL.

Job

Given a target URL or website, diagnose the homepage, a representative first-level page, and a representative second-level page when possible. Output development-ready and content-ready recommendations that improve how public pages can be discovered, parsed, cited, and summarized by search-driven AI systems. By default, analyze public page readiness and public evidence coverage only; do not estimate AI-platform recall, rankings, citation share, or internal platform behavior unless the user provides platform sampling data.

Workflow

  1. Read references/research-foundation.md, references/authority-reference-model.md, and references/report-module-taxonomy.md. Frame the audit as a five-stage chain: discovery, retrieval candidate, main-content extraction, evidence quality, generated citation.
  2. Identify page type and sample scope. If the input is a homepage, select homepage, one representative first-level page, and one representative second-level page. State the selection basis and unresolved input gaps.
  3. Build an evidence ledger. Prefer official pages, official docs, schema/source code, standards, and peer-reviewed or arXiv research before third-party commentary. Mark each finding as observed, official, standard, research, inferred, or input gap.
  4. Check crawlability and renderability: status code, robots, sitemap, canonical, meta robots, mobile-first parity, JavaScript dependency, and whether primary content appears in initial HTML.
  5. Check structural quality: H1-H3, main/article, summary, table of contents, FAQ, tables, lists, breadcrumbs, internal links, anchor text, accessibility headings, and schema.
  6. Check content evidence: conclusions first, full entity names, data, citations, cases, dates, author/source, freshness, objectivity, price, service boundaries, regional constraints, and source accountability.
  7. Check AI extractability and public-answer material coverage: key-value facts, atomic facts, comparison tables, steps, Q&A, context-independent summary, paragraph independence, entity graph, sameAs links, and chunk-level citation readiness. Convert domestic platform concerns into high-intent question material gaps, not platform recall claims.
  8. Produce code-layer fixes, content-layer fixes, page-module suggestions, schema/HTML snippets, priority, owner, acceptance test, risk, and estimated cost.
  9. Deliver Word, PDF, sticky-menu HTML, and Markdown from one Markdown content source. Use the kami editorial report style in references/report-formatting-spec.md and references/output-layout-policy.md.
  10. After DOCX generation, run scripts/polish_docx.py to apply Kami-style Word typography, margins, and table formatting.
  11. Run scripts/review_report_layout.py and references/quality-gates.md before claiming completion.

Read the full file on GitHub · 60 lines

Files

What ships with it

30 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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. 2mo ago First seen · 60 lines · 41 tokens per session scan A a8308fc3b954

Subscribe to this mod's changes

yao-geo-page-audit is a skill published in the GitHub repository yaojingang/yao-geo-skills (910 stars, last pushed 29d ago), licensed MIT. It adds 41 tokens to every session and 1,001 once invoked, about $0.0002 per session on Opus 5.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

officecli-academic-paper

Use this skill to build academic-style .docx output: journal / conference / thesis chapters carrying formal citation style (APA, Chicago, IEEE, MLA), numbered equations, figure & table cross-references, footnotes/endnotes, bibliography, or multi-column journal layout. Trigger on: 'research paper', 'journal paper'…

iOfficeAI/OfficeCLI · 141 tokens

officecli

Create, analyze, proofread, and modify Office documents (.docx, .xlsx, .pptx) using the officecli CLI tool. Use when the user wants to create, inspect, check formatting, find issues, add charts, or modify Office documents.

iOfficeAI/OfficeCLI · 56 tokens

obsidian-bases

Create and edit Obsidian Bases (.base files) with views, filters, formulas, and summaries. Use when working with .base files, creating database-like views of notes, or when the user mentions Bases, table views, card views, filters, or formulas in Obsidian.

kepano/obsidian-skills · 63 tokens

skillshare

Manage skills, agents, extras, hooks, plugins, and MCP connection settings with the Skillshare CLI. Use when the user asks to configure or run Skillshare, install or sync resources across AI tools, manage shared memory notes, review a session for lessons or dream over saved memories, import MCP settings, manage…

runkids/skillshare · 103 tokens

skillshare-implement-feature

Implement a feature from a spec file or description using TDD workflow. Use this skill whenever the user asks to: add a new CLI command, implement a feature from a spec, build new functionality, add a flag, create a new internal package, or write Go code for skillshare. This skill enforces test-first development…

runkids/skillshare · 114 tokens

skillshare-changelog

Generate CHANGELOG.md entry from recent commits in conventional format. Also syncs the website changelog page. Use this skill whenever the user asks to: generate a changelog, document what changed between tags, or create a new CHANGELOG entry. If you see requests like "write the changelog for v0.17", "what changed…

runkids/skillshare · 134 tokens