LLM Engineering
Use when a product feature runs on an LLM and must stay usable when the model refuses, returns malformed or invalid JSON, or times out. Also use when users are seeing a raw provider error, a feature dead-ends on a refusal, or a retry loop is making things worse instead of better. If a model failure can reach the user, use this skill.
1 file
Description
Use when a product feature runs on an LLM and must stay usable when the model refuses, returns malformed or invalid JSON, or times out. Also use when users are seeing a raw provider error, a feature dead-ends on a refusal, or a retry loop is making things worse instead of better. If a model failure can reach the user, use this skill.
Any user-facing feature where an LLM call can fail: the model declines the request, returns text where you expected structured output, hits a rate limit, or exceeds a latency budget.
The user should never see a raw model refusal or a JSON parse error. Map every failure mode to a calm, specific message and, where possible, a next action.
catch that returns empty output hides real breakage. Log the failure mode with enough context to see which prompts fail.Added 2026-07-01. Back to the Skill Library.

New tutorials, open-source projects, and deep dives on coding agents - delivered weekly.