ask

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

1|Updated Apr 6, 2026
One-click install
npx skills add https://github.com/Hyeonjun0527/yeon --skill ask-hyeonjun0527
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ask
Source: https://github.com/Hyeonjun0527/yeon/tree/main/.codex/skills/ask
Command: npx skills add https://github.com/Hyeonjun0527/yeon --skill ask-hyeonjun0527

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Route prompts to Claude, Codex, or Gemini locally and persist the result as an artifact.

Core Features & Use Cases

  • Prompt routing: Route prompts to the local AI providers via the omc ask wrapper and avoid manual CLI invocations.
  • Artifact persistence: Automatically save the provider response as an ask artifact under the project's artifact directory.
  • Use Case: Engineers and assistants can orchestrate multi-provider prompts and retain traceable outputs for auditing.

Quick Start

Route a user prompt to the selected provider using omc ask and store the resulting artifact.

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 different AI providers and save the response as an artifact?

Route prompts to AI providers using the omc ask wrapper, which invokes Claude, Codex, or Gemini locally and automatically persists the resulting answer as an artifact under the project's artifact directory.

What is the best way to avoid manual CLI invocations when switching between Claude and Gemini?

Use prompt routing via the omc ask wrapper to manage provider invocation and compatibility handling, avoiding manual raw CLI assembly when switching between local AI providers.

Can I retain traceable AI outputs for auditing when building interactive assistants?

Yes, artifact persistence automatically saves provider responses as ask artifacts, retaining traceable outputs with provider provenance for auditing interactive assistant builds.

Does prompt routing support code review helpers that require provider provenance?

Prompt routing supports code review helpers by invoking local AI providers and persisting resulting answers as artifacts, ensuring provider provenance and auditable artifact logs.

Why should I not manually assemble raw CLI commands for multi-provider prompts?

Manual raw CLI assembly bypasses compatibility handling and safe usage enforcement; the omc ask wrapper manages provider invocation and artifact creation safely instead.

Do I need any dependencies to orchestrate multi-provider prompts locally?

No external dependencies are required; the Skill relies on the omc ask wrapper to manage local provider invocation, artifact creation, and compatibility handling independently.