OpenSkillIndex← back to search
claude-code

Oh-my-codex ask-claude

Ask Claude via local CLI and capture a reusable artifact

install
source · Clone the upstream repo
git clone https://github.com/Yeachan-Heo/oh-my-codex
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/Yeachan-Heo/oh-my-codex "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/ask-claude" ~/.claude/skills/yeachan-heo-oh-my-codex-ask-claude && rm -rf "$T"
manifest: skills/ask-claude/SKILL.md
source content

Ask Claude (Local CLI)

Use the locally installed Claude CLI as a direct external advisor for focused questions, reviews, or second opinions.

Usage

/ask-claude <question or task>

Routing

Preferred: Local CLI execution

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.

Missing binary behavior

If 

claude
is not found, do not switch to MCP. Instead:

  1. Explain that local Claude CLI is required for this skill.
  2. Ask the user to install/configure Claude CLI.
  3. Provide a quick verification command:
claude --version

Artifact requirement

After local execution, save a markdown artifact to:

.omx/artifacts/claude-<slug>-<timestamp>.md

Minimum artifact sections:

  1. Original user task
  2. Final prompt sent to Claude CLI
  3. Claude output (raw)
  4. Concise summary
  5. Action items / next steps

Task: {{ARGUMENTS}}