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.
Security Assessment
About crash-analytics
crash-analytics is a Claude skill that helps developers and app owners monitor, triage, and reduce their mobile app's crash rate, and understand how crash stability affects App Store discoverability, featuring, ratings, and retention. It activates on crash-related topics such as Crashlytics, crash rate, ANRs, crash-free sessions or users, symbolication, and firebase crashes, and positions crash rate as an App Store Optimization (ASO) signal with concrete targets (crash-free sessions above 99.5%, crash-free users above 99%).
The skill compares tooling options (Firebase Crashlytics, App Store Connect, Xcode Organizer, and MetricKit) and gives setup snippets for iOS (Swift/FirebaseCrashlytics) and Android (Kotlin/Gradle), including logging non-fatal errors and custom debugging keys. It provides a priority-scoring triage framework (P0–P3 by frequency and affected users), guidance for reading and debugging symbolicated crash reports, dSYM upload and symbolication steps, App Store Connect crash-trend interpretation, and a phased-rollout release strategy to limit blast radius. It closes with a template stability audit report and advice on responding to crash-driven one-star reviews.
It targets iOS and Android developers, mobile product owners, and ASO practitioners who want a structured, read-and-analyze approach to stability. The shell and CLI usage is limited to a documented, read-only dSYM upload command for symbolication; the rest is guidance, dashboards, and reporting — no destructive or risky operations.
FAQ
Which crash-reporting tools does it cover?
Firebase Crashlytics for real-time crashes and ANRs, App Store Connect for crash-rate trends, Xcode Organizer for aggregated logs, and MetricKit for on-device diagnostics. It recommends pairing Crashlytics with App Store Connect.
How does it decide which crashes to fix first?
It uses a priority score combining crash frequency, affected users, and user-segment weight, mapping issues to P0–P3 tiers with recommended response times — for example, launch or checkout crashes affecting over 1% of sessions are P0, fix today.
What platforms and setup are required?
iOS via the FirebaseCrashlytics pod/SPM package (Swift) and Android via the firebase-crashlytics Gradle dependency (Kotlin). MetricKit needs iOS 13+. App Store Connect crash data needs no code.
Does it run any risky commands?
No. The only shell usage is the standard, read-only dSYM upload command for symbolication; everything else is guidance, triage frameworks, and report templates.
Install crash-analytics
Quick Setup:
- Copy the skill folder to
.claude/skills/ - Claude will automatically detect and use the skill
Repository
eronred/aso-skills