Stats
Actions
Tags
'%20stop-opacity%3D'0.16'%2F%3E%3Cstop%20offset%3D'1'%20stop-color%3D'rgb(200%2C90%2C60)'%20stop-opacity%3D'0.03'%2F%3E%3C%2FlinearGradient%3E%3C%2Fdefs%3E%3Crect%20width%3D'320'%20height%3D'200'%20fill%3D'url(%23g)'%2F%3E%3Ccircle%20cx%3D'250'%20cy%3D'56'%20r%3D'92'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.06'%2F%3E%3Ccircle%20cx%3D'64'%20cy%3D'172'%20r%3D'58'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.05'%2F%3E%3C%2Fsvg%3E)
From firebase
Guides provisioning and SDK setup for Firebase Crashlytics on Android/iOS, plus configuring custom keys, logs, user identifiers, and non-fatal exception reporting.
How this skill is triggered — by the user, by Claude, or both
Slash command
/firebase:firebase-crashlyticsThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
This skill provides a complete guide for getting started with Crashlytics on
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.
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.
To learn how to setup Crashlytics in your application code, choose your platform:
The SDK provides a number of features to make crash reports more actionable.
To learn how to customize crash reports and add additional debugging data, consult the documentation for your platform.
npx claudepluginhub firebase/agent-skills --plugin firebaseGuides you through full Sentry setup in Flutter/Dart projects: error monitoring, tracing, profiling, session replay, logging, and native crash tracking.
Sets up Firebase CLI, authenticates, and configures active projects. Use when initializing Firebase or setting up google-services.json / GoogleService-Info.plist.
Analyzes iOS app crash logs from simulators/devices/TestFlight, symbolicates stack traces with dSYM files using atos, identifies common patterns and root causes.