Loading...
Loading...
Found 502 Skills
Multi-instance (Multi-Agent) orchestration workflow for deep research: Split a research goal into parallel sub-goals, run child processes in the default `workspace-write` sandbox using Codex CLI (`codex exec`); prioritize installed skills for networking and data collection, followed by MCP tools; aggregate sub-results with scripts and refine them chapter by chapter, and finally deliver "finished report file path + key conclusions/recommendations summary". Applicable to: systematic web/data research, competitor/industry analysis, batch link/dataset shard retrieval, long-form writing and evidence integration, or scenarios where users mention "deep research/Deep Research/Wide Research/multi-Agent parallel research/multi-process research".
This is intended for use when OpenSpec workflows require dependency-aware parallel subagents that are compatible with OPSX commands, legacy OpenSpec commands, and Codex CLI prompt aliases.
Debate implementation plans between Claude Code and Codex CLI. After Claude Code creates a plan, invoke this skill to have Codex review it. Both AIs debate through multiple rounds until reaching full consensus before implementation begins.
Run OpenAI's Codex CLI agent in non-interactive mode using `codex exec`. Use when delegating coding tasks to Codex, running Codex in scripts/automation, or when needing a second agent to work on a task in parallel.
OpenAI Codex CLI wrapper — three modes. Code review: independent diff review via codex review with pass/fail gate. Challenge: adversarial mode that tries to break your code. Consult: ask codex anything with session continuity for follow-ups. The "200 IQ autistic developer" second opinion. Use when asked to "codex review", "codex challenge", "ask codex", "second opinion", or "consult codex".
Use when experiments complete to judge what claims the results support, what they don't, and what evidence is still missing. Codex MCP evaluates results against intended claims and routes to next action (pivot, supplement, or confirm). Use after experiments finish — before writing the paper or running ablations.
Create and scaffold plugin directories for Codex with a required `.codex-plugin/plugin.json`, optional plugin folders/files, and baseline placeholders you can edit before publishing or testing. Use when Codex needs to create a new local plugin, add optional plugin structure, or generate or update repo-root `.agents/plugins/marketplace.json` entries for plugin ordering and availability metadata.
Run, watch, debug, and extend OpenClaw QA testing with qa-lab and qa-channel. Use when Codex needs to execute the repo-backed QA suite, inspect live QA artifacts, debug failing scenarios, add new QA scenarios, or explain the OpenClaw QA workflow. Prefer the live OpenAI lane with regular openai/gpt-5.4 in fast mode; do not use gpt-5.4-pro or gpt-5.4-mini unless the user explicitly overrides that policy.
Apply, switch, and restore Codex desktop themes from the local ~/.codexthemes library with one command, and report which theme is currently active. Use when a user asks to apply or activate a theme they created or installed, switch between installed themes, restore the native Codex look, or check or debug which theme is currently applied.
Professional code review with auto CHANGELOG generation, integrated with Codex AI
Run Codex CLI, Claude Code, OpenCode, or Pi Coding Agent via background process for programmatic control.
Send SMTP email notifications after Codex completes a task. Use when one Codex or Claude run is finished, or when you need to notify on task completion with device name, project name, status, and summary via email.