Maintain CodexMonitor and Codex app-server protocol parity. Use when asked to audit supported or missing app-server notifications/requests, trace event routing, diagnose schema drift in app-server payloads, or update docs/app-server-events.md after upstream Codex changes.
80
100%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Low
Low-risk findings worth noting
Use this skill to keep CodexMonitor app-server integration accurate as ../Codex evolves.
Start with:
docs/app-server-events.mdTreat that file as the canonical runbook and update it when behavior changes.
../Codex and update the hash in docs/app-server-events.md title.src/utils/appServerEvents.ts and src/features/app/hooks/useAppServerEvents.ts.Supported Events and Missing Events sections in docs/app-server-events.md.Supported Requests, Missing Client Requests, and Server Requests sections.../Codex/codex-rs/app-server-protocol/src/protocol/v2.rs.src/utils/appServerEvents.ts, src/features/app/hooks/useAppServerEvents.ts, and src/features/threads/utils/threadNormalize.ts.npm run typecheck.npm run test for frontend behavior changes.cd src-tauri && cargo check for backend changes.src/utils/appServerEvents.tssrc/features/app/hooks/useAppServerEvents.tssrc/features/threads/hooks/useThreadEventHandlers.tssrc/features/threads/hooks/useThreadItemEvents.ts, src/features/threads/hooks/useThreadTurnEvents.tssrc/features/threads/utils/threadNormalize.tssrc/features/threads/hooks/useThreadsReducer.tssrc/services/tauri.ts, src-tauri/src/shared/codex_core.rssrc-tauri/src/bin/codex_monitor_daemon/rpc.rs and rpc/*references/quick-commands.mddocs/app-server-events.mdWhen asked for an audit or update:
docs/app-server-events.md in the same change when behavior changed.dd61b9a
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.