exploring-ai-failures
Skill96 starsChanged 37 days agoNo licenceView on GitHub
Find where an AI/LLM application is failing in production and surface the failure patterns, working from real traces. Use when someone wants to understand what's going wrong with an AI feature, find and categorize failure modes, triage errors, or investigate quality issues (wrong answers, ignored instructions, hallucinations, tool misuse) — "what's failing in my agent", "surface error patterns", "why are the responses bad", "find the common failure modes", "what should I fix next". Covers scoping to one use case, finding failing traces by whichever signal fits the context (code errors, metric outliers, trace-type slices, manual review, existing-eval spikes, clustering), and reading them into a ranked failure taxonomy.
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 3 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Other versions1 project uses a version of this.
Word for word · 1
- PostHog/skills★ 76100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository179 other files it gives its agents.
- adding-warehouse-person-propertiesSkill
- analyzing-ai-citationsSkill
- analyzing-expensive-usersSkill
- analyzing-experiment-session-replaysSkill
- analyzing-funnel-correlationSkill
- analyzing-offline-evaluationsSkill
- analyzing-task-runsSkill
- assessing-heatmapsSkill
- auditing-endpointsSkill
- auditing-experiments-flagsSkill
- auditing-warehouse-source-healthSkill
- auditing-warehouse-view-healthSkill
- authoring-data-quality-checksSkill
- authoring-error-tracking-alertsSkill
- authoring-log-alertsSkill
- authoring-scoutsSkill
- building-a-dashboardSkill
- building-canvasesSkill
- building-html-canvasesSkill
- building-loopsSkill
- building-react-quill-canvasesSkill
- building-workflowsSkill
- checking-deploy-timingSkill
- checking-member-accessSkill
- choosing-trend-or-slope-viewSkill
- cleaning-up-stale-feature-flagsSkill
- composing-grid-canvasesSkill
- configuring-experiment-analyticsSkill
- configuring-experiment-rolloutSkill
- consuming-endpoints-from-client-codeSkill
- context-layer-consolidationSkill
- context-layer-dreamingSkill
- context-layer-health-checkSkill
- copying-endpoints-across-projectsSkill
- copying-flags-across-projectsSkill
- creating-ai-subscriptionSkill
- creating-an-endpointSkill
- creating-box-plot-insightsSkill
- creating-experimentsSkill
- creating-online-evaluationsSkill
- creating-replay-vision-scannersSkill
- creating-surveysSkill
- debugging-experimentsSkill
- debugging-failed-data-quality-checksSkill
- debugging-surveysSkill
- designing-email-templatesSkill
- designing-replay-vision-scannersSkill
- diagnosing-ci-and-merge-bottlenecksSkill
- diagnosing-endpoint-performanceSkill
- diagnosing-experiment-healthSkill
- diagnosing-failed-warehouse-syncsSkill
- diagnosing-missing-recordingsSkill
- diagnosing-sdk-healthSkill
- diagnosing-stacktrace-symbolicationSkill
- downloading-batch-export-filesSkill
- exploring-apm-tracesSkill
- exploring-autocapture-eventsSkill
- exploring-endpoint-execution-logsSkill
- exploring-live-trafficSkill
- exploring-llm-clustersSkill
- The first 60 shown.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.