Use when the task involves reading, creating, or editing `.docx` documents, especially when formatting or layout fidelity matters; prefer `python-docx` plus the bundled `scripts/render_docx.py` for visual checks.
Use when a user gives a clear, generalizable correction about how a local skill should trigger or behave, or when a novel multi-step workflow is completed and the user approves continuing with it. Update the owning skill or create a narrow new skill, and record durable rules plus avoided paths under ~/.codex/skills.
Use whenever working inside any source repository or project workspace, especially if the task may create helper scripts, generated artifacts, scratch notes, exported reports, screenshots, debug logs, temporary data files, or test/validation run waste. Keeps the repository clean by routing auxiliary files outside the repo, using external workspace paths by default, cleaning accidental repo clutter immediately, and sweeping disposable test artifacts when runs stop.
Convert screenshot or image sequences into deterministic MP4 review clips. Use when Codex needs to merge screenshots or still-image frames into video from a folder, glob, numbered pattern, or JSON manifest, especially for sparse frame-step captures, per-sequence review clips, or sidecar report generation.
Use when the user explicitly asks for a desktop or system screenshot (full screen, specific app or window, or a pixel region), or when tool-specific capture capabilities are unavailable and an OS-level capture is needed.
Convert a user-trained multi-step workflow into a reusable Codex skill or a stable workflow template. Use when the user asks to 固化 workflow, 抽象模板流程, 沉淀流程与提示, 把当前流程做成技能, 将多轮修正变成可复用框架, or quickly freeze an orchestration pattern for future tasks.
Use when the user wants local files or folders in Codex output to appear as clickable blue links, or when a response includes local paths the user is likely to open. Formats local filesystem references as absolute Markdown links that open the target file or directory in the Codex app.
Maintain manifest-driven shared/runtime memory frameworks that use file-backed shared source plus runtime working copies and SQLite sidecar indexes. Use when Codex needs to add or refactor memory families, validate/render/promote/query/compact memory stores, enforce shared-vs-local boundaries, or tune lifecycle rules such as dedupe, supersede, provenance, and temporal validity.