LM Studio E2E Audit

Audit LM Studio runtime workflows by validating server startup and tool-call traces.

Updated Mar 13, 2026

Search Tags:#runtime-validation #server-startup #lm-studio #e2e-audit #tool-trace #prompt-bootstrap

Ready to run

npx skills add https://github.com/JDL440/nfl-eval --skill lm-studio-e2e-audit

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: LM Studio E2E Audit
Source: https://github.com/JDL440/nfl-eval/tree/main/.squad/skills/lmstudio-e2e-audit
Command: npx skills add https://github.com/JDL440/nfl-eval --skill lm-studio-e2e-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Audits the LM Studio end-to-end runtime workflow by validating the real server startup path, provider registration, and prompt bootstrap, ensuring the runtime behaves as expected rather than relying on isolated unit tests.

Core Features & Use Cases

End-to-end server startup validation: confirms LM Studio provider is registered and the runtime prompt refresh occurs at startup.
Tool-call trace analysis: reads stage_runs and llm_traces to summarize tool calls by name and outcome.
Failure diagnosis: highlights where startup or prompt bootstrap failures occur and what to inspect in logs.
Use Case: verify a new LM Studio integration after provider/path changes by running the real server workflow and extracting success/failure signals.

Quick Start

Run the end-to-end audit on a live v2 server to validate LM Studio startup, prompt bootstrap, and tool-call traces.

Frequently Asked Questions about LM Studio E2E Audit

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

FAQPage Schema

How do I validate LM Studio server startup and provider registration end-to-end?▼

Validate LM Studio server startup by running an end-to-end audit on a live v2 server, which confirms provider registration, verifies prompt bootstrap, and extracts success or failure signals from actual server runs.

What is an LM Studio end-to-end runtime audit?▼

An LM Studio end-to-end runtime audit validates real server startup paths, provider registration, and prompt bootstrap by inspecting stage_runs and llm_traces, ensuring the runtime behaves as expected rather than relying on isolated unit tests.

How do I diagnose LM Studio prompt bootstrap or startup failures?▼

Diagnose LM Studio prompt bootstrap failures by inspecting stage_runs and llm_traces during an end-to-end audit; the process highlights where startup or prompt bootstrap failures occur and identifies what to inspect in logs.

Do I need a live server to run an LM Studio e2e audit?▼

Yes, you need access to a live v2 server run because the end-to-end audit validates real server startup paths, provider registration, and prompt bootstrap by inspecting actual stage_runs and llm_traces.

When should I run an LM Studio tool-call trace analysis?▼

Run an LM Studio tool-call trace analysis when provider paths, stage actions, or runtime prompts change, or when you need proof of tool-call sequences and success or failure outcomes from actual server runs.

Can I verify a new LM Studio integration without isolated unit tests?▼

Yes, you can verify a new LM Studio integration after provider or path changes by running the real server workflow end-to-end and extracting success and failure signals from tool-call traces instead of relying on unit tests.