LLMLB Assistant CLI FAQs

Question 1

What is the primary purpose of this skill?

Accepted Answer

It provides a secure and efficient way to interact with the LLMLB distributed router for managing, inspecting, and testing LLM API endpoints directly from Claude Code.

Question 2

What environment variables are required?

Accepted Answer

The skill utilizes LLMLB_URL, LLMLB_API_KEY for standard requests, LLMLB_ADMIN_API_KEY for admin tasks, and LLMLB_JWT_TOKEN as a fallback for auth endpoints.

Question 3

How does this skill handle security for API requests?

Accepted Answer

The skill validates cURL commands for shell-injection patterns, blocks requests to non-allowed hosts, and uses environment variables for secure authentication management.

Question 4

Does this skill replace the LLMLB MCP server?

Accepted Answer

Yes, this skill implements the modern 'llmlb assistant' CLI flow, which is the preferred and more flexible method for interacting with LLMLB infrastructure.

Question 5

Can I use custom authentication headers?

Accepted Answer

Yes, while the skill defaults to automatic authentication using environment variables, you can use the --no-auto-auth flag to send custom authentication headers when necessary.

LLMLB Assistant CLI

Key Features

Use Cases

LLMLB Assistant CLI

Key Features

Use Cases