skills.rest
INNERJOINT
INNERJOINTCOMMUNITY
Explore all skills by this author →
GitHub

ask

Route advisor prompts through local LLM CLIs and persist responses as artifacts.

Updated Mar 26, 2026
Search Tags:#codex#claude#gemini#artifact#ask#omc#prompt-routing
One-click install
npx skills add https://github.com/INNERJOINT/HarnessSkills --skill ask-innerjoint
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ask
Source: https://github.com/INNERJOINT/HarnessSkills/tree/main/skills/ask
Command: npx skills add https://github.com/INNERJOINT/HarnessSkills --skill ask-innerjoint

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Many users manually assemble provider CLI commands or run provider tools directly, which leads to incorrect flags, outdated invocations, and lost outputs; this Skill centralizes and standardizes routing so prompts are executed reliably and results are captured as artifacts.

Core Features & Use Cases

  • Provider-agnostic routing: Send a single prompt to local Claude, Codex, or Gemini CLIs via the omc ask wrapper without manually assembling provider-specific flags.
  • Artifact persistence: Automatically persist responses to a consistent artifact path for traceability and later review.
  • Use Case: Perform a security-focused code review with Codex, solicit UX improvement suggestions from Gemini, or draft an implementation plan with Claude while ensuring outputs are stored for audit or collaboration.

Quick Start

Use the ask skill to route a security review request for a patch to codex and persist the response 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 a single prompt to local Claude, Codex, or Gemini CLIs without manually assembling provider-specific flags?▼

You can route prompts to local Claude, Codex, or Gemini CLIs by using the omc ask wrapper, which standardizes invocations and ensures correct provider flags without manual assembly.

How does artifact persistence work for local LLM responses generated via command line interfaces?▼

Artifact persistence automatically saves local LLM responses to a consistent path under .omc/artifacts/ask, ensuring outputs from prompt routing are captured reliably for traceability and later review.

Do I need to install and authenticate local LLM CLIs before routing prompts for code review or implementation planning?▼

Yes, you need the corresponding local Claude, Codex, or Gemini CLIs installed and authenticated before routing prompts for code review or implementation planning through the omc ask wrapper.

What is the best way to standardize local LLM invocations and avoid incorrect flags or outdated commands?▼

The best way to standardize local LLM invocations is using the omc ask wrapper, which centralizes prompt routing to ensure provider-version compatibility and correct flags across different LLM CLIs.

Why do I lose outputs when running provider CLI tools directly for security code reviews or UX suggestions?▼

You lose outputs when running provider CLI tools directly because they lack automatic artifact persistence; using the omc ask wrapper ensures responses are captured and stored consistently under .omc/artifacts/ask.

Related Skills

Explore More Software Engineering Skills→
Moliboy5000Moliboy5000

ask

Query local Claude, Codex, or Gemini CLIs and persist outputs as reusable artifacts.

Community
Intermediate
Leap0920Leap0920
1

ask

Route prompts to local Claude, Codex, or Gemini CLIs and persist outputs as OMC ask artifacts.

Community
Intermediate
brabos-aibrabos-ai
8

add-frontend-development

Guide frontend development with stack-agnostic architecture and type safety.

Official
Advanced
RobinNorbergRobinNorberg
5

ask

Routes prompts to local AI providers and saves responses as timestamped artifacts.

Community
Intermediate