OpenSkillIndex← back to search
claude-code

Oh-my-codex ask-gemini

Ask Gemini 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-gemini" ~/.claude/skills/yeachan-heo-oh-my-codex-ask-gemini && rm -rf "$T"
manifest: skills/ask-gemini/SKILL.md
source content

Ask Gemini (Local CLI)

Use the locally installed Gemini CLI as a direct external advisor for brainstorming, design feedback, and second opinions.

Usage

/ask-gemini <question or task>

Routing

Preferred: Local CLI execution

Run Gemini through the canonical OMX CLI command path (no MCP routing):

omx ask gemini "{{ARGUMENTS}}"

Exact non-interactive Gemini CLI command from 

gemini --help
:

gemini -p "{{ARGUMENTS}}"
# equivalent: gemini --prompt "{{ARGUMENTS}}"

If needed, adapt to the user's installed Gemini CLI variant while keeping local execution as the default path.

Legacy compatibility entrypoints (

./scripts/ask-gemini.sh
, 
npm run ask:gemini -- ...
) are transitional wrappers.

Missing binary behavior

If 

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

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

Artifact requirement

After local execution, save a markdown artifact to:

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

Minimum artifact sections:

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

Task: {{ARGUMENTS}}