| name | docs-watch |
| description | Check docs.celo.org and other live sources for drift against this repo's cached reference files (contracts, network info, docs sitemap, ecosystem, grants) and fix or flag it. Use when asked to check docs updates, run the docs watch, or on the scheduled weekly run. |
celopedia-skills docs upstream watch
Goal: detect when the facts mirrored into skills/celopedia-skill/references/
have drifted from their live sources, and surface every finding — mechanical
fixes and ambiguous/high-stakes flags alike — in one reviewable pull
request per run, opened against celo-org/celopedia-skills:main (the
canonical upstream repo, not a fork), so a human can approve, edit, or
close it. This builds on the process already documented in this repo's
README.md ("Contributing" section: check docs.celo.org → update the file
→ bump version → open a PR) but replaces its own ad hoc reports/issues with
a single PR as the one place everything gets reviewed.
Sources checked
| # | Source | Fetch command (see live-data-sources.md for more) | Reference file |
|---|
| 1 | Docs sitemap | curl -s https://docs.celo.org/llms.txt | docs-map.md |
| 2 | Contract addresses | https://docs.celo.org/tooling/contracts/core-contracts + token-contracts + l1-contracts + uniswap-contracts (WebFetch) | contracts.md |
| 3 | Network info | https://docs.celo.org/build-on-celo/network-overview (WebFetch) | network-info.md |
| 4 | Ecosystem / TVL | curl -s https://api.llama.fi/protocols | jq '[.[] | select(.chains[]? == "Celo")]' | ecosystem.md |
| 5 | Grant programs | curl -s https://www.celopg.eco/programs (WebFetch) | grants-funding.md |
Procedure
-
Load the snapshot at .claude/skills/docs-watch/snapshot.md — the
facts we currently rely on, with the date each was last verified.
-
Fetch each source above and extract the same facts the corresponding
reference file documents (page list, address table, chain params,
protocol list, program status table).
-
Diff each source against both the snapshot and the current content of
its reference file.
-
Classify every delta:
no action — cosmetic/unrelated (e.g. a docs page's prose changed but
not its existence or URL). Not mentioned in the PR.reference update — mechanical, unambiguous fact change: a sitemap page
added/removed/renamed, a DeFi protocol added/removed from the Celo chain
list, a grant program's Live/Past status flipped, a new fee-currency
token added. Edit the reference file directly with the corrected fact,
on the run's branch (see step 5) — do not commit or PR per-item.needs review — anything ambiguous or high-stakes (a contract address
that doesn't match, a chain ID / fee-currency address change, anything
touching contracts.md core protocol addresses or network-info.md
chain IDs). Do not edit the file — never guess a fix for these.
Instead, write a clearly-marked entry describing exactly what was
observed vs. what's cached, for the "Needs review" section of the PR
body (step 5).
-
Every run ends one of three ways — always distinguishable from each
other by whether/how a PR shows up, since this skill never writes report
files:
Notes
live-data-sources.md already documents the priority order (live API >
official docs > hardcoded references > ecosystem directory) — this skill
exists to keep the "hardcoded references" tier honest, not to replace live
lookups elsewhere.- Never guess a contract address or chain parameter to "fix" a
needs review item — that tier exists specifically so factual corrections to
security-sensitive data always get a human's eyes first.
