Source profileQuality 84/100

evanca/flutter-ai-rules/skills/firebase-app-check/SKILL.md

firebase-app-check

Use when implementing app attestation, configuring App Check providers, setting up debug tokens, enabling backend enforcement, or managing token refresh.

Source repository stars
604
Declared platforms
0
Static risk flags
0
Last source update
2026-08-04
Source checked
2026-08-04

Decision brief

What it does—and where it fits

This skill defines how to correctly implement Firebase App Check in Flutter applications, covering provider selection, debug configuration, enforcement rollout, and security hardening.

Best for

  • Setting up and activating Firebase App Check in a Flutter project.
  • Selecting the right attestation provider for each platform.
  • Configuring debug providers for development, testing, and CI.

Not for

  • Tasks that require unconfirmed production actions or broad system permissions.
  • Environments where the pinned source and install steps cannot be inspected.

Compatibility matrix

Platform support, with evidence labels

PlatformStatusEvidenceWhat to check
CodexNot declaredNo explicit evidencePortability before use
Claude CodeNot declaredNo explicit evidencePortability before use
CursorNot declaredNo explicit evidencePortability before use
Gemini CLINot declaredNo explicit evidencePortability before use
Open the compatibility checker

Installation

Inspect first. Install second.

The source command is displayed only when detected. A safe inspection prompt is always available so your agent can explain every action before execution.

Source-detected install commandSource
npx skills add https://github.com/evanca/flutter-ai-rules --skill "skills/firebase-app-check"
Safe inspection promptEditorial

Inspect the Agent Skill "firebase-app-check" from https://github.com/evanca/flutter-ai-rules/blob/b294a77b68b5508f8d3151fb93d87ed9622d2ff1/skills/firebase-app-check/SKILL.md at commit b294a77b68b5508f8d3151fb93d87ed9622d2ff1. List every install step, command, network request, credential, file read/write, external action, and rollback step. Explain whether it fits my task. Do not install or execute anything until I approve.

Workflow

What the source asks the agent to do

  1. 01

    1. Setup and Configuration

    Initialize App Check after Firebase.initializeApp() and before using any Firebase services:

    Register apps in the Firebase console under Project Settings App Check.For web, obtain a reCAPTCHA v3 site key from the Firebase console.Confirm activation completes before any Firestore, Storage, or RTDB calls.
  2. 02

    Setup Checklist

    1. Register apps in the Firebase console under Project Settings App Check. 2. For web, obtain a reCAPTCHA v3 site key from the Firebase console. 3. Confirm activation completes before any Firestore, Storage, or RTDB calls. 4. Consider setting a custom TTL — shorter TTLs are more…

    Register apps in the Firebase console under Project Settings App Check.For web, obtain a reCAPTCHA v3 site key from the Firebase console.Confirm activation completes before any Firestore, Storage, or RTDB calls.
  3. 03

    Platform-Specific Debug Setup

    iOS: Enable debug logging by adding -FIRDebugEnabled to Arguments Passed on Launch in Xcode. The debug token appears in the console output.

    iOS: Enable debug logging by adding -FIRDebugEnabled to Arguments Passed on Launch in Xcode. The debug token appears in the console output.Android: The debug token prints to logcat on first run. Filter by DebugAppCheckProvider.Web: Set self.FIREBASEAPPCHECKDEBUGTOKEN = true; in web/index.html before Firebase scripts load.
  4. 04

    When to Use

    Setting up and activating Firebase App Check in a Flutter project. Selecting the right attestation provider for each platform. Configuring debug providers for development, testing, and CI. Enabling enforcement and monitoring App Check metrics. Implementing token refresh handling…

    Setting up and activating Firebase App Check in a Flutter project.Selecting the right attestation provider for each platform.Configuring debug providers for development, testing, and CI.
  5. 05

    2. Provider Selection

    Android: | Provider | Use case | |---|---| | AndroidProvider.playIntegrity | Production (default) | | AndroidProvider.debug | Development / CI only |

    Android: | Provider | Use case | |---|---| | AndroidProvider.playIntegrity | Production (default) | | AndroidProvider.debug | Development / CI only |Apple (iOS / macOS): | Provider | Use case | |---|---| | AppleProvider.deviceCheck | Production default (iOS 11+, macOS 10.15+) | | AppleProvider.appAttest | Enhanced security (iOS 14+, macOS 14+) | | AppleProvider.appA…Web: | Provider | Use case | |---|---| | ReCaptchaV3Provider | Standard reCAPTCHA v3 | | ReCaptchaEnterpriseProvider | Enhanced with additional features |

Permission review

Static risk signals and limitations

No configured static risk pattern was detected

This is not proof of safety. Runtime behavior, indirect dependencies, and hidden external systems are outside the static scan.

Evidence record

Why each signal appears

EvidenceSourceComputedTestedEditorial
SignalValueEvidence typeMeaning
Quality score84/100ComputedDocumentation, specificity, maintenance, and trust rules
Repository stars604SourceRepository attention, not individual Skill quality
Compatibility0 platformsSourceDeclared in the catalog source record
Usage guideautomated source guideEditorialGenerated or reviewed according to the visible evidence level

Pinned source

Provenance and original SKILL.md

Repository
evanca/flutter-ai-rules
Skill path
skills/firebase-app-check/SKILL.md
Commit
b294a77b68b5508f8d3151fb93d87ed9622d2ff1
License
MIT
Collected
2026-08-04
Default branch
main
View the original SKILL.md

Firebase App Check Skill

This skill defines how to correctly implement Firebase App Check in Flutter applications, covering provider selection, debug configuration, enforcement rollout, and security hardening.

When to Use

Use this skill when:

  • Setting up and activating Firebase App Check in a Flutter project.
  • Selecting the right attestation provider for each platform.
  • Configuring debug providers for development, testing, and CI.
  • Enabling enforcement and monitoring App Check metrics.
  • Implementing token refresh handling and custom TTL configuration.

1. Setup and Configuration

flutter pub add firebase_app_check
import 'package:firebase_app_check/firebase_app_check.dart';

Initialize App Check after Firebase.initializeApp() and before using any Firebase services:

await Firebase.initializeApp();
await FirebaseAppCheck.instance.activate(
  webProvider: ReCaptchaV3Provider('recaptcha-v3-site-key'),
  androidProvider: AndroidProvider.playIntegrity,
  appleProvider: AppleProvider.deviceCheck,
);

Setup Checklist

  1. Register apps in the Firebase console under Project Settings > App Check.
  2. For web, obtain a reCAPTCHA v3 site key from the Firebase console.
  3. Confirm activation completes before any Firestore, Storage, or RTDB calls.
  4. Consider setting a custom TTL — shorter TTLs are more secure but consume quota faster.

2. Provider Selection

Android:

ProviderUse case
AndroidProvider.playIntegrityProduction (default)
AndroidProvider.debugDevelopment / CI only

Apple (iOS / macOS):

ProviderUse case
AppleProvider.deviceCheckProduction default (iOS 11+, macOS 10.15+)
AppleProvider.appAttestEnhanced security (iOS 14+, macOS 14+)
AppleProvider.appAttestWithDeviceCheckFallbackApp Attest with Device Check fallback
AppleProvider.debugDevelopment / CI only

Web:

ProviderUse case
ReCaptchaV3ProviderStandard reCAPTCHA v3
ReCaptchaEnterpriseProviderEnhanced with additional features

Android note: For certain Android devices, enable "Meets basic device integrity" in the Google Play console to ensure proper App Check functionality.


3. Development and Testing

Use debug providers during development to run in emulators or CI environments:

await Firebase.initializeApp();
await FirebaseAppCheck.instance.activate(
  androidProvider: AndroidProvider.debug,
  appleProvider: AppleProvider.debug,
);

Platform-Specific Debug Setup

iOS: Enable debug logging by adding -FIRDebugEnabled to Arguments Passed on Launch in Xcode. The debug token appears in the console output.

Android: The debug token prints to logcat on first run. Filter by DebugAppCheckProvider.

Web: Set self.FIREBASE_APPCHECK_DEBUG_TOKEN = true; in web/index.html before Firebase scripts load.

Register Debug Tokens

  1. Copy the debug token from the device/emulator console output.
  2. In the Firebase console, navigate to App Check > Apps > Manage debug tokens.
  3. Add the token. It is immediately active for that app.

Token Listener for Custom Backends

FirebaseAppCheck.instance.onTokenChange.listen((token) {
  // Attach token to custom backend requests
  // e.g., set as Authorization header
});
  • Never use debug providers or share debug tokens in production builds.
  • Keep debug tokens private — do not commit them to public repositories.
  • Revoke compromised debug tokens immediately from the Firebase console.

4. Enforcement Rollout

Follow this sequence to avoid disrupting legitimate users:

  1. Deploy App Check activation code to all app versions.
  2. Monitor App Check metrics in the Firebase console — wait until most traffic shows valid tokens.
  3. Enable enforcement gradually, starting with non-critical Firebase services (e.g., Cloud Storage before Firestore).
  4. Verify that unverified request percentage drops to near zero before enforcing on critical services.
  • Once enforcement is enabled, only apps with valid App Check tokens can access protected Firebase resources.
  • Use App Check in combination with Firebase Security Rules for defense in depth.
  • Implement proper error handling for App Check verification failures — surface a user-friendly message rather than a raw error.

5. Security Best Practices

  • Never disable App Check in production builds once enabled.
  • Implement a fallback mechanism for App Check verification failures (e.g., retry with exponential backoff).
  • Regularly review App Check metrics to identify potential abuse patterns.
  • App Check tokens are automatically refreshed at approximately half the TTL duration.
  • For high-security applications, use the shortest practical TTL.
  • Implement server-side verification for critical operations using the Firebase Admin SDK:
// Node.js Admin SDK example for verifying App Check tokens
const appCheckToken = req.header('X-Firebase-AppCheck');
const appCheckClaims = await getAppCheck().verifyToken(appCheckToken);

References

Alternatives

Compare before choosing

Computed 10042,968

coreyhaines31/marketingskills

ab-testing

When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this," "which version is better," "test two versions," "statistical significance," "how long should I run this test," "growth experiments," "experiment velocity," "experiment backlog," "ICE score," "experimentation program

Computed 10023,781

alirezarezvani/claude-skills

app-store-optimization

App Store Optimization (ASO) toolkit for researching keywords, analyzing competitor rankings, generating metadata suggestions, and improving app visibility on Apple App Store and Google Play Store. Use when the user asks about ASO, app store rankings, app metadata, app titles and descriptions, app store listings, app visibility, or mobile app marketing on iOS or Android. Supports keyword research and scoring, competitor keyword analysis, metadata optimization, A/B test planning, launch checklist

Computed 1004,922

dotnet/skills

migrate-vstest-to-mtp

Migrates .NET test projects from VSTest to Microsoft.Testing.Platform (MTP). Use when user asks to "migrate to MTP", "switch from VSTest", "enable Microsoft.Testing.Platform", "use MTP runner", set OutputType=Exe only for test projects in Directory.Build.props, or mentions EnableMSTestRunner, EnableNUnitRunner, or UseMicrosoftTestingPlatformRunner. USE FOR: MTP behavioral differences vs VSTest (exit code 8, zero tests discovered, --ignore-exit-code, TESTINGPLATFORM_EXITCODE_IGNORE); centralizing

Computed 100165

JasonColapietro/suede-creator-skills

suede-ab-testing

Suede-owned experimentation discipline for hypotheses, sample sizing, test duration, significance, and repeatable experiment programs. Use when comparing variants, deciding whether a result is reliable, or building an experiment backlog and cadence. NOT FOR: analytics instrumentation (use suede-analytics), post-click conversion diagnosis (use suede-site-alchemy), or writing the variant copy itself (use suede-copy).