ask

Route prompts through local Claude, Codex, or Gemini CLI workflows and persist results as ask artifacts.

Updated Apr 17, 2026
One-click install
npx skills add https://github.com/dropsyoon/oh-my-claudecode --skill ask-dropsyoon
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ask
Source: https://github.com/dropsyoon/oh-my-claudecode/tree/main/skills/ask
Command: npx skills add https://github.com/dropsyoon/oh-my-claudecode --skill ask-dropsyoon

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the friction of choosing the right Claude, Codex, or Gemini CLI invocation and reliably capturing the result for later use, so you can focus on the question or task rather than command assembly.

Core Features & Use Cases

  • Provider-aware prompt routing: Sends your prompt through the correct local provider path using the OMC advisor skill interface.
  • Artifact persistence: Saves the completed result as an ask artifact so you can review, reference, or chain follow-up work.
  • No raw CLI assembly: Prevents outdated or incorrect provider flag construction by requiring the canonical omc ask wrapper.

Quick Start

Ask a provider-specific question by running: /oh-my-claudecode:ask claude "draft an implementation plan for issue #123".

Frequently Asked Questions about ask

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

FAQPage Schema
How do I route a single prompt to a specific local CLI like Claude or Gemini?

Prompt routing to local Claude, Codex, or Gemini CLIs is handled by sending your request through the omc ask wrapper, which automatically selects the correct provider workflow. This ensures the prompt reaches the right CLI without manual command assembly.

What is the best way to save CLI prompt results for later reference?

Saving CLI prompt results is achieved by persisting the outcome as an ask artifact. The system writes the completed response to .omc/artifacts/ask/ as a markdown file, creating a traceable record for later review or follow-up work.

Can I execute advisory-style Q&A tasks and keep a traceable artifact?

Advisory-style Q&A and task execution for single-prompt workflows are supported, generating traceable results automatically. The process targets these specific use cases and enforces artifact persistence so you can reference the output later.

Do I need to manually construct provider CLI flags for Codex or Claude?

Manual provider CLI construction is explicitly prevented to avoid outdated or incorrect flag usage. You must use the canonical omc ask wrapper instead, which handles the provider-aware routing and command assembly internally.

How does artifact persistence work for single-prompt workflows?

Artifact persistence for single-prompt workflows works by writing the provider result to a timestamped markdown file. The saved artifact is named using the provider, slug, and timestamp, stored under .omc/artifacts/ask/.

Why does my provider CLI invocation keep failing with outdated flags?

Provider CLI invocations fail when flags are constructed manually, which leads to outdated or incorrect command syntax. Using the omc ask wrapper eliminates this friction by enforcing the correct canonical command structure.