ask

Route prompts to local Claude, Codex, or Gemini CLIs and store artifacts.

1|1|Updated Apr 13, 2026
One-click install
npx skills add https://github.com/Cheggin/request-for-startups --skill ask-cheggin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ask
Source: https://github.com/Cheggin/request-for-startups/tree/main/skills/ask
Command: npx skills add https://github.com/Cheggin/request-for-startups --skill ask-cheggin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Route prompts to the local Claude, Codex, or Gemini CLIs via omc ask and persist the result as an ask artifact for traceability and audits.

Core Features & Use Cases

  • Route prompts to multiple provider CLIs (Claude, Codex, Gemini) using a single, safe wrapper to ensure consistent behavior.
  • Persist artifacts for each interaction in a standardized location, enabling auditing, reproducibility, and knowledge capture.
  • Use cases include security reviews, product inquiries, and research tasks where an advisor's guidance must be captured and referenced later.

Quick Start

Invoke omc ask with a provider and a task to route the prompt and create an 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 Claude, Codex, or Gemini from a single command line interface?

Route prompts to local Claude, Codex, or Gemini CLIs by invoking omc ask with a provider and task. This wrapper ensures consistent behavior and returns a validated answer across development and research tasks.

Can I persist Claude or Gemini CLI interactions for later security audits?

Yes, you can persist CLI interactions for audits. The wrapper stores each interaction as an artifact under .omc/artifacts/ask with timestamped metadata and provider information, enabling reproducibility and knowledge capture.

What is the best way to manage prompts across multiple AI provider CLIs?

Manage prompts across multiple AI provider CLIs using a single safe wrapper. It routes inquiries to Claude, Codex, or Gemini as needed and standardizes artifact storage for every interaction, ensuring consistent results.

Does this prompt routing method work for both development tasks and research inquiries?

Yes, this prompt routing method works for development tasks and research inquiries. You can apply it across security reviews, product inquiries, and general research, routing different providers as needed for each specific task.

How do I start routing a prompt to a specific provider using omc ask?

To start routing a prompt, invoke omc ask with your chosen provider and the task description. The wrapper handles prompt delivery to the local CLI and automatically creates a timestamped artifact capturing the result.

Why should I use a wrapper to route prompts instead of calling provider CLIs directly?

Use a wrapper to route prompts to ensure consistent behavior and safe execution across providers. It automatically captures each interaction as a timestamped artifact, providing traceability and reproducibility that direct CLI calls lack.