gem-llm-cli-client

Chat, manage sessions, and debug gem endpoint usage via REPL and slash commands.

Updated Apr 4, 2026
One-click install
npx skills add https://github.com/saintgo7/claude-skills --skill gem-llm-cli-client
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gem-llm-cli-client
Source: https://github.com/saintgo7/claude-skills/tree/main/gem-llm-cli-client
Command: npx skills add https://github.com/saintgo7/claude-skills --skill gem-llm-cli-client

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

gem-llm-cli-client helps you use the gem-cli terminal client reliably for interactive chat and slash commands, while providing clear debugging and troubleshooting when authentication, connectivity, or tool-calling behavior goes wrong.

Core Features & Use Cases

  • Terminal-based gem-cli workflow: Supports REPL usage and slash commands for quick model switching, cost tracking, history inspection, login refresh, and conversation control.
  • Tool-calling safety guardrails: Implements blocked dangerous bash patterns even when auto-approval is enabled, returning a refusal for high-risk commands.
  • Non-interactive and scripting support: Enables single-shot calls via REPL piping or direct HTTP calls for automation, testing, and embedding-friendly runs.
  • Operational troubleshooting: Covers common failure modes like missing API keys, invalid keys, gateway connection issues, rate limits, token quota limits, and tool-call loop hard caps.

Quick Start

Ask for help by running the terminal client and logging in: execute gem login on your machine to save your config, then start the REPL with gem to chat with a chosen model.

Frequently Asked Questions about gem-llm-cli-client

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

FAQPage Schema
How do I set up a terminal client for LLM chat and debugging with tool calling?

To use a terminal client for LLM chat and debugging, run the login command to save your API key configuration, then start the REPL to interactively chat, switch models, and inspect tool calling behavior.

What safety filters prevent dangerous bash patterns during automated tool calling?

Safety filters detect and refuse dangerous bash patterns during tool calling by returning a high-risk command refusal, ensuring that automated non-interactive calls and auto-approval cannot execute harmful shell commands.

Why does my terminal client fail to connect to the gateway during non-interactive calls?

Gateway connection issues during non-interactive calls typically stem from missing or invalid API keys, hitting rate limits, or exceeding token quota limits, all of which require checking your login configuration and endpoint validity.

Can I use REPL and slash commands to track cost and inspect conversation history?

Yes, you can use slash commands within the REPL to quickly switch models, track token costs, inspect conversation history, and manage session control while interacting with the endpoint.

How do I troubleshoot tool-call loops when debugging endpoint connectivity?

To troubleshoot tool-call loops, check if you are hitting the hard cap on tool-call loops, verify your endpoint connectivity, and ensure your API key configuration is valid to prevent automated call failures.