exploring-ai-failures

Diagnose production AI failures by reading LLM traces into ranked failure modes.

713|118|Updated Aug 11, 2020
One-click install
npx skills add https://github.com/PostHog/posthog-foss --skill exploring-ai-failures
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: exploring-ai-failures
Source: https://github.com/PostHog/posthog-foss/tree/main/products/ai_observability/skills/exploring-ai-failures
Command: npx skills add https://github.com/PostHog/posthog-foss --skill exploring-ai-failures

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

AI applications fail silently in production: the model returns HTTP 200 with a response that is wrong, off-topic, ignores instructions, or misuses tools, and these failures never raise an error. This Skill finds both loud and silent failures in PostHog LLM trace data and groups them into a ranked, actionable failure taxonomy.

Core Features & Use Cases

  • Failure Trace Discovery: Select candidate traces using code errors, metric outliers (tokens, latency, cost), trace-type slices, stratified sampling, existing-eval spikes, or clustering.
  • Trace Reading and Coding: Read 20-30 traces per use case with query-llm-trace, note what went wrong, and group notes into named failure modes.
  • Ranked Failure Taxonomy: Deliver a ranked list of failure modes with deep-linked example traces, ready to turn into fixes or online evaluations.
  • Use Case: A team notices their support chatbot gives bad answers. Use this Skill to scope to the support trace slice, read a batch of traces, and come back with ranked modes like "ignores the date filter" or "invents a policy", each with linked example traces.

Quick Start

Ask the assistant to find and categorize the failure modes in your AI feature's production traces from the last 7 days.

Frequently Asked Questions about exploring-ai-failures

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

FAQPage Schema
How do I find failure modes in my LLM application?

Scope to one use case, select candidate traces using error flags, metric outliers, or a stratified sample, then read 20-30 traces and group what went wrong into named failure modes. Rank the modes by frequency and attach example trace links.

How to detect silent failures in AI agents that return HTTP 200?

Silent failures cannot be found with GROUP BY queries or keyword greps because the patterns are unknown in advance. You must open and read traces directly, using metric outliers or stratified sampling to pick which ones to inspect.

What signals can I use to select LLM traces to review?

Available signals include $ai_is_error code errors, outliers in input/output tokens, latency, and cost, single trace-type slices, stratified random samples, spikes in existing evaluation failures, and clustering at high volume.

Why is counting $ai_is_error events not enough for failure analysis?

The $ai_is_error flag only catches exceptions and API failures, which are the loud minority. Most impactful AI failures complete successfully with wrong or off-topic content and only appear when a human reads the trace.

What should I do when there are too few traces to analyze?

Widen the time window or loosen the slice filters first. Then stress-test with edge-case or adversarial inputs, or generate a small synthetic set across request types and read those traces as a bootstrap, not ground truth.