code-quality-audit
Use for read-only code quality, correctness, security, maintainability, observability, and operational audits that produce a ranked PROGRESS.md backlog in an isolated audit worktree.
codex-productivity-auditor
Audit a project and recent Codex session behavior to recommend Codex productivity setup across AGENTS.md, skills, hooks, MCP/plugins, subagents, local environment actions, automations, memories, and workflow docs. Use when the user asks how to make repeated steering second nature or asks what Codex setup is missing.
comet-browser-testing
Use when testing web apps with Perplexity/Comet browser automation, debugging with real browsers, verifying authenticated flows, or when client-side visual verification is needed. Load for dynamic content testing, form automation, console error checking, or when server-side logs alone are insufficient. This skill provides a 3-phase token-efficient methodology: (1) Server-side checks via process_logs MCP and curl, (2) Client-side verification via Comet MCP with specific prompts, (3) Learning loop via context graph storage.
context-budget
Analyze and report what is consuming the 200K context window. Use when the user says /context-budget, "what's eating my context", "how much context am I using", or wants to optimize token usage.
create-skill
Single entry for authoring, auditing, and optimizing Codex skills under .codex/skills/NAME. Three lanes: Create scaffolds a folder and SKILL.md template; Audit runs deterministic checks over frontmatter, naming, body size, description quality, and reference integrity; Optimize fixes audit findings such as description rewrites, body to references split, frontmatter repair, and name normalization. Use when the operator says create a skill, scaffold a skill, add SKILL.md, audit a skill, check skills, validate skill conformance, optimize a skill, fix a skill description, shrink a skill, or why is this skill not activating.
develop-web-game
Use when Codex is building or iterating on a web game (HTML/JS) and needs a reliable development + testing loop: implement small changes, run a Playwright-based test script with short input bursts and intentional pauses, inspect screenshots/text, and review console errors with render_game_to_text.
doc
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.
drams-design
Use when designing UI components, building layouts, creating page structures, or developing design systems following Dieter Rams' principles. Load for any task involving buttons, sliders, cards, forms, inputs, menus, headers, navigation, hero sections, grids, responsive layouts, page templates, tabs, toasts, modals, alerts, loading states, or UI/layout elements that need to be innovative, useful, aesthetic, understandable, unobtrusive, honest, long-lasting, thorough, environmentally friendly, or embody 'less but better' design philosophy.
eval
Scaffold PoC projects, test workflows against eval criteria. Use for /eval, "test this workflow". NOT for scoring (/eval-score) or improving (/autoimprove).
execplan
Create living execution documents for complex multi-step tasks. Use for /execplan, "create a plan". NOT for quick tasks or code reviews — only structured phased planning.
figma-implement-design
Translates Figma designs into production-ready application code with 1:1 visual fidelity. Use when implementing UI code from Figma files, when user mentions "implement design", "generate code", "implement component", provides Figma URLs, or asks to build components matching Figma specs. For Figma canvas writes via `use_figma`, use `figma-use`.
frontend-skill
Use when the task asks for a visually strong landing page, website, app, prototype, demo, or game UI. This skill enforces restrained composition, image-led hierarchy, cohesive content structure, and tasteful motion while avoiding generic cards, weak branding, and UI clutter.
github-ci-fix
Use when a user asks to publish, debug, or fix a GitHub change until the PR is ready to merge. Create or reuse the PR, diagnose GitHub Actions failures with `gh`, address active merge-blocking review comments autonomously when safe, and stay in a PR-to-mergeable loop until required checks are green and no fixable blocker remains. After the PR is ready to merge, run `session-introspection` to capture anti-recurrence controls.
harness-audit
Check system setup health across 7 categories. Use for /harness-audit, "verify my setup", "check harness". NOT for project quality (/audit) or eval scoring (/eval-score).
html-artifact
Produce a single self-contained HTML file as the deliverable for information-dense tasks that benefit from tables, SVG diagrams, inline code annotations, side-by-side comparisons, tabs, interactive controls, or copy-back affordances. Lanes: plan, review, report, prototype, editor. Use when the operator asks for an HTML artifact, HTML file, single-page HTML, HTML explainer, HTML spec, PR review in HTML, incident or status report as HTML, implementation plan in HTML, feature explainer, concept explainer, flowchart, SVG diagram, slide deck, design-system docs, component variant gallery, drag-drop triage board, feature-flag admin UI, prompt tuner, shareable explainer, or throwaway UI/editor. Do not use for high-design marketing pages or production apps.
jupyter-notebook
Use when the user asks to create, scaffold, or edit Jupyter notebooks (`.ipynb`) for experiments, explorations, or tutorials; prefer the bundled templates and run the helper script `new_notebook.py` to generate a clean starting notebook.
learn
Save a reusable pattern from this session to the knowledge base. Use for /learn, "remember this", "save this pattern". NOT for session state (/save-session) or full session review (/introspect).
learning-recommendations
Use when presenting learning recommendations from background analysis, reviewing pending pattern suggestions, or approving automation scripts from traces. Load when learning-agent has findings to present.
llm-council
Run high-stakes questions, ideas, and decisions through a council of 5 AI advisors who analyze independently, peer-review each other anonymously, and synthesize a final verdict with artifacts. Mandatory triggers: 'council this', 'run the council', 'war room this', 'pressure-test this', 'stress-test this', 'debate this'. Strong triggers when paired with a real decision or tradeoff: 'should I X or Y', 'which option', 'what would you do', 'is this the right move', 'validate this', 'get multiple perspectives', 'I can't decide', 'I'm torn between'. Do not use for factual lookups, simple yes/no questions, summarization, or low-stakes choices.
mac-widget-design
Use when creating, updating, or verifying a local macOS WidgetKit widget, especially desktop widgets with a native black dashboard visual system, reliable local install/run workflow, app-group snapshot/cache internals, timeline reloads, and real desktop screenshot proof.
macos-app-optimizer
Use when analyzing macOS apps for optimization opportunities, improving memory/RAM usage, reducing memory leaks, optimizing SwiftUI performance, or analyzing Swift code for efficiency. Load for any macOS app performance analysis or memory optimization task.
onecli-integration
Configure or modify OneCLI integrations in agentic apps. Use when adding `@onecli-sh/sdk`, wiring OneCLI into container or process launchers, managing OneCLI agent identifiers, or adding manual approval flows.
operate
Run the autonomous control plane loop — orient, identify, act, verify, update, introspect. Use for /operate, "run the loop", "what needs doing". NOT for single-task work — use specific skills instead.
Use when tasks involve reading, creating, or reviewing PDF files where rendering and layout matter; prefer visual checks by rendering pages (Poppler) and use Python tools such as `reportlab`, `pdfplumber`, and `pypdf` for generation and extraction.
playwright-interactive
Persistent browser and Electron interaction through `js_repl` for fast iterative UI debugging.
playwright
Use when the task requires automating a real browser from the terminal (navigation, form filling, snapshots, screenshots, data extraction, UI-flow debugging) via `playwright-cli` or the bundled wrapper script.
project-context-router
Decide where instructions, memory, plans, and artifacts should live between global Codex baseline and project-specific files. Use when creating/updating AGENTS/ROADMAP/memory docs, introducing new workflow rules, or deciding whether content belongs in ~/.codex/rules versus a repository.
project-governance-bootstrap
Bootstrap organized project or workspace governance using Linear for execution, Notion for durable memory, AGENTS-triggered docs, MCP/auth setup, and no-drift workflow controls. Use when starting a new repo/workspace or retrofitting ad hoc project management into a governed operating model.
quality-radar-remediation
Run a bounded quality audit across a repo or control plane, split the scan into 3-5 evidence lanes, consolidate overlapping findings, and remediate the highest-leverage issues with one main-agent owner. Use when a user wants a broad hygiene pass, drift audit, regression triage, control-plane review, or a parallel analysis followed by direct remediation.
render-deploy
Deploy applications to Render by analyzing codebases, generating render.yaml Blueprints, and providing Dashboard deeplinks. Use when the user wants to deploy, host, publish, or set up their application on Render's cloud platform.
repo-readiness-bootstrap
Bootstrap or assess a Codex-first day-one readiness baseline for an unfamiliar repo. Use when entering a repo for the first time, making a repo agent-runnable, or needing one canonical readiness report before implementation.
research
Process a research article or blog post into actionable insights for the knowledge base. Use for /research, "process this article", "extract insights from". NOT for web search or code review.
sample-app-benchmark
Run a reusable fresh-app benchmark for a new idea, tool, or control-plane challenger by comparing a clean `main` baseline against a committed challenger branch in separate top-level Codex sessions with isolated benchmark environments.
screenshot
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.
security-best-practices
Perform language and framework specific security best-practice reviews and suggest improvements. Trigger only when the user explicitly requests security best practices guidance, a security review/report, or secure-by-default coding help. Trigger only for supported languages (python, javascript/typescript, go). Do not trigger for general code review, debugging, or non-security tasks.
security-ownership-map
Analyze git repositories to build a security ownership topology (people-to-file), compute bus factor and sensitive-code ownership, and export CSV/JSON for graph databases and visualization. Trigger only when the user explicitly wants a security-oriented ownership or bus-factor analysis grounded in git history (for example: orphaned sensitive code, security maintainers, CODEOWNERS reality checks for risk, sensitive hotspots, or ownership clusters). Do not trigger for general maintainer lists or non-security ownership questions.
security-threat-model
Repository-grounded threat modeling that enumerates trust boundaries, assets, attacker capabilities, abuse paths, and mitigations, and writes a concise Markdown threat model. Trigger only when the user explicitly asks to threat model a codebase or path, enumerate threats/abuse paths, or perform AppSec threat modeling. Do not trigger for general architecture summaries, code review, or non-security design work.
sentry
Use when the user asks to inspect Sentry issues or events, summarize recent production errors, or pull basic Sentry health data via the Sentry API; perform read-only queries with the bundled script and require `SENTRY_AUTH_TOKEN`.
session-introspection
Close meaningful sessions by capturing only preventable friction, choosing the narrowest durable control that would stop recurrence, routing it to one owner, and applying obvious safe controls immediately.
skill-portfolio-review
Audit the entire skill portfolio for redundancy, misplacement, staleness, and context bloat. Use for /skill-portfolio-review, 'review my skills', 'clean up skills', 'are any skills redundant', or after adding 3+ new skills since last review. Produces DELETE/MERGE/REFRAME/KEEP recommendations per skill. NOT for auditing a single skill (/skill-quality-gate) or project quality (/audit).
skill-profile
>
skill-quality-gate
Audit a skill against Anthropic's production best practices (9-point scorecard). Use after creating or improving any skill via /skill-creator. Also use when user says 'audit skill', 'check skill quality', 'review my skill', or wants to validate a skill before distribution. NOT for project-level audits (/audit) or harness health (/harness-audit).
sora
Use when the user asks to generate, edit, extend, poll, list, download, or delete Sora videos, create reusable non-human Sora character references, or run local multi-video queues via the bundled CLI (`scripts/sora.py`); includes requests like: (i) generate AI video, (ii) edit this Sora clip, (iii) extend this video, (iv) create a character reference, (v) download video/thumbnail/spritesheet, and (vi) Sora batch planning; requires `OPENAI_API_KEY` and Sora API access.
speech
Use when the user asks for text-to-speech narration or voiceover, accessibility reads, audio prompts, or batch speech generation via the OpenAI Audio API; run the bundled CLI (`scripts/text_to_speech.py`) with built-in voices and require `OPENAI_API_KEY` for live calls. Custom voice creation is out of scope.
transcribe
Transcribe audio files to text with optional diarization and known-speaker hints. Use when a user asks to transcribe speech from audio/video, extract text from recordings, or label speakers in interviews or meetings.
verify
Run structured quality gate against current project. Use for /verify, "verify the build", "run quality checks". NOT for eval scoring (/eval-score) or auditing (/audit).
webmcp
Use when a web app should expose browser-native WebMCP tools and you need to integrate, verify, troubleshoot, or directly operate that app through Chrome's WebMCP early-preview runtime. Trigger for requests like "enable WebMCP", "integrate WebMCP into this dashboard", "why is navigator.modelContext missing", "why can tools register but not execute", "test WebMCP", or "operate this app through WebMCP".
winui-app
Bootstrap, develop, and design modern WinUI 3 desktop applications with C# and the Windows App SDK using official Microsoft guidance, WinUI Gallery patterns, Windows App SDK samples, and CommunityToolkit components. Use when creating a brand new app, preparing a machine for WinUI, reviewing, refactoring, planning, troubleshooting, environment-checking, or setting up WinUI 3 XAML, controls, navigation, windowing, theming, accessibility, responsiveness, performance, deployment, or related Windows app design and development work.
workflow-cli
Reference for modifying workflow.py or managing ~/.codex/docs/. Use when the user asks about workflow CLI commands, adding or updating docs, alias registration, workflow registry or lint issues, or fixing workflow command behavior. NOT for general CLI design principles (/cli-for-agents).
worktree-orchestrator
Use when spawning parallel Claude Code subagents in git worktrees for code review, architecture analysis, SDK verification, or testing. Load for multi-agent codebase optimization, parallel PR creation, or orchestrating Claude Code features across isolated worktrees. Triggers: 'parallel analysis', 'worktree review', 'multi-agent optimization', 'spawn reviewers', 'orchestrate worktrees', 'smart review'.
Page 2 of 2 · 100 results