WebisityStudioWebisityStudio/claude-codex-mcp-bridge/skills/ask-codex/SKILL.md

ask-codex

Skill2 starsChanged 3 months agoMITView on GitHub

Sends one bounded implementation, investigation, or verification task to Codex without manually managing bridge threads.

10 other projects use a version of this.

Adopted by

Most recently taken up by

maxatwork/skillstheir own version, first seen Nov 8, 2026
finalize/skillstheir own version, first seen Nov 1, 2026
madeordinary/serel-memorytheir own version, first seen Nov 1, 2026
PolyArch/humanizetheir own version, first seen Oct 8, 2026
BackToCimaCoppi/Praxistheir own version, first seen Sep 23, 2026
Yumeno/add_codexclitheir own version, first seen Sep 19, 2026

Other versions10 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 10
PolyArch/humanize★ 1.5ksame name
Sateezg/codex-bridge★ 248same name
bookSiYi1412/ask-codex★ 9same name
s977043/river-review★ 7same name
BackToCimaCoppi/Praxis★ 6same name
yeaight7/agent-powerups★ 6same name
madeordinary/serel-memory★ 1same name
finalize/skills★ 0same name
maxatwork/skills★ 0same name
Yumeno/add_codexcli★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository2 other files it gives its agents.
- claude-codex-coordinatorSkill
- review-with-codexSkill

The file

We split this skill into the rules it gives an agent

6 rules. 0 are common, 1 is distinctive, and 5 are very specific to this project.

0
Common
Most of the 7 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.

Common
Distinctive
Very specific
could be automatic: a setting could enforce it

Very specific:
Use the ask_codex MCP tool for the user's request.
line 10
Very specific:
Keep the default worktree for implementation work.
line 13
Very specific:
If the result warns about uncommitted changes and the task depends on them, run again with includeUncommitted: true.
line 14
Very specific:
If the status is running_codex, tell the user Codex is still working and carry on.
line 15
Very specific:
If Codex returns waiting_for_fable, answer the question and continue with bridge_continue_codex using the returned run ID.
line 16
Distinctive:
Do not commit, push, merge, deploy, publish, send externally, alter credentials, delete data, or mutate production without explicit …
line 18

“Common” is measured: kept by at least 6 in 10 of the 7 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.

Files

SKILL.md

Ask Codex

Use the ask_codex MCP tool for the user's request.

Pass the user's task in request without diluting its acceptance criteria. The project defaults to this session's project; pass projectPath only for a different repository.
Keep the default worktree for implementation work. Use useWorktree: false only when the user explicitly wants work in the current checkout.
If the result warns about uncommitted changes and the task depends on them, run again with includeUncommitted: true.
If the status is running_codex, tell the user Codex is still working and carry on. The result arrives in your mailbox from bridge; you can also call bridge_orchestration_wait with the run ID. Never start a duplicate run.
If Codex returns waiting_for_fable, answer the question and continue with bridge_continue_codex using the returned run ID.
Report changed files and real verification evidence. Compare Codex's filesChanged with the bridge's observedChanges before calling the work done.
Do not commit, push, merge, deploy, publish, send externally, alter credentials, delete data, or mutate production without explicit approval.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

It worked
Partly
It didn't

What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free