godview

name	godview
description	Query the verified god's-eye view of top-rated repos — transferable knowledge, agentic tooling, and community — or run its curation loop (digest a candidate, refresh freshness, check the gates). Trigger - user asks "what does <top repo> teach", "which agentic tools are trustworthy", "who is building X", "add <repo> to godview", or "/godview".

/godview — the flagship thin router

All curated truth lives in data/*.yml; this skill only routes. Never answer from memory when the data files can answer — and never claim something the registry doesn't back.

Route by intent

User wants…	Do
"What does teach?"	Read data/knowledge.yml (or the human render knowledge/README.md) entries whose sources include the repo's slug; relay the tier (✅/🌓/🟡/⚪) — never present a 🟡 claimed or ⚪ disputed card as fact; deep-dive via its digest in research/digests/
"Is true?"	Check data/knowledge.yml for a disputed (⚪) card first — the correction may already be recorded; otherwise verify at the claim's native altitude (code→read code, price→read pricing) before answering
"Which agentic tools are real/trustworthy?"	Read data/tooling.yml; relay the trust: field and the evidence file — never rank by stars alone
"Who's building the future of X?"	Read data/community.yml; every node has a why and provenance
"How fresh is this?"	make northstar (prints STALE flags — measured, not promised)
"Add repo X"	Append a candidate to data/registry.yml (candidacy criteria in the file), then make check. Promotion to 🟡 requires a SHA-pinned digest in research/digests/ — use a parallel sub-agent to digest, label UNCONFIRMED facts, never invent an install command
"Sync with upstreams"	make sync (NETWORK) → make build → review diff → open a PR. Merges stay human
"Is the repo green?"	make check (offline, deterministic; exit 0 = green)

Hard rules (from the registry's own laws)

• Satellites are never vendored — the seed worldmonitor is AGPL dual-licensed: pointer-only, run upstream. Same for every copyleft/unclear license.
• No evidence means no — an entry citing a non-digested source exists but doesn't count toward the north-star; don't present it as verified.
• Stars are gameable — check contributor graphs before nominating; rejected repos and reasons live in data/registry.yml under rejected:.
• Evidence tier is load-bearing — a card's tier is its trust level. Commentary (video/note) enters at 🟡 claimed and reaches ✅ verified-in-code only with an artifact_ref (someone read the code). A ⚪ disputed card IS the deliverable — it records where a source was wrong.