ask

Route prompts to Claude, Codex, or Gemini via the omc wrapper and persist results as artifacts.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Route prompts to Claude, Codex, or Gemini via omc ask and persist the result as artifacts, enabling deterministic advisor routing without manual CLI assembly.

Core Features & Use Cases

  • Automatic routing through the omc ask wrapper to ensure correct provider invocation and flag handling.
  • Artifact generation and persistence to the standardized .omc/artifacts/ask directory for auditability.
  • Safe, standardized workflow that prevents direct raw provider CLI usage and ensures provider-version compatibility.

Quick Start

Invoke the command /oh-my-claudecode:ask codex "review this patch" to route the prompt via omc and persist the answer as 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 without manual CLI assembly?

You can route prompts to Claude, Codex, or Gemini by invoking the omc ask wrapper, which manages provider invocation and flag handling automatically. This ensures correct provider-version compatibility without requiring raw CLI construction.

How do I persist AI prompt responses as artifacts for auditability?

AI prompt responses are persisted as artifacts automatically by the omc ask wrapper, which saves outputs to the standardized .omc/artifacts/ask directory. This guarantees artifact-based traceability for development and automation tasks.

What is the best way to automate code reviews across different AI providers?

Automating code reviews across AI providers is best done through prompt routing workflows that direct queries to Claude, Codex, or Gemini via the omc wrapper. This standardizes the process while persisting review results as artifacts.

Does the omc ask wrapper support task planning and design discussions?

Yes, the omc ask wrapper supports task planning and design discussions by applying prompt routing workflows across development and automation tasks. It routes prompts to the appropriate provider and saves results as artifacts.

Why should I avoid direct raw provider CLI usage when routing prompts?

Avoiding direct raw provider CLI usage is enforced to ensure safe, standardized workflows and provider-version compatibility. The omc wrapper handles correct provider invocation and guarantees artifact generation for traceability.