home / skills / yeachan-heo / oh-my-claudecode / ask-gemini

ask-gemini skill

safe

/skills/ask-gemini

This skill lets you consult Gemini locally and capture reusable advisory artifacts for iterative AI-assisted coding workflows.

npx playbooks add skill yeachan-heo/oh-my-claudecode --skill ask-gemini

Review the files below or copy the command above to add this skill to your agents.

Files (1)

SKILL.md

674 B

---
name: ask-gemini
description: Ask Gemini via local CLI and capture a reusable artifact
---

# Ask Gemini

Use Gemini as an external advisor through OMC's ask command.

## Usage

```bash
/oh-my-claudecode:ask-gemini <question or task>
```

## Routing

Preferred path:

```bash
omc ask gemini "{{ARGUMENTS}}"
```

Wrapper alias (compatibility):

```bash
bash "${CLAUDE_PLUGIN_ROOT}/scripts/ask-gemini.sh" "{{ARGUMENTS}}"
```

## Requirements

- Local Gemini CLI must be installed and authenticated.
- Verify with:

```bash
gemini --version
```

## Artifacts

`omc ask` writes artifacts to:

```text
.omc/artifacts/ask/gemini-<slug>-<timestamp>.md
```

Task: {{ARGUMENTS}}

Overview

This skill lets you query Gemini from the local CLI and captures the response as a reusable artifact. It integrates with the omc ask command to route prompts to Gemini and store outputs in a timestamped markdown file. Use it to get external advice, code suggestions, or design input while keeping an auditable artifact of the interaction.

How this skill works

When you run the ask-gemini command via the omc ask or the Bash wrapper, the skill forwards your question to the locally installed Gemini CLI. The CLI response is captured and written into a consistent artifact file under the .omc/artifacts/ask directory with a slug and timestamp. Artifacts are plain markdown so you can review, share, or feed them into other workflows.

When to use it

You need external model advice or coding suggestions during a team workflow.
You want to capture and version responses from Gemini for audits or reviews.
You prefer invoking Gemini from the local environment rather than a web UI.
You need a reusable artifact to attach to tickets, PRs, or documentation.

Best practices

Ensure the local Gemini CLI is installed and authenticated before running the command.
Phrase prompts clearly and include context for reproducible results.
Use concise slugs or identifiers in prompts so artifact filenames remain meaningful.
Store artifacts in your project or link them to related issues for team visibility.
Verify gemini --version to confirm the CLI is accessible in CI or local shells.

Example use cases

Ask for a code refactor suggestion and save the response as an artifact to attach to a pull request.
Request design tradeoffs for an architecture decision and keep the answer for team discussion.
Generate unit test ideas for a module and store them as markdown for later implementation.
Run a quick code review prompt from your terminal and archive the model feedback.

FAQ

What do I need installed?

A local Gemini CLI that is installed and authenticated. Verify with gemini --version.

Where are responses saved?

Responses are written to .omc/artifacts/ask/gemini-<slug>-<timestamp>.md for easy reuse and tracking.