ask — Claude Code skill: route prompts across AI models
Skill to route prompts through local CLIs of different models (Claude, Codex, Gemini, Cursor and others) and save results as artifacts.
npx skills add Yeachan-Heo/oh-my-claudecode --skill ask -a claude-codeWhat ask does
ask redirects a question to your chosen model via a single omc ask command instead of calling each provider's CLI directly. The result is saved to .omc/artifacts/ask/ with a timestamp and provider name.
It works like this: you pick a provider (claude, codex, gemini, cursor, antigravity, grok, or muse) and state your task, then the skill runs omc ask {{provider}} {{text}}. Flags and version compatibility are handled automatically — no manual CLI assembly needed. On Windows, Antigravity has a limitation; use omc ask gemini instead.
Requires the chosen CLI installed locally and authenticated. Verify with claude --version, codex --version, or similar for your provider. Muse and Grok need versions that support --prompt-file.
What it helps with
- route a request to the right AI assistant with one command
- save an agent's response as an artifact without manual copy-paste
- avoid errors when building CLI flags for different providers
- work with multiple models in a single project
- get a critic's review of your implementation plan
Example prompts for the agent
- /oh-my-claudecode:ask claude "draft an implementation plan for issue #123"
- /oh-my-claudecode:ask codex "review this patch from a security perspective"
- /oh-my-claudecode:ask cursor "apply this plan to the codebase"
How to install ask
1Skills CLI (Vercel)
npx skills add Yeachan-Heo/oh-my-claudecode --skill ask -a claude-code2Manually: put the files in place
~/.claude/skills/ask/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/ask/
1Skills CLI (Vercel)
npx skills add Yeachan-Heo/oh-my-claudecode --skill ask -a codex2Manually: put the files in place
.agents/skills/ask/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add Yeachan-Heo/oh-my-claudecode --skill ask -a cursor2Manually: put the files in place
.cursor/skills/ask/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install Yeachan-Heo/oh-my-claudecode ask2Manually: put the files in place
.github/skills/ask/SKILL.md1Skills CLI (Vercel)
npx skills add Yeachan-Heo/oh-my-claudecode --skill ask -a gemini-cli2Platform CLI
gemini skills install https://github.com/Yeachan-Heo/oh-my-claudecode --path skills/askManually: put the files in place
.devin/skills/ask/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add Yeachan-Heo/oh-my-claudecode --skill ask -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
From the same set26
The whole set →Similar
Questions about ask
How do I install ask in Claude Code?
Run npx skills add Yeachan-Heo/oh-my-claudecode --skill ask -a claude-code. The skill will be available at ~/.claude/skills/ask/SKILL.md.
What does ask do?
ask routes your question to a chosen local CLI model (Claude, Codex, Gemini, Cursor, etc.), handles flags automatically, and saves the result as an artifact.
Which models are supported?
ask works with Claude, Codex, Gemini, Cursor, Antigravity, Grok, and Muse. On Windows, Antigravity has limitations; use Gemini instead.
Source text
SKILL.md · MIT
---
name: ask
description: Process-first advisor routing for Claude, Codex, Gemini, Antigravity, Grok, Cursor, or Muse via `omc ask`, with artifact capture and no raw CLI assembly
---
# Ask
Use OMC's canonical advisor skill to route a prompt through the local Claude, Codex, Gemini, Antigravity, Grok, Cursor, or Muse CLI and persist the result as an ask artifact.
## Usage
```bash
/oh-my-claudecode:ask <claude|codex|gemini|antigravity|grok|cursor|muse> <question or task>
```
Examples:
```bash
/oh-my-claudecode:ask codex "review this patch from a security perspective"
/oh-my-claudecode:ask gemini "suggest UX improvements for this flow"
/oh-my-claudecode:ask antigravity "suggest UX improvements for this flow"
/oh-my-claudecode:ask claude "draft an implementation plan for issue #123"
/oh-my-claudecode:ask cursor "apply this implementation plan"
/oh-my-claudecode:ask muse --agent-prompt critic "review this plan"
```
## Routing
**Required execution path — always use this command:**
```bash
omc ask {{ARGUMENTS}}
```
**Do NOT manually construct raw provider CLI commands.** Never run `codex`, `claude`, `gemini`, `agy`, `grok`, `cursor-agent`, or `muse` directly to fulfill this skill. The `omc ask` wrapper handles correct flag selection, artifact persistence, and provider-version compatibility automatically. Manually assembling provider CLI flags will produce incorrect or outdated invocations.
## Requirements
- The selected local CLI must be installed and authenticated.
- Verify availability with the matching command:
```bash
claude --version
codex --version
gemini --version
agy --version
grok --version
cursor-agent --version
muse --version
```
- **Antigravity CLI install** (Google's successor to the Gemini CLI): install the `agy`
binary per the [official Antigravity instructions](https://antigravity.google) (inspect
any installer before running it). Verify: `agy --version`
> **Platform note:** `omc ask antigravity` is supported on macOS/Linux. On Windows it is guarded with a clear error, because `agy --print` takes the prompt as an argv value (it cannot read stdin) and has known upstream Windows `-p` limitations; use `omc ask gemini` on Windows.
- **Gemini CLI** remains supported for enterprise/API-key use cases.
- **Muse and Grok** require versions supporting `--prompt-file`. The wrapper uses private temporary files for prompts, including role files with YAML frontmatter. Muse runs with approvals disabled and preserves its configured sandbox behavior.
## Artifacts
`omc ask` writes artifacts to:
```text
.omc/artifacts/ask/<provider>-<slug>-<timestamp>.md
```
Task: {{ARGUMENTS}}
© Yeachan-Heo · MIT · Yeachan-Heo/oh-my-claudecode