Firebase Crashlytics
Provision Firebase Crashlytics and wire Android or iOS SDK usage so crashes and non-fatal errors are actionable in production.
Overview
Firebase Crashlytics is an agent skill most often used in Operate (also Ship) that guides Crashlytics provisioning, Android/iOS SDK setup, and richer crash report instrumentation.
Install
npx skills add https://github.com/firebase/agent-skills --skill firebase-crashlyticsWhat is this skill?
- End-to-end path: Firebase project and app prerequisites, then Android or iOS SDK setup references
- SDK customization: custom keys, custom logs, user identifiers, non-fatal exception reporting
- Optional Firebase CLI via `npx -y firebase-tools@latest` and MCP server to read collected crash data
- Platform split documentation: android_setup.md and ios_setup.md reference guides
- Points to firebase-basics skill when project or app provisioning is unclear
- 4 SDK customization areas listed (custom keys, logs, user identifiers, non-fatal exceptions)
- 2 platform setup guides (Android, iOS)
Adoption & trust: 36.1k installs on skills.sh; 345 GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
Your mobile app ships without structured crash visibility, so production failures are invisible until app-store reviews or angry support tickets.
Who is it for?
Indie mobile developers on Firebase who need a documented setup path and SDK customization checklist for Android or iOS.
Skip if: Web-only apps without Firebase mobile clients, or teams wanting server-side APM instead of Firebase mobile crash reporting.
When should I use this skill?
User needs help setting up Crashlytics, adding crash reporting, or using the Crashlytics SDK in their application.
What do I get? / Deliverables
Crashlytics is provisioned and instrumented so fatals and non-fatals surface with context you can inspect via Firebase tooling or the CLI MCP server.
- Crashlytics-enabled mobile app configuration
- Instrumented SDK usage (keys, logs, user id, non-fatals)
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Crash reporting is canonical on Operate because its value is reading and acting on live crash data after users hit real devices. Crashlytics is explicitly error and stability telemetry—not generic infra deploy or growth analytics.
Where it fits
You triage a spike in crashes using custom logs and user IDs added after the skill’s SDK usage section.
You enable Crashlytics before store submission so first-day installs produce readable crash buckets.
You link the Firebase app and drop in the Android or iOS SDK following the reference setup docs.
How it compares
Firebase mobile crash SDK guide—not a generic test runner or backend error tracker like Sentry for non-Firebase stacks.
Common Questions / FAQ
Who is firebase-crashlytics for?
Solo builders shipping Android or iOS apps on Firebase who want agent-guided Crashlytics provisioning, SDK integration, and richer crash context.
When should I use firebase-crashlytics?
Use it when setting up Crashlytics, adding crash reporting to app code, or customizing reports—during Ship launch hardening for first-time setup and during Operate when improving crash diagnosability.
Is firebase-crashlytics safe to install?
It may invoke Firebase CLI and modify mobile project configuration; review the Security Audits panel on this page and validate Firebase project access controls.
SKILL.md
READMESKILL.md - Firebase Crashlytics
# Crashlytics This skill provides a complete guide for getting started with Crashlytics on Android or iOS. Crash data collected from client applications can be read using the MCP server in the Firebase CLI. ## Prerequisites Provisioning Crashlytics requires both a Firebase project and a Firebase app, either Android or iOS. To read the data collected by Crashlytics, install the MCP server in the Firebase CLI. See the `firebase-basics` skill for references. ## SDK Setup To learn how to setup Crashlytics in your application code, choose your platform: * **Android**: [android_setup.md](references/android_setup.md) * **iOS**: [ios_setup.md](references/ios_setup.md) ## SDK Usage The SDK provides a number of features to make crash reports more actionable. * Add custom keys * Add custom logs * Set user identifiers * Report non-fatal exceptions To learn how to customize crash reports and add additional debugging data, consult the documentation for your platform. * **Android**: [Customize Crash Reports for Android](https://firebase.google.com/docs/crashlytics/android/customize-crash-reports.md) * **iOS**: [Customize Crash Reports for Apple Platforms](https://firebase.google.com/docs/crashlytics/ios/customize-crash-reports.md) # Firebase Crashlytics Android Setup Guide Important references: - Refer to the `firebase-basics` skills, particularly those for project and app setup, before proceeding. ## Project and App Setup Before you begin, ensure you have the following. If a `google-services.json` file is present, then use that Firebase project and app. Otherwise you may need to create them. - **Firebase CLI**: Installed and logged in (see `firebase-basics`). - **Firebase Project**: Created via `npx -y firebase-tools@latest projects:create` (see `firebase-basics`). - **Firebase App**: Created via `npx -y firebase-tools@latest apps:create <IOS|ANDROID|WEB> <package-name-or-bundle-id>` The `google-services.json` file must be present in the Android app's module directory. If missing, get the config using the Firebase CLI: `npx -y firebase-tools@latest apps:sdkconfig ANDROID <App-ID>`. ## Add Dependencies to Gradle Build These changes are made to your Android project's Gradle files. ### Project-level `build.gradle.kts` (`<project>/build.gradle.kts`) Add the latest version of the Crashlytics Gradle plugin to the `plugins` block. Fetch the [latest version from the Google Maven repository](https://maven.google.com/web/index.html?q=firebase-crashlytics-gradle#com.google.firebase:firebase-crashlytics-gradle) before adding this. ```kotlin plugins { // ... other plugins id("com.google.firebase.crashlytics") version "<latest_plugin_version>" apply false } ``` ### App-level `build.gradle.kts` (`<project>/<app-module>/build.gradle.kts`) 1. Add the Crashlytics plugin to the `plugins` block: ```kotlin plugins { // ... other plugins id("com.google.firebase.crashlytics") } ``` 2. Add the Firebase Crashlytics dependency to the `dependencies` block. It is recommended to use the Firebase Bill of Materials (BoM) to manage SDK versions. Fetch the [latest version from the Google Maven repository](https://maven.google.com/web/index.html?q=firebase-bom#com.google.firebase:firebase-bom) before adding this. ```kotlin dependencies { // ... other dependencies // Import the Firebase BoM implementation(platform("com.google.firebase:firebase-bom:<latest_bom_version>")) // Add the dependencies for the Crashlytics and Analytics