vybekiit 0.7.29 → 0.7.33

package/dist/global-skills/firebase-basics/references/android_setup.md

@@ -1,41 +1,247 @@
-# 🛠️ Firebase Android Setup Guide
+# Firebase Android Setup Guide
 
 ______________________________________________________________________
 
-## 📋 Prerequisites
+## Prerequisites
 
-## Before running these commands, ensure you are authenticated: `npx -y firebase-tools@latest login` (or `npx -y firebase-tools@latest login --no-localhost` on remote servers)
+1. **Firebase CLI**: Make sure the Firebase CLI is available and authenticated.
 
-## 0. Create an Android application
+   For detailed instructions about the Firebase CLI, see
+   `firebase_basics/references/local-env-setup`. Here are high-level
+   instructions for setting up the Firebase CLI.
 
-if you haven't already created an android application, create one.
+   1. Ensure the Firebase CLI is available:
 
-## 1. Create a Firebase Project
+      ```bash
+      npx -y firebase-tools@latest --version
+      ```
 
-If you haven't already created a project, create a new cloud project with a
-unique ID:
-`npx -y firebase-tools@latest projects:create <UNIQUE_PROJECT_ID> --display-name '<DISPLAY_NAME>'`
-*Example:*
-`npx -y firebase-tools@latest projects:create my-cool-app-20260330 --display-name 'MyCoolApp'`
+   1. Login to the CLI:
+
+      - local:
+
+        ```bash
+        npx -y firebase-tools@latest login
+        ```
+
+      - remote servers:
+
+        ```bash
+        npx -y firebase-tools@latest login --no-localhost
+        ```
+
+1. **Android project**: Create or use an existing Android project in an
+   Android-development IDE.
+
+______________________________________________________________________
+
+## 1. Check if the Android project is connected to a Firebase Project
+
+Check if the Android project already has a `google-services.json` file in its
+**module (app-level)** root directory.
+
+### `google-services.json` file is present
+
+If the Android project already has a `google-services.json` file, do NOT create
+a new Firebase project or re-register the app — skip steps 2 through 4 below.
+Instead, verify the existing Firebase setup within the codebase and fix anything
+that is missing:
+
+- The `google-services.json` file is in the **module (app-level)** root
+  directory: `app/google-services.json`
+
+- The Google services Gradle plugin (`google-services`) is added to *both* the
+  project-level and module (app-level) Gradle build files. If it is missing from
+  either file, add it by following step 5 below.
+
+### `google-services.json` file is NOT present
+
+If the Android project does NOT already have a `google-services.json` file, then
+proceed with the remaining steps in this guide.
+
+______________________________________________________________________
+
+## 2. Create a new Firebase project or use an existing one
+
+Check if there's an existing Firebase Project available for use with the Android
+project:
+
+```bash
+npx -y firebase-tools@latest projects:list
+```
+
+- **If existing Firebase Project:** Ask the human user if they want to use the
+  existing project.
+
+- **If no existing Firebase Project or human user does not want to use an
+  existing project:** Create a new Firebase Project.
+
+  Provide a required unique PROJECT_ID and an optional PROJECT_DISPLAY_NAME:
+
+  ```bash
+  npx -y firebase-tools@latest projects:create <UNIQUE_PROJECT_ID> --display-name <PROJECT_DISPLAY_NAME>
+  ```
+
+  *Example:*
 
-### 2. Register Your Android App
+  ```bash
+  npx -y firebase-tools@latest projects:create my-cool-app-20260330 --display-name MyCoolApp
+  ```
+
+______________________________________________________________________
+
+## 3. Register the Android project
+
+Register the app module (package name) of the Android project with the Firebase
+project. Provide an optional APP_DISPLAY_NAME and required PACKAGE_NAME:
+
+```bash
+npx -y firebase-tools@latest apps:create ANDROID <APP_DISPLAY_NAME> --package-name <PACKAGE_NAME> --project <PROJECT_ID>
+```
 
-Link your Android app module (package name) to your project. Notice that the
-display name is passed as a positional argument at the end:
-`npx -y firebase-tools@latest apps:create ANDROID '<APP_DISPLAY_NAME>' --package-name '<PACKAGE_NAME>' --project <PROJECT_ID>`
 *Example:*
-`npx -y firebase-tools@latest apps:create ANDROID 'MyApplication' --package-name 'com.example.myapplication' --project my-cool-app-20260330`
 
-### 3. Download `google-services.json`
+```bash
+npx -y firebase-tools@latest apps:create ANDROID MyApplication --package-name com.example.myapplication --project my-cool-app-20260330
+```
+
+NOTE: A package name is often referred to as an *application ID* within an
+Android project. Find an app's package name in the module (app-level) Gradle
+file, usually `app/build.gradle.kts`.
+
+______________________________________________________________________
+
+## 4. Obtain and save `google-services.json`
+
+1. Fetch the Firebase configuration file (`google-services.json`) using the
+   Firebase Android APP_ID (which is printed in the output of the previous
+   `apps:create` command):
+
+   ```bash
+   npx -y firebase-tools@latest apps:sdkconfig ANDROID <APP_ID> --project <PROJECT_ID>
+   ```
+
+1. Save the configuration file within the **module (app-level)** root directory
+   of the Android project: `app/google-services.json`
+
+______________________________________________________________________
+
+## 5. Add the `google-services` plugin
+
+> [!IMPORTANT] **[AGENT] RESOLVING THE PLUGIN VERSION DETERMINISTICALLY** Never
+> guess or hardcode a memorized out-of-date plugin version. Before adding
+> dependencies, you MUST query the latest available versions directly from the
+> Google Maven Repository:
+>
+> ```bash
+> # Find the latest Google services Gradle plugin version
+> curl -s https://dl.google.com/dl/android/maven2/com/google/gms/google-services/maven-metadata.xml | grep -oE '<latest>[^<]+' | cut -d'>' -f2
+> ```
+
+These changes are made to the Android project's Gradle files.
+
+### Project-level `build.gradle.kts` (`<project>/build.gradle.kts`)
+
+Add the latest version of the Google services Gradle plugin to the `plugins`
+block:
+
+```kotlin
+plugins {
+    // ... other plugins
+
+    // [AGENT] Fetch the latest resolved version using the Gradle command above
+    id("com.google.gms.google-services") version "<latest_plugin_version>" apply false
+}
+```
+
+### Module (app-level) `build.gradle.kts` (`<project>/<app-module>/build.gradle.kts`)
+
+Add the Google services Gradle plugin to the `plugins` block:
+
+```kotlin
+plugins {
+    // ... other plugins
+    id("com.google.gms.google-services")
+}
+```
+
+______________________________________________________________________
+
+## 6. App Check (Debug Token Persistence)
+
+When using App Check on Android emulators or local development,
+`DebugAppCheckProviderFactory.getInstance()` generates a UUID token and stores
+it in `SharedPreferences`. Wiping emulator data, clearing app storage, or fresh
+installs generate a new UUID in Logcat, causing debug token churn in the
+Firebase Console.
+
+> [!WARNING] **CRITICAL: Never Hardcode or Commit Debug Tokens** App Check debug
+> tokens allow clients to bypass attestation and access backend resources
+> without a genuine device. **Never hardcode debug token strings in
+> build.gradle.kts, Java, or Kotlin files, and never commit tokens to version
+> control.** If a token is compromised, revoke it immediately in the Firebase
+> Console.
+
+To persist a stable debug token across emulator resets and testing without
+committing secrets:
+
+1. Obtain or generate a stable UUID debug token and register it in the Firebase
+   Console under **Security > App Check > Apps > Manage debug tokens**.
+
+1. Store the token in your project's gitignored `local.properties`:
+
+   ```properties
+   # In local.properties (ensure this file is in your .gitignore!)
+   APP_CHECK_DEBUG_TOKEN=<YOUR_DEBUG_TOKEN>
+   ```
+
+1. Inject the secret in `app/build.gradle.kts` for instrumentation/testing:
+
+   ```kotlin
+   val localProperties = java.util.Properties().apply {
+       val localPropertiesFile = rootProject.file("local.properties")
+       if (localPropertiesFile.exists()) {
+           load(localPropertiesFile.inputStream())
+       }
+   }
+   val appCheckDebugToken = localProperties.getProperty("APP_CHECK_DEBUG_TOKEN")
+       ?: System.getenv("APP_CHECK_DEBUG_TOKEN") ?: ""
+
+   android {
+       defaultConfig {
+           // For normal emulator runs (injects into AndroidManifest)
+           manifestPlaceholders["firebaseAppCheckDebugSecret"] = appCheckDebugToken
+
+           // For instrumentation tests
+           if (appCheckDebugToken.isNotEmpty()) {
+               testInstrumentationRunnerArguments["firebaseAppCheckDebugSecret"] = appCheckDebugToken
+           }
+       }
+   }
+   ```
+
+1. In your application or activity, install the debug provider for debug builds:
+
+   ```kotlin
+   if (BuildConfig.DEBUG) {
+       Firebase.appCheck.installAppCheckProviderFactory(
+           DebugAppCheckProviderFactory.getInstance()
+       )
+   }
+   ```
+
+______________________________________________________________________
 
-## Fetch the configuration file using the App ID (which is printed in the output of the previous command): `npx -y firebase-tools@latest apps:sdkconfig ANDROID <APP_ID> --project <PROJECT_ID>` *Example output extraction to file:* ` # (Output must be saved as app/google-services.json)`
+## Verification plan
 
-## ✅ Verification Plan
+### Manual verification
 
-### Manual Verification
+Validate that the Firebase Project was created and the Firebase Android App was
+registered successfully:
 
-Validate that the project was created and registered successfully:
-`npx -y firebase-tools@latest projects:list`
-`npx -y firebase-tools@latest apps:list --project <PROJECT_ID>`
+```bash
+npx -y firebase-tools@latest projects:list
+npx -y firebase-tools@latest apps:list --project <PROJECT_ID>
+```
 
 ______________________________________________________________________

package/dist/global-skills/firebase-basics/references/ios_setup.md

@@ -111,3 +111,60 @@ class AppDelegate: UIResponder, UIApplicationDelegate {
   }
 }
 ```
+
+## 4. App Check (Debug Token Persistence)
+
+When using App Check in local development or the iOS Simulator, the Firebase iOS
+SDK generates a new UUID debug token whenever `NSUserDefaults` is erased (such
+as during a simulator reset or fresh install). This causes debug token churn and
+invalidates tokens previously registered in the Firebase console.
+
+> [!WARNING] **CRITICAL: Never Hardcode or Commit Debug Tokens** App Check debug
+> tokens allow clients to bypass attestation and access backend resources
+> without a genuine device. Treat them as sensitive secrets. **Never commit
+> debug tokens into version control or hardcode them directly into source
+> code.** If a token is compromised, revoke it immediately in the Firebase
+> Console.
+
+To persist a stable debug token across simulator resets without committing
+secrets:
+
+1. Obtain or generate a stable UUID debug token and register it in the Firebase
+   Console under **Security > App Check > Apps > Manage debug tokens**.
+
+1. Supply `AppCheckDebugToken` via your local environment instead of hardcoding
+   it in code:
+
+   - **Xcode Scheme Environment Variables (Recommended):**
+
+     - Select **Product > Scheme > Edit Scheme...** (or `Cmd + <`).
+     - Navigate to **Run > Arguments > Environment Variables**.
+     - Add `AppCheckDebugToken = <YOUR_DEBUG_TOKEN>`.
+     - *Tip:* Keep your personal scheme unshared or ensure user scheme data
+       (`xcuserdata/`) is included in `.gitignore` so your personal debug token
+       is not committed.
+
+   - **In Code (Only with Secure / Gitignored Loading):** If setting the
+     environment variable in code before initializing
+     `AppCheckDebugProviderFactory`, load the token dynamically from a
+     gitignored local file or build configuration—never hardcode the raw token
+     string:
+
+     ```swift
+     #if DEBUG
+     // ⛔️ DO NOT hardcode literal tokens: setenv("AppCheckDebugToken", "secret-uuid", 0)
+     // ✅ SAFE: Load dynamically from a gitignored local file, xcconfig, or process environment
+     // Note: loadGitIgnoredDebugToken() is a placeholder for your custom helper (e.g., reading from a gitignored plist)
+     if let debugToken = loadGitIgnoredDebugToken() {
+       setenv("AppCheckDebugToken", debugToken, 0)
+     }
+     let providerFactory = AppCheckDebugProviderFactory()
+     AppCheck.setAppCheckProviderFactory(providerFactory)
+     #endif
+
+     FirebaseApp.configure() // Must be called AFTER setting the App Check provider factory
+     ```
+
+Setting this environment variable avoids invalidating tokens registered in the
+Firebase console by ensuring a consistent debug token is reused across simulator
+resets and fresh app installs.

package/dist/global-skills/firebase-basics/references/web_setup.md

@@ -75,3 +75,55 @@ async function getUsers() {
   });
 }
 ```
+
+## 5. App Check (Debug Token Persistence)
+
+When developing locally with App Check on Web, setting
+`self.FIREBASE_APPCHECK_DEBUG_TOKEN = true` generates a temporary UUID token in
+the browser console and stores it in browser storage (IndexedDB). Clearing site
+data, using incognito/private browsing, or switching browsers causes debug token
+churn and invalidates console registration.
+
+> [!WARNING] **CRITICAL: Never Hardcode or Commit Debug Tokens** App Check debug
+> tokens allow clients to bypass attestation and access backend resources
+> without a genuine client. Treat them as sensitive secrets. **Never commit
+> debug tokens to version control or hardcode raw token strings in client
+> files.** If a token is compromised, revoke it immediately in the Firebase
+> Console.
+
+To persist a stable debug token across browser resets without leaking secrets:
+
+1. Obtain or generate a stable UUID debug token and register it in the Firebase
+   Console under **Security > App Check > Apps > Manage debug tokens**.
+
+1. Add the token to a local, gitignored environment file (e.g. `.env.local`):
+
+   ```bash
+   # In .env.local (ensure this file is in your .gitignore!)
+   NEXT_PUBLIC_APP_CHECK_DEBUG_TOKEN="<YOUR_DEBUG_TOKEN>"
+   # Or for Vite:
+   # VITE_APPCHECK_DEBUG_TOKEN="<YOUR_DEBUG_TOKEN>"
+   ```
+
+1. Configure your code before initializing App Check:
+
+   ```javascript
+   import { initializeAppCheck, ReCaptchaEnterpriseProvider } from "firebase/app-check";
+
+   if (typeof self !== "undefined") {
+     if (typeof process !== "undefined" && process.env.NODE_ENV === "development") {
+       // ✅ SAFE: Load dynamically from Next.js environment variable; fallback to true to auto-generate
+       self.FIREBASE_APPCHECK_DEBUG_TOKEN =
+         process.env.NEXT_PUBLIC_APP_CHECK_DEBUG_TOKEN || true;
+     } else if (typeof import.meta !== "undefined" && import.meta.env?.DEV) {
+       // ✅ SAFE: Load dynamically from Vite environment variable; fallback to true to auto-generate
+       self.FIREBASE_APPCHECK_DEBUG_TOKEN =
+         import.meta.env.VITE_APPCHECK_DEBUG_TOKEN || true;
+     }
+   }
+
+   const appCheck = initializeAppCheck(app, {
+     provider: new ReCaptchaEnterpriseProvider("/* reCAPTCHA site key */"),
+     isTokenAutoRefreshEnabled: true,
+   });
+   ```

package/dist/global-skills/firebase-crashlytics/SKILL.md

@@ -3,7 +3,9 @@ name: firebase-crashlytics
 description: Comprehensive guide for Firebase Crashlytics, including provisioning and SDK usage. Use this skill when the user needs help setting up Crashlytics, adding crash reporting, or using the Crashlytics SDK in their application.
 compatibility: This skill is best used with the Firebase CLI, but does not require it. Firebase CLI can be accessed through `npx -y firebase-tools@latest`.
 metadata:
+  author: Google LLC
   category: CloudObservabilityAndMonitoring
+disable-model-invocation: true
 ---
 
 # Crashlytics

package/dist/global-skills/firebase-crashlytics/references/android_setup.md

@@ -1,80 +1,98 @@
-# 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 ANDROID <display-name> --package-name=<package-name>`
-
-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.
+# Firebase Crashlytics - Android Setup Guide (Kotlin)
+
+This guide describes the SDK setup and basic usage patterns for Firebase
+Crashlytics in an Android app using Kotlin DSL (`build.gradle.kts`) and Kotlin
+code.
+
+## Prerequisites
+
+IMPORTANT: Before specifically working with Firebase Crashlytics, make sure to
+use the skill and reference `firebase_basics/references/android_setup` to ensure
+the following is done.
+
+- The Firebase CLI is available and authenticated.
+- An Android project exists and is registered with a Firebase Project.
+- The Android project has a Firebase config file (`google-services.json`) and
+  the Google services Gradle plugin (`google-services`).
+
+______________________________________________________________________
+
+## 1. Add dependencies to Gradle build files
+
+> [!IMPORTANT] **[AGENT] RESOLVING THE SDK & PLUGIN VERSIONS DETERMINISTICALLY**
+> Never guess or hardcode a memorized out-of-date SDK or plugin version. Before
+> adding dependencies, you MUST query the latest available versions directly
+> from the Google Maven Repository:
+>
+> ```bash
+> # Find the latest Firebase Android BoM version
+> curl -s https://dl.google.com/dl/android/maven2/com/google/firebase/firebase-bom/maven-metadata.xml | grep -oE '<latest>[^<]+' | cut -d'>' -f2
+>
+> # Find the latest Crashlytics Gradle plugin version
+> curl -s https://dl.google.com/dl/android/maven2/com/google/firebase/firebase-crashlytics-gradle/maven-metadata.xml | grep -oE '<latest>[^<]+' | cut -d'>' -f2
+>
+> # Find the latest firebase-crashlytics version
+> curl -s https://dl.google.com/dl/android/maven2/com/google/firebase/firebase-crashlytics/maven-metadata.xml | grep -oE '<latest>[^<]+' | cut -d'>' -f2
+>
+> # Find the latest firebase-crashlytics-ndk version
+> curl -s https://dl.google.com/dl/android/maven2/com/google/firebase/firebase-crashlytics-ndk/maven-metadata.xml | grep -oE '<latest>[^<]+' | cut -d'>' -f2
+> ```
+>
+> If the dependency is already declared, fetch the exact resolved version
+> currently active in the workspace's build graph:
+>
+> ```bash
+> ./gradlew -q :app:dependencyInsight --dependency firebase-crashlytics --configuration releaseRuntimeClasspath
+> ```
+
+These changes are made to the 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.
+Add the latest version of the Crashlytics Gradle plugin to the `plugins` block:
 
 ```kotlin
 plugins {
     // ... other plugins
+
+    // [AGENT] Fetch the latest resolved version using the Gradle command above
     id("com.google.firebase.crashlytics") version "<latest_plugin_version>" apply false
 }
 ```
 
-### App-level `build.gradle.kts` (`<project>/<app-module>/build.gradle.kts`)
+### Module (app-level) `build.gradle.kts` (`<project>/<app-module>/build.gradle.kts`)
 
-1. Add the Crashlytics plugin to the `plugins` block:
+1. Add the Crashlytics Gradle plugin to the `plugins` block:
 
    ```kotlin
    plugins {
        // ... other plugins
+
        id("com.google.firebase.crashlytics")
    }
    ```
 
-1. 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.
+1. Add the Firebase Crashlytics dependency to the `dependencies` block:
 
    ```kotlin
    dependencies {
        // ... other dependencies
 
-       // Import the Firebase BoM
+       // [AGENT] Fetch the latest resolved version using the Gradle command above
        implementation(platform("com.google.firebase:firebase-bom:<latest_bom_version>"))
 
-       // Add the dependencies for the Crashlytics and Analytics
+       // Add the dependency for the Firebase Crashlytics library
+       // When using the BoM, don't specify versions in Firebase library dependencies
        implementation("com.google.firebase:firebase-crashlytics")
-       implementation("com.google.firebase:firebase-analytics")
    }
    ```
 
-## Follow up Steps
+______________________________________________________________________
 
-### Optional: Install the NDK SDK to capture native crashes
+## 2. *Optional:* Install the NDK SDK to capture native crashes
 
-If your app uses native code (C/C++), or includes a library with native code,
-you can configure Crashlytics to report native crashes.
+If the Android project uses native code (C/C++), or includes a library with
+native code, configure Crashlytics to report native crashes.
 
 App-level `build.gradle.kts` (`<project>/<app-module>/build.gradle.kts`)
 
@@ -83,23 +101,27 @@ App-level `build.gradle.kts` (`<project>/<app-module>/build.gradle.kts`)
    ```kotlin
    dependencies {
        // ... other dependencies
+
+       // [AGENT] Fetch the latest resolved version using the Gradle command above
+       implementation(platform("com.google.firebase:firebase-bom:<latest_bom_version>"))
+
+       // Add the dependency for the Firebase Crashlytics NDK library
+       // When using the BoM, don't specify versions in Firebase library dependencies
        implementation("com.google.firebase:firebase-crashlytics-ndk")
    }
    ```
 
-1. Enable the `nativeSymbolUpload` flag in your `buildTypes` configuration. This
-   will automatically upload symbol files for your native code, which are
+1. Enable the `nativeSymbolUpload` flag in the `buildTypes` configuration. This
+   will automatically upload symbol files for the native code, which are
    required to symbolicate native crash reports.
 
    ```kotlin
-   import com.google.firebase.crashlytics.buildtools.gradle.CrashlyticsExtension
-
    android {
        // ... other config
        buildTypes {
            getByName("release") {
                // ...
-               configure<CrashlyticsExtension> {
+               firebaseCrashlytics {
                    nativeSymbolUploadEnabled = true
                }
            }
@@ -107,49 +129,55 @@ App-level `build.gradle.kts` (`<project>/<app-module>/build.gradle.kts`)
    }
    ```
 
-After these changes, Crashlytics will automatically report crashes in your app's
+After these changes, Crashlytics will automatically report crashes in the app's
 native code.
 
-### Required: Force a Test Crash
+______________________________________________________________________
+
+## 3. *Required:* Force a test crash
 
-To verify that Crashlytics is correctly installed, you need to force a test
-crash in the app.
+To verify that Crashlytics is correctly set up in the Android project, force a
+test crash in the app.
 
-1. Add code to your main activity (e.g., in `onCreate`) to trigger a crash a few
+1. Add code to the main activity (e.g., in `onCreate`) to trigger a crash a few
    seconds after app startup:
 
    ```kotlin
    import android.os.Handler
    import android.os.Looper
 
-   // ... in your Activity's onCreate method or similar startup logic
+   // ... in the Activity's onCreate method or similar startup logic
    Handler(Looper.getMainLooper()).postDelayed({
        throw RuntimeException("Test Crash") // Force a crash after 3 seconds
    }, 3000)
    ```
 
-1. Run your app on a device or emulator. The app should crash after a short
+1. Run the app on a device or emulator. The app should crash after a short
    delay.
 
 1. Restart the app. The Crashlytics SDK will send the crash report to Firebase
    on the next app launch.
 
-1. After a few minutes, the crash should be available in the Firebase console.
-   Go to **DevOps & Engagement** > **Crashlytics** to view your dashboard and
-   crash reports.
+1. After a few minutes, the crash should be available in Firebase.
+
+   - If the Firebase MCP server is installed, use the `get_report` tool to
+     verify that a crash was received.
+   - As a fallback, tell the human user to go to the Crashlytics dashboard in
+     the Firebase console to verify the new crash report. Provide the human user
+     with a constructed Firebase console URL using the Firebase PROJECT_ID and
+     the PACKAGE_NAME:
+     `https://console.firebase.google.com/u/0/project/PROJECT_ID/crashlytics/app/android:PACKAGE_NAME/issues`
+
+1. After verifying that Firebase has received the crash report -- either using
+   the `get_report` tool or manually viewing it in the Firebase console --
+   remove the code that triggers the test crash.
 
-- If the Firebase MCP server is installed, use the `get_report` tool to check
-  that a crash was received.
-- As a fallback, visit the Crashlytics dashboard in the Firebase console to see
-  the new crash report.
+______________________________________________________________________
 
-5. After verifying that Firebase has received the crash report - either using
-   the `get_report` tool or manually viewing it in the Firebase console - remove
-   the code from step 1 that triggers the crash. This prevents the application
-   from always crashing on start up after a delay.
+## Optional additional steps
 
-### Optional: Add custom debugging information
+### Add custom debugging information
 
-Customize reports to help you better understand what's happening in your app and
-the circumstances around events reported to Crashlytics. See
-[Customize Crash Reports for Android](https://firebase.google.com/docs/crashlytics/android/customize-crash-reports.md).
+Customize reports to help better understand what's happening in the app and the
+circumstances around events reported to Crashlytics. See
+https://firebase.google.com/docs/crashlytics/android/customize-crash-reports.md.txt.

package/dist/global-skills/firebase-crashlytics/references/ios_setup.md

@@ -66,6 +66,7 @@ two options to be done manually.
 **For SwiftUI Apps (in `AppDelegate.swift`):**
 
 *File: `AppDelegate.swift`*
+
 ```swift
 import UIKit
 import FirebaseCore

package/dist/global-skills/firebase-data-connect/SKILL.md

@@ -2,7 +2,9 @@
 name: firebase-data-connect
 description: Builds and deploys Firebase SQL Connect (aka Firebase Data Connect) backends with PostgreSQL securely. Use when designing schemas with tables and relations, writing authorized queries and mutations, configuring real-time data updates, or generating type-safe SDKs. Use when you need a relational database with Firebase, or when the user mentions SQL Connect or Data Connect.
 metadata:
+  author: Google LLC
   category: Databases
+disable-model-invocation: true
 ---
 
 # Firebase SQL Connect