Wiki Quality Audit
npm run wiki-qualityaudits the pages that shape future agents: read-first docs, routers, source-backed tool/skill pages, tweet/artifact evidence, and executable skill prompt load.
Routing
Open this page when Kevin asks for a broad article/tool/skill/wiki quality pass, when read-first documents feel stale, or when source-backed pages need stronger evidence surfaces. Use doctor.ts for structural health; use this audit for agent-load and research-quality debt.
Command
npm run wiki-quality
npm run wiki-quality -- --network --limit=60
npm run wiki-quality -- --json
The network mode samples the most reused non-X source URLs and reports live status. Treat 403/429 as follow-up signals, not automatic broken links; some sources block scripted fetches even when they load in a browser.
What It Checks
| Surface | Finding class |
|---|---|
| Read-first docs | Missing brain-first, skill-routing, freshness, wiki-closeout, or codification signals |
| Hubs and routers | Missing routing language, overly long scan-unfriendly hubs |
| Source-backed pages | Missing inline citations, important links that should be ::artifact cards |
| X-derived pages | Missing ::tweet artifacts for source-critical posts |
| Executable skills | Oversized prompts, missing disclosure folders, long descriptions, no-op prose |
First Fix Order
- Fix read-first warnings first; they affect every new conversation.
- Fix hub routing language so future agents discover the right category naturally.
- Add
::tweetand::artifactevidence to source-heavy pages. - Add inline citations to source-backed tools and skills.
- Use Browser Testing Skills to prune oversized skills and move branch-specific detail into
references/,docs/, orscripts/.
Output
Reports are written to outputs/audits/<YYYY-MM-DD>-wiki-quality.md or outputs/audits/<YYYY-MM-DD>-wiki-quality-network.md. The report is intentionally not a zero-warning gate yet; it is a queue for corpus refinement.
When a warning involves generated packs, registries, redirects, runtime views, or source/generator drift, update the source page or generator and follow Generated Surface Contract.
Timeline
- 2026-07-01 | Added generated-surface handling for quality-audit findings that involve packs, registries, redirects, runtime views, or source/generator drift. Source: User request, 2026-07-01
- 2026-06-25 | Added the corpus-quality audit route and
scripts/wiki-quality-audit.tsafter Kevin asked for a deeper audit of all articles, tools, skills, routers, and read-first documents with web research. Source: User request, 2026-06-25