ask

Route prompts to Claude, Codex, or Gemini and persist responses as ask artifacts.

Updated Apr 29, 2026
One-click install
npx skills add https://github.com/nichobbs/lyric-lang --skill ask-nichobbs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ask
Source: https://github.com/nichobbs/lyric-lang/tree/main/.claude/skills/ask
Command: npx skills add https://github.com/nichobbs/lyric-lang --skill ask-nichobbs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It eliminates the tedium and risk of manually assembling provider-specific CLI commands by routing your prompt through OMC’s canonical advisor workflow and saving the output as a durable artifact.

Core Features & Use Cases

  • Correct provider routing: Sends questions to Claude, Codex, or Gemini via the required omc ask wrapper rather than direct provider CLIs.
  • Provider-version compatibility: Uses the wrapper to select the proper flags and invocation format automatically.
  • Persistent ask artifacts: Stores each response as an ask artifact under .omc/artifacts/ask/ for later review and traceability (e.g., security review of a patch).

Quick Start

Ask for a security review by running: /oh-my-claudecode:ask codex "review this patch from a security perspective"

Frequently Asked Questions about ask

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I route prompts to local LLM advisors like Claude, Codex, or Gemini?

You can route prompts to local LLM advisors by using the omc ask wrapper, which automatically directs your prompt to the correct provider and handles invocation compatibility. It ensures prompts are sent safely without executing provider CLIs directly.

How do I save LLM code review responses for later traceability?

To save LLM code review responses for traceability, the prompt routing process automatically persists each output as an ask artifact. Files are stored as markdown under the .omc/artifacts/ask/ directory using a provider-slug-timestamp naming convention.

Do I need to run provider CLIs directly to use Claude, Codex, or Gemini for task planning?

No, you must never run provider CLIs directly for task planning. You should exclusively invoke the omc ask wrapper to ensure correct prompt routing, provider-version compatibility, and proper artifact capture for reproducible workflows.

What is the best way to manage provider-specific CLI flags for local LLM workflows?

The best way to manage provider-specific CLI flags is to use the omc ask wrapper. It automatically selects the proper flags and invocation format for Claude, Codex, or Gemini, eliminating the tedium and risk of manual command assembly.

Can I use omc ask to generate a security review of a code patch?

Yes, you can generate a security review by running a command like omc ask codex with your review prompt. The response is routed safely to the Codex provider and saved as a durable markdown artifact for later review.