llm-cli

Automate multi-provider LLM usage via the llm CLI with file and stdin inputs.

3|Updated Feb 6, 2026
One-click install
npx skills add https://github.com/pinion05/skills --skill llm-cli
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: llm-cli
Source: https://github.com/pinion05/skills/tree/main/llm-cli
Command: npx skills add https://github.com/pinion05/skills --skill llm-cli

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill unifies access to multiple LLM providers via the llm CLI, enabling seamless model selection, input handling, and execution across providers.

Core Features & Use Cases

  • Non-interactive processing: Run prompts on files or stdin and receive direct results.
  • Interactive mode: Engage in a conversational session with a chosen model.
  • Provider detection & setup: Auto-detects available providers and guides first-time setup.
  • Input handling: Accepts text prompts, files (text and common media types), and piped input.
  • Persistent configuration: Remembers last-used model/provider for streamlined workflows.
  • Slash command integration: Supports Claude Code skill invocation and /llm command bridging.

Quick Start

Install the llm CLI, run /llm --setup to detect providers, then run a sample prompt such as /llm "Summarize this document" or llm -m gpt-4o "Your query".

Frequently Asked Questions about llm-cli

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

FAQPage Schema
How do I unify CLI access across multiple LLM providers?

Unified LLM access is achieved by automating model selection and input handling through the llm CLI, bridging non-interactive and interactive workflows across major providers.

Can I process files and stdin with multi-provider LLM models?

Multi-provider LLM models process files and stdin by accepting text prompts, piped input, and 25+ file types, returning direct results for non-interactive queries.

How do I set up the llm CLI for provider detection?

Provider detection setup requires running the /llm --setup command, which auto-detects available providers and guides first-time configuration for the LLM CLI.

What's the best way to manage LLM provider selection in automated scripts?

Automated scripts manage LLM provider selection by using persistent configuration that remembers the last-used model, streamlining non-interactive workflows without manual prompts.

Does the multi-provider LLM CLI support interactive conversational sessions?

Interactive conversational sessions are supported by the multi-provider LLM CLI, allowing users to engage directly with a chosen model after smart provider detection.

How do I invoke multi-provider LLM commands via slash commands?

Multi-provider LLM commands are invoked via slash command integration, supporting Claude Code skill invocation and /llm command bridging to execute prompts on files or stdin.