cli-providers

Standardize provider-specific CLI capability handling across Claude and Gemini.

11|2|Updated Feb 5, 2026
One-click install
npx skills add https://github.com/recca0120/code-quest --skill cli-providers
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cli-providers
Source: https://github.com/recca0120/code-quest/tree/main/.claude/skills/cli-providers
Command: npx skills add https://github.com/recca0120/code-quest --skill cli-providers

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the challenge of provider-specific inconsistencies when integrating multiple AI CLIs that do not share the same flags, output formats, stream events, or permission/elicitation behavior.

Core Features & Use Cases

  • Capability matrix guidance: Helps you determine which CLI features are safe to assume versus which must be conditionally enabled per provider.
  • Provider-specific integration workflow: Supports updating logic when you discover new flag support, output differences, stream event types, or limitations.
  • Integration and troubleshooting use cases: Useful when spawning processes, constructing CLI arguments, parsing NDJSON/stream output, and implementing new ProviderAdapter support across Claude, Gemini, and others.

Quick Start

Use the cli-providers skill when you implement or troubleshoot provider-specific CLI spawning, argument building, or output parsing so you can consult the capability matrix and update it after each new discovery.

Frequently Asked Questions about cli-providers

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

FAQPage Schema
How do I handle different CLI flags and output formats when integrating multiple AI providers?

To handle different CLI flags and output formats across multiple AI providers, maintain a capability matrix to track feature support and implement ProviderAdapter logic to drive provider-conditional behavior for spawning and parsing.

What is a capability matrix for AI CLI multi-provider support?

A capability matrix for multi-provider AI CLI support is a reference tracking which CLI features are safe to assume versus which must be conditionally enabled per provider, ensuring you select compatible flags and handle stream events correctly.

How do I parse NDJSON stream events from different AI CLIs?

To parse NDJSON stream events from different AI CLIs, implement provider-specific parsing logic within a ProviderAdapter, consulting your capability matrix to account for variations in stream event types and output formats.

Does this approach work for adding support for new AI CLIs like Claude and Gemini?

Yes, this approach works for adding support for new AI CLIs like Claude and Gemini by providing an integration workflow where you update logic and the capability matrix upon discovering new flag support, output differences, or limitations.

Why does my CLI argument building fail when switching between AI providers?

CLI argument building fails when switching between AI providers because providers do not share the same flags, permission behavior, or elicitation behavior, requiring you to consult a capability matrix and conditionally select compatible arguments.