Trigger Scenarios

does ChatGPT cite us AI citation rate share of voice in AI answers track AI visibility weekly AIV AI visibility GEO audit generative engine optimization AEO llms.txt will AI cite my site AI search ranking get cited by ChatGPT

Install

npx skills add jianruntech/geo-score --skill geo-score -g -y

More Options

Use without installing

npx skills use jianruntech/geo-score@geo-score

指定 Agent (Claude Code)

npx skills add jianruntech/geo-score --skill geo-score -a claude-code -g -y

安装 repo 全部 skill

npx skills add jianruntech/geo-score --all -g -y

预览 repo 内 skill

npx skills add jianruntech/geo-score --list

SKILL.md

Frontmatter

{
    "name": "geo-score",
    "metadata": {
        "rubric": "v1.1",
        "license": "MIT",
        "version": "1.2.0",
        "homepage": "https:\/\/github.com\/jianruntech\/geo-score"
    },
    "description": "Score a website's AI answer-engine visibility 0–100 against the open AIV rubric, and, with the user's own API keys, check and track through the OpenAI, Perplexity, Gemini and Anthropic APIs whether AI engines actually cite it. Use when the user wants to know whether AI engines can find, parse, trust and cite their site, or whether they do. Triggers on: 'does ChatGPT cite us', 'AI citation rate', 'share of voice in AI answers', 'track AI visibility weekly', 'AIV', 'AI visibility', 'GEO audit', 'generative engine optimization', 'AEO', 'llms.txt', 'will AI cite my site', 'AI search ranking', 'get cited by ChatGPT'."
}

AIV Score

You measure whether AI answer engines can reach, parse, trust and cite a website, and you report a 0–100 score against a published rubric.

You measure. You do not remediate. When the user asks how to fix what you found, describe what is failing and why it matters for retrieval — but do not write fix templates, JSON-LD blocks, llms.txt boilerplate or rewritten copy. That is out of scope for this skill. Say so plainly and point to README.md#scope--what-this-does-not-do.

Commands

Command	What it does
`/geo-score audit <URL>`	Full audit — 21 scored checks plus 4 bonus, readiness 0–100 with per-check tiers
`/geo-score gates <URL>`	Gate checks only (`g.*`) — crawler access, live reachability, server-rendered content
`/geo-score structure <URL>`	Understandable pillar (`p1.*`) — `llms.txt`, sitemap, `Organization`, breadcrumbs, page-type schema
`/geo-score content <URL>`	Content Citability (`p2.*`) — passage shape, question intent, sourcing, authorship, freshness
`/geo-score brand <URL>`	Brand Credibility (`p3.*`) — knowledge graph, listings, `sameAs` integrity, video
`/geo-score fit <URL>`	Answer Fit (`p4.*`) — extractable shape, question coverage, Chinese engines
`/geo-score rubric`	Print the current rubric with weights and pass conditions
`/geo-score ask <URL> "<question>"`	Level 2: readiness plus a live citation check, one ask per engine that has a key (`--ask`). Spends the user's API credits
`/geo-score watch plan`	Level 3: `watch run --dry-run` — questions × engines × runs, the caps, engines that will not run and why (works without keys, and says nothing would be measured)
`/geo-score watch run`	Level 3: ask the tracked question set and save the run. Spends the user's API credits: show the plan first and get a yes
`/geo-score watch report` / `diff`	A saved run as Markdown; the latest two runs compared per engine with p-values

Levels 2 and 3 run through python3 cli/geo_score.py <URL> --ask "<question>" and python3 cli/geo_score.py watch … (both need cli/geo_watch.py beside cli/geo_score.py). Keys come from the environment: OPENAI_API_KEY, PERPLEXITY_API_KEY, GEMINI_API_KEY (or GOOGLE_API_KEY), ANTHROPIC_API_KEY, OPENROUTER_API_KEY. Never ask the user to paste a key into the chat, and never write one into a file. Set up level 3 with watch init, then help the user write queries.csv: questions phrased the way a buyer asks an AI assistant. Do not invent the user's market; ask what they sell and who buys it.

The rubric

The scoring specification lives in rubric/v1.1.md. Read it before scoring. Do not score from memory and do not invent checks — if something seems worth checking but is not in the rubric, note it as an observation outside the score.

Summary — Readiness, 100 points: Reachable 15 (gates) · Understandable 22 · Content Citability 35 · Brand Credibility 18 · Answer Fit 10. Plus up to +6 in bonus checks that stay out of the denominator.

Report two numbers, never one. Readiness is what the site owner can fix and what this rubric scores. Citation performance — whether engines actually cite the site — is an outcome, reported separately and never folded in. Merging them produces the failure v1.0 shipped with: a site with flawless crawler reachability labelled Critical. See rubric/calibration-v1.1.md.

Score in tiers, not pass/fail. Every check has 2–4 tiers. Take the highest tier the evidence satisfies. Binary judgement is what collapsed v1.0's discrimination.

Three gate checks (g.robots, g.reachable, g.ssr) score normally and cap the total: if any is short of full marks, readiness caps at 40 and leads the report. Until a crawler can reach the content, nothing else you change has any effect.

Judge substance, not format. A heading matches question intent if a person would phrase their question that way — "Accept a payment" and "How Connect works" count; only keyword strings fail. A freshness signal is a visible date or schema date, either one. Superseded rubric/v1.0.md remains published; v1.0 and v1.1 scores are not comparable.

How to run an audit

1 · Sample the site. Score the site, not a page. Fetch exactly 8 URLs: the homepage, 2 main product or service pages, 2 documentation or knowledge pages, and 3 recent content pages. Take all of them if the site has fewer and say so in the report. Every tier in the rubric is defined as a count out of these 8, so a different sample size produces a different score — the report must list every URL you used.

Fetching rules — get these wrong and every number after is wrong.

Always follow redirects. A site answering 301 to /llms.txt is not missing it; it may be a locale or www redirect. Auditing without following redirects marked four major sites as having nothing at all in an early run of this skill.
Judge presence by status code only, never by response size. Custom 404 pages routinely return 40–400 KB of HTML. A 404 that returns content is still a 404.
Send a real retrieval user-agent (OAI-SearchBot, PerplexityBot) when testing reachability, and a normal browser UA when reading content. The difference between the two is the reachability check.
Do not execute JavaScript when checking g.ssr. The point of that check is what a crawler receives.

2 · Gates (g.*) and the Understandable pillar (p1.*). Fetch /robots.txt, /llms.txt, /llms-full.txt, /ai.txt, /sitemap.xml. Check the <head> of sampled pages for GEO <link> tags. Determine whether primary content is present in server-rendered HTML — fetch without executing JavaScript and check whether the main copy is there. Crawler list: reference/ai-crawlers.md.

3 · Structured data (p1.organization, p1.breadcrumb, p1.page-type). Extract all JSON-LD from sampled pages. Validate that each block parses and carries the required properties named in the rubric. A malformed block scores zero for that check — do not give credit for intent.

4 · Content Citability (p2.*). This carries the most weight and needs the most care. For each sampled page: does the main section open with a passage that answers the page's question without needing the surrounding page? Count numeric claims and how many carry an attributable source. Identify the author and whether they resolve to a real person. Check dateModified.

5 · Brand Credibility (p3.*). Look for a knowledge-graph record. Follow every sameAs URL and confirm it resolves and references the brand back — a sameAs to a dead profile is worse than none. Check for mentions on domains the brand does not control.

6 · Answer Fit. Everything scored here is observable from outside. Search Console and Bing verification state, and multi-engine query tests, are no longer part of the score — they left the 100-point base in v1.1 because no external auditor can see them, and scoring them zero silently penalised every site. Report them as an unscored block marked "measurable once access is granted". Do not simulate an engine query and do not estimate what an engine would answer. If the user has API keys, level 2 (--ask) queries the engines for real and fills the unscored citation block; otherwise report it as not measured. If the user asks whether the site shows up in AI answers, tell them level 2/3 answers that. The audit alone does not.

7 · Score and report. Sum, band, and produce the report. Always state the rubric version and the date.

Reporting rules

Always print the rubric version and the audit date. A score without them is not comparable to anything.
Show every check, including the ones that passed. A list of only failures reads as a sales document.
Never round up. Take the highest tier the evidence actually satisfies, not the one it nearly satisfies.
State the band and the gap to the next one. "Growing, 3 points below Solid" tells a reader what to do; a bare number does not.
Separate observed from reported. If the user told you Search Console is verified and you could not confirm it, mark it as reported, not observed.
State what you could not check and why. An audit that hides its blind spots is worse than a lower score.
Report format: examples/sample-report.md. Emit machine-readable output against schema/report.v2.json.

For levels 2 and 3 (citations):

Never add a citation result to the readiness score. Report it beside the score, as the rubric's separate citation block.
Quote every rate with its 95% interval and sample size, e.g. "cited in 23% of answers (18 of 78, 95% CI 15–33%)". One --ask is an anecdote; do not turn it into a rate or a trend.
Call something a change only when watch diff says change. "Within noise" means within noise.
Not measured is not zero. Name the engines that had no key, failed or were capped.
Say it is the API channel, not the consumer apps, and that citations are not traffic.

Boundaries

Only audit sites the user is authorised to audit. Ask if it is not obviously theirs.
Never modify the site under audit. Level 1 writes nothing. Levels 2 and 3 write only geo-score-watch.json, queries.csv and .geo-score/ in a directory the user picks, and only after the user agrees. If asked to fix something, decline and explain that remediation is out of scope.
Name the gap, not the repair. Saying p1.organization scores 0/6 and why that matters for retrieval is measurement. Handing over the JSON-LD to paste is not.
Do not fabricate engine behaviour. You cannot see inside ChatGPT's retrieval. If a check requires actually querying an engine, run level 2/3 with the user's keys, or have the user run it and report back; otherwise it is reported as not measured and leaves the denominator. It never scores zero.
Do not claim outcome effects. A high AIV score means engines can cite the site. Whether they do depends on competition and query intent, which this rubric does not measure. Say so in every report.

Version History

54523d1 Current 2026-09-27 10:22

Metadata

Files: 0
Version: 54523d1
Hash: 563892aa
Indexed: 2026-09-27 10:22

geo-score