mj-agent-infra-llm-endpoint-probe

Probes OpenAI-compatible local LLM endpoints for reachability, model match, and chat smoke.

1|Updated Mar 4, 2026
One-click install
npx skills add https://github.com/MJ-AgentLab/mj-agent --skill mj-agent-infra-llm-endpoint-probe-mj-agentlab
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: mj-agent-infra-llm-endpoint-probe
Source: https://github.com/MJ-AgentLab/mj-agent/tree/main/.claude/skills/mj-agent-infra-llm-endpoint-probe
Command: npx skills add https://github.com/MJ-AgentLab/mj-agent --skill mj-agent-infra-llm-endpoint-probe-mj-agentlab

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When switching mj-agent from the Ark cloud provider to a local OpenAI-compatible LLM endpoint on DGX-Spark (vLLM, SGLang, Ollama, TGI, or llama.cpp), misconfigured base URLs, mismatched model IDs, or unreachable hosts cause opaque runtime failures. This Skill verifies the endpoint before the agent runtime depends on it. ## Core Features & Use Cases - Three-step health probe: checks LLM_BASE_URL presence, queries /v1/models (with automatic Ollama /api/tags fallback), and runs a 1-token chat completion smoke test. - Model ID validation: compares the endpoint's loaded model list against LLM_MODEL_ID in .env and reports mismatches with corrective actions. - Actionable troubleshooting: maps failure modes (connection refused, 404, 401, 422, 500) to concrete fixes such as port checks, base URL path corrections, and API key alignment. - Use Case: After switching LLM_PROVIDER to local-openai-compat, run the probe to confirm the DGX vLLM endpoint at 192.168.0.189:8000 is reachable, serves the expected model, and answers a minimal chat request before launching LangGraph Studio. ## Quick Start Ask the agent to run a DGX endpoint healthcheck to verify the local LLM endpoint is reachable and serving the configured model.

Frequently Asked Questions about mj-agent-infra-llm-endpoint-probe

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

FAQPage Schema
How do I healthcheck a vLLM OpenAI-compatible endpoint?▼

Query GET /v1/models on the endpoint's base URL to confirm it returns a JSON list of loaded models, then send a minimal chat completion with max_tokens set to 1. A 200 response with valid choices confirms the endpoint is healthy.

How to verify a local LLM endpoint before switching LLM providers?▼

Run a three-step probe: confirm the base URL environment variable is set, check that /v1/models returns the expected model ID, and execute a 1-token chat smoke test. This catches reachability, model mismatch, and schema issues before runtime.

Does Ollama support the OpenAI /v1/models endpoint?▼

Ollama exposes an OpenAI-compatible mode but may not respond on /v1/models in all configurations. The probe detects Ollama by the :11434 port and falls back to querying /api/tags, which returns the loaded model list.

Why does my local LLM endpoint return 404 on /v1/models?▼

A 404 usually means the base URL path is wrong. The URL should end in /v1 (for example http://host:8000/v1), not /v1/ or a bare host. Verify the serving framework actually exposes the OpenAI-compatible route.

When should I not use an endpoint probe for LLM health?▼

Do not probe cloud providers like Volcengine Ark that have no /v1/models contract; API key validation through the standard client is sufficient. The probe is also not a substitute for graph-level behavior tests or database connectivity checks.