Agent skill · writing content · sickn33
maintain-codex-wiki
Maintain a review-first engineering wiki with provenance, citation-aware queries, explicit capture and promotion, and deterministic checks.
Why this skill is useful
Provides structured methods for capturing and validating engineering knowledge that the AI wouldn't generate on its own.
What it needs
About 8k tokens when loaded. Last updated 2026-08-07. 44,571 stars on the source repository.
What this skill does
Maintain Codex Wiki Overview Maintain a repository-local Markdown wiki as compiled engineering knowledge, not as an automatic source of truth. Preserve provenance, separate evidence classes, and require review before wiki conclusions become repository rules, skills, or learning material. When to Use Query what a repository already knows about a technical decision or practice. Capture a durable lesson from a merged change, incident, review, or experiment. Ingest external research without silently treating it as authoritative. Reconcile conflicting or superseded guidance. Check wiki structure, citations, freshness, and index coverage. Promote verified knowledge into a rule, skill, module, or automated check. Do not invoke this workflow merely because a task produced code or chat output. No material wiki change is a valid result. Knowledge Contract Use a knowledge/ directory with these minimum surfaces: Each wiki page starts with one allowed status: verified, community, experimental, or decision. Choose the status from the evidence and operation. Capture and Archive pages default to experimental; never label them verified automatically. Use Last verified only for verified pages. For community, experimental, and decision pages, replace it with Last updated: YYYY-MM-DD. Use four source classes: official: current first-party documentation. repository: versioned evidence already present in the repository. community: an external implementation, article, or discussion. experiment: reproducible evaluation with setup and limitations. Official sources establish current product behavior. Community sources are patterns to test, not product specifications. Confinement Invariant Apply this before any operation reads, searches, or changes wiki state. For every wiki page, index, registry, log, cache target, and working-tree repository file inspected while capturing new evidence: 1. require a normalized repository-relative path; 2. reject absolute paths and .. components; 3. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills sickn33/maintain-codex-wiki--a48fb0