geo-scorelisted

# 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 | ## The rubric The scoring specification lives in [`rubric/v1.1.md`](rubric/v1.1.md). **Read it before scoring.** Do not score from memory and do not invent