Menu
[OMX] Ask Claude via local CLI and capture a reusable artifact
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
[OMX] Run an anti-slop cleanup/refactor/deslop workflow
[OMX] Run read-only deep repository analysis and return a ranked synthesis with explicit confidence, concrete file references, and clear evidence-vs-inference boundaries. Use when a user says 'analyze', 'investigate', 'why does', 'what's causing', or needs grounded cross-file explanation before any changes are proposed.
[OMX] Ask Gemini via local CLI and capture a reusable artifact
[OMX] Full autonomous execution from idea to working code
[OMX] Stateful validator-gated research loop with native-hook persistence
[OMX] Cancel any active OMX mode (autopilot, ralph, ultrawork, ecomode, ultraqa, swarm, ultrapilot, pipeline, team)
| name | ask-claude |
| description | [OMX] Ask Claude via local CLI and capture a reusable artifact |
Use the locally installed Claude CLI as a direct external advisor for focused questions, reviews, or second opinions.
/ask-claude <question or task>
Run Claude through the canonical OMX CLI command path (no MCP routing):
omx ask claude "{{ARGUMENTS}}"
Exact non-interactive Claude CLI command from claude --help:
claude -p "{{ARGUMENTS}}"
# equivalent: claude --print "{{ARGUMENTS}}"
If needed, adapt to the user's installed Claude CLI variant while keeping local execution as the default path.
Legacy compatibility entrypoints (./scripts/ask-claude.sh, npm run ask:claude -- ...) are transitional wrappers.
If claude is not found, do not switch to MCP.
Instead:
claude --version
After local execution, save a markdown artifact to:
.omx/artifacts/claude-<slug>-<timestamp>.md
Minimum artifact sections:
Task: {{ARGUMENTS}}