Fix Invalid JSON from AI
The JSON won't parse and you can't see why. Deterministic cause-sniffing — trailing commas, single quotes, unclosed brackets — and the repair prompt that fixes it.
Judge the whole conversation, not one reply — evaluate a multi-turn exchange for context retention, coherence, goal completion, and recovery from misunderstanding.
A chat agent can give good individual replies and still fail the conversation — losing context across turns, contradicting itself, or never actually resolving the user's goal. This prompt evaluates the multi-turn exchange as a whole: does it hold context, stay coherent turn to turn, recover when it misunderstands, and reach the user's goal — the qualities single-reply scoring can't see.
Assemble the full conversation
Gather a complete multi-turn exchange, not a single reply, along with the user goal. The eval judges the conversation as a whole.
Open this resource in AI Output Validator
Load the prompt into AI Output Validator and paste in the transcript. The tool scores context retention, coherence, recovery, and goal completion without you reading turn by turn.
Review the per-dimension scores
Read how the conversation held context, stayed coherent, recovered from misunderstanding, and reached the goal, noting where it slipped.
Feed the weak turns back
Use the low-scoring dimensions to adjust the agent prompt or memory handling, then re-evaluate a fresh conversation.
Feed the full transcript plus the GOAL line, and the prompt scores six dimensions 0-5 each, including CONTEXT RETENTION and GOAL COMPLETION, then names the single turn where it most went wrong. AI Output Validator produces the scored analysis; you run its judgment in your own assistant and decide what the numbers mean for the agent.
Yes. A RULE states that reaching a goal in ten turns it could do in three is a partial failure, and the GOAL COMPLETION dimension weighs turns to resolution. The AGGREGATE section also records whether the user left with their goal met as yes, partially, or no, so inefficiency shows even when the answer eventually lands.
A RULE tells the evaluator to judge the trajectory, not isolated replies, so a polished reply that ignores earlier turns still fails the CONTEXT RETENTION dimension. Single-turn scoring needs a per-reply scorecard instead; this contract only makes sense against a full multi-turn transcript paired with a stated user goal.
The JSON won't parse and you can't see why. Deterministic cause-sniffing — trailing commas, single quotes, unclosed brackets — and the repair prompt that fixes it.
Paste the response, get the verdict: real JSON parsing, missing-field detection, and a repair prompt for everything found.
Grade agent output the same way every time — a rubric scoring correctness, grounding, safety, tone, and completeness, with a pass threshold instead of a gut call.
Stop getting 'Sure, here is the JSON…' — the output-contract pattern that forces models to return only parseable JSON: schema, example, and a strict rule block.
Free text in, named fields out. The extraction prompt pattern that turns any unstructured text into consistent, parseable records.
Billing, Technical, Account, How-To, Feature Request — ticket triage with definitions that decide the borderline cases for the model.
Paste an AI's output and validate it against the expected format — with a repair prompt for every failure found.
The full path to a support operation, not just a bot — stand up the knowledge base, route the tickets, add the AI agent, integrate your stack, close the feedback loop, evaluate, and deploy.
Build an evaluation scorecard two people can apply to the same agent run and reach the same number — dimensions that don't measure each other, anchors you can point at, and the failures that shouldn't average out.