Crash Inbox — turn this week's error-telemetry export into a fix order

Paste the error export from your telemetry dashboard — messages, stack traces, hit counts, user counts — as CSV, TSV, JSON or raw stack traces. The page reads it in your browser: it merges the rows that are really one bug, classifies every frame as yours, a dependency, a browser extension or the runtime, detects unsymbolicated bundles, and separates the errors you could not act on even if you wanted to. Then four lanes: triage the whole export into a fix order, trace one error's data flow from the producer of the bad value to the consumer that crashed, rewrite its message so the next occurrence is diagnosable from telemetry alone, and find where it is being swallowed, retried or rethrown blind. Every check answers pass, fail or unknown, and never confuses the last two. Built on the agent skill @microsoft/fix-errors; a derived work, not affiliated with or endorsed by Microsoft.

Every public app is built from a security-scanned skill and must pass a clean scan — skill and frontend — before it can be listed. Have a skill of your own? Turn it into an app — or read the step-by-step walkthrough.