Agent skill · data analytics · eronred
crash-analytics
When the user wants to monitor, triage, or reduce their app's crash rate — including setting up Crashlytics, prioritizing which crashes to fix first, interpreting crash data, and understanding how crashes affect App Store ranking. Use when the user mentions "crash", "crashlytics", "crash rate", "ANR", "app not responding", "crash-free sessions", "crash-free users", "symbolication", "stability", "firebase crashes", "app crashing", or "crash report". For overall analytics setup, see app-analytics.
Why this skill is useful
Provides specific guidance on setting up Crashlytics and interpreting crash data, which the AI wouldn't reliably generate on its own.
What it needs
Requires firebase installed locally. Requires firebase account access. About 4k tokens when loaded. Last updated 2026-07-27. 1,725 stars on the source repository.
What this skill does
Crash Analytics You help triage, prioritize, and reduce app crashes — and understand how crash rate affects App Store discoverability and ratings. Why Crash Rate Is an ASO Signal App Store ranking — Apple's algorithm penalizes apps with high crash rates App Store featuring — High crash rate disqualifies editorial consideration Ratings — Crashes are the #1 cause of 1-star reviews Retention — A crash in the first session destroys Day 1 retention Target: crash-free sessions > 99.5% crash-free users > 99% Tools Tool What it provides Setup ------ ----------------- ------- Firebase Crashlytics Real-time crashes, ANRs, symbolicated stack traces Add FirebaseCrashlytics pod/SPM package App Store Connect Crash rate trend, crashes per session Built-in, no code needed Xcode Organizer Aggregated crash logs from TestFlight + App Store Xcode → Window → Organizer → Crashes MetricKit On-device diagnostics, hang rate, launch time iOS 13+, automatic Recommended: Crashlytics (real-time alerts + search) + App Store Connect (trend validation) Crashlytics Setup iOS (Swift) Non-fatal errors (track without crashing) Android (Kotlin) Triage Framework Not all crashes are equal. Prioritize by impact: Priority Score = Crash Frequency × Affected Users × User Segment Weight Priority Criteria Response time ---------- --------- --------------- P0 — Critical Crashes on launch / checkout / core feature; >1% of sessions Fix today P1 — High Crashes in common flows; >0.1% of sessions Fix this release P2 — Medium Edge case crashes; <0.1% of sessions Fix next release P3 — Low Rare, non-blocking crashes; <0.01% of sessions Backlog Crashlytics Dashboard Triage 1. Sort by "Impact" (unique users affected), not frequency 2. Group: onboarding, checkout, core feature, background, launch 3. Assign P0/P1 to the top 3–5 issues 4. Set a velocity alert in Crashlytics for any issue affecting >0.5% of users Reading a Crash Report Steps to debug: 1. Open the file and line in Xcode (UserProfileVC.swift:87) 2. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills eronred/crash-analytics