message-flow-troubleshooter

Detect and isolate message flow failures across client, proxy, and LLM provider.

1|Updated Apr 11, 2026
One-click install
npx skills add https://github.com/drgon1/santian --skill message-flow-troubleshooter
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: message-flow-troubleshooter
Source: https://github.com/drgon1/santian/tree/main/ai-skills/skills/message-flow-troubleshooter
Command: npx skills add https://github.com/drgon1/santian --skill message-flow-troubleshooter

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps diagnose broken or inconsistent message delivery across a client, an intermediate routing layer, and an LLM provider, especially when replies disappear, become malformed, or stop at the proxy.

Core Features & Use Cases

  • Two-sided inspection: Compare the client’s original request with the provider’s raw response to determine whether the failure starts on the left side, the right side, or in the middle.
  • Restart-first triage: When the middle layer is down or blocking traffic, restart immediately before spending time on deeper analysis.
  • Code-level fallback: If a restart does not fix the issue, switch to targeted logic debugging instead of repeated full-chain guessing.
  • Use cases: Cursor receiving empty output, tool-call loops, truncated messages, proxy crashes, and message transformation bugs.

Quick Start

Ask the assistant to inspect the client request, the provider’s raw response, and the middle-layer logs, then decide whether to restart the proxy or trace the transformation bug.

Frequently Asked Questions about message-flow-troubleshooter

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

FAQPage Schema
How do I troubleshoot empty replies or truncated messages from an LLM proxy?

Perform a bidirectional payload comparison between the client request and the provider's raw response to isolate whether empty replies or truncated messages originate from the left side, right side, or the middle proxy layer.

Why does my middleware routing layer stop delivering traffic to the LLM provider?

Your middleware routing layer might stop delivering traffic due to middle-layer outages or crashes. You should apply a restart-first triage strategy, immediately restarting the proxy before spending time on deeper code analysis or full-chain guessing.

How do I debug malformed tool calls and message transformation bugs in a chat pipeline?

To debug malformed tool calls and message transformation bugs in a chat pipeline, inspect the middle-layer logs and switch to targeted code-level logic debugging if a proxy restart fails to restore normal message delivery.

What is the best way to diagnose a Cursor client receiving empty output from a proxy?

The best way to diagnose a Cursor client receiving empty output from a proxy is to inspect the client's request alongside the provider's raw response, which determines whether the delivery failure is client-side or caused by the intermediate routing layer.

What should I do when restarting the proxy does not fix the LLM message flow failure?

When restarting the proxy does not fix the LLM message flow failure, switch from restart-first triage to targeted code-level logic debugging to trace specific message transformation bugs instead of repeated full-chain guessing.