What problem does it solve? Running Claude Code against a self-hosted vLLM model requires a local shim, per-machine configuration, and careful verification — misconfigured setups fail with cryptic 400 errors, truncated prompts, or silent context clamping. This Skill installs the claude-local launcher, proves it works with a live print-mode run, and reads the shim log before declaring anything a defect. ## Core Features & Use Cases - Guided installation: Detects existing installs, runs the installer from a clone or the skeleton's raw URL, and supports multiple named endpoints (vLLM, Ollama) with a configurable default. - Live verification: Exercises the full chain (launcher → shim → server → tool call) via print mode, then inspects the shim log as the source of truth for what was sent. - Troubleshooting playbook: Covers unreachable endpoints, Ollama context truncation, 400 role errors, oversized prompts from MCP tool schemas, and output-token cap conflicts. - Use Case: A developer gets a new vLLM box serving a Qwen model and wants Claude Code to run against it without losing Anthropic access on plain claude — this Skill installs the scoped launcher and confirms a tool-call round trip. ## Quick Start Ask the assistant to set up claude-local against your vLLM server at its base URL and verify it with a live print-mode run.