Codex Skills sync and catalog governance
How local skill or plugin changes become durable repository artifacts: inspect the repo instructions, compare local skill homes to the allowlisted suite, decide whether new local work belongs in the curated catalog, regenerate source-backed indexes, review docs-site output, and record drift or blockers before publishing or handoff.
Workflow steps
- 1
Inspect AGENTS.md, README.md, suite metadata, plugin backups, and current git status before changing skill or catalog surfaces
Action
- 2
Run the source comparison or catalog artifact check to identify local skill changes, stale repo files, source-only files, or suite allowlist drift
Process
- 3
Human operator decides whether new local work should enter the curated public suite, remain local-only, or stay blocked for later review
Decision
- 4
Regenerate approved catalog artifacts such as skills/INDEX.md, skills/manifest.json, and docs-site/src/lib/catalog.generated.ts
Action
- 5
Create evidence by running catalog checks, docs-site build or local server review, and screenshot proof for representative catalog and detail routes
Action
- 6
Record the artifact paths, command results, unresolved drift, human review state, and next checkpoint before merge, publish, or handoff
State