Skip to content
Firebase Basics

Firebase Basics Skill

Google's official Firebase entry-point skill — CLI login, project creation and selection, and programmatic retrieval of google-services.json and GoogleService-Info.plist.

GitHub Docs
Development
Released
Apache-2.0

Install

Install with the skills CLI

One command for Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf and dozens of other agents. Needs Node.js; the skill is fetched straight from google/skills.

$ npx skills add google/skills --skill firebase-basics

Run it in a terminal. The CLI finds the agents installed on your machine, asks which ones to add the skill to, and whether to install it into the folder you ran it from or for all your projects.

Other ways to install

Copy the whole skill folder — SKILL.md and any scripts or references beside it — into ~/.claude/skills/firebase-basics/, where Claude Code picks it up in every project. Only git is needed.

tmp=$(mktemp -d) && \
  git clone --depth 1 --branch main https://github.com/google/skills.git "$tmp" && \
  mkdir -p ~/.claude/skills && \
  cp -R "$tmp"/skills/cloud/firebase-basics ~/.claude/skills/firebase-basics

No scripts or references next to it? Saving the SKILL.md alone as ~/.claude/skills/firebase-basics/SKILL.md works too.

Using another agent? Its personal skills folder
Codex
~/.agents/skills/
Cursor
~/.cursor/skills/
GitHub Copilot
~/.copilot/skills/
Gemini CLI
~/.gemini/skills/
Windsurf
~/.codeium/windsurf/skills/
OpenCode
~/.config/opencode/skills/

About

  • Pinned `npx -y firebase-tools@latest` invocation so the CLI version never drifts
  • Browser-less `--no-localhost` login for remote shells and containers
  • Project creation and switching, with the agent required to ask which path you want
  • Config files fetched via `apps:sdkconfig` instead of a manual console download
  • Per-agent setup and refresh guides for Claude Code, Cursor, Gemini CLI and others

Every Firebase task an agent performs starts from the same three things: a current CLI, an authenticated session, and an active project. Get any of them wrong and the failure surfaces much later, as a confusing error in a deploy or an SDK call. This skill from Google's official skills repository owns exactly that entry point and nothing else.

It pins the agent to npx -y firebase-tools@latest for every command so a stale globally-installed CLI cannot drift the behaviour, and explicitly forbids suggesting a bare firebase invocation. It covers browser-less login with --no-localhost for remote shells and containers, checking and switching the active project with firebase use, and creating a new project with the project-ID rules spelled out. It also instructs the agent to pause and ask which of those two paths the developer wants rather than guessing.

The most practically useful directive is about config files: instead of sending a developer to the Firebase console to download google-services.json or GoogleService-Info.plist by hand, the agent fetches them with firebase apps:sdkconfig and writes them to the right path in the project. Per-agent setup references are included for Claude Code, Cursor, Gemini CLI, Antigravity, Android Studio and GitHub Copilot, along with refresh instructions for each, plus web, Android and iOS SDK setup guides.

It is deliberately narrow. Hosting deploys, Firestore, Auth, App Hosting, Data Connect, Crashlytics and Remote Config each have their own skill in the same repository — this one exists so the others start from a known-good state.

Try it

Once installed, ask your agent something like:

"Log me into Firebase from this remote shell, point the workspace at our staging project, and pull the Android config file into app/."

SKILL.md

The instructions your agent loads, as published by Google.

SKILL.md
name
firebase-basics
metadata
category: Serverless
description
Provides foundational Firebase CLI setup, CLI installation, version checks (`firebase-tools@latest --version`), CLI login (including --no-localhost), project creation, project selection (`firebase use`), and app config file downloads (`google-services.json`, `GoogleService-Info.plist`). Use ONLY for CLI login, project creation/switching, or downloading app config files. Don't use for Firebase Hosting deploy, Firestore, Auth, App Hosting, Data Connect, Crashlytics, or Remote Config.

Firebase Basics

Prerequisites

Complete these setup steps before proceeding:

  1. Local Environment Setup: Verify the environment is properly set up so we

can use Firebase tools:

  • Run npx -y firebase-tools@latest --version to check if the Firebase

CLI is installed.

  • Verify if the Firebase MCP server is installed using your existing

tools.

  • CRITICAL: Before configuring any extensions or agent environments

below, you MUST read
[references/local-env-setup.md](references/local-env-setup.md).

  • DO NOT SKIP this step: if 'firebase-basics' is the only Firebase

skill available to you, you must follow the reference for your agent
environment to set up the full suite of Firebase skills:

  • Gemini CLI: Review

[references/setup/gemini_cli.md](references/setup/gemini_cli.md)

  • Antigravity: Review

[references/setup/antigravity.md](references/setup/antigravity.md)

  • Android Studio: Review

[references/setup/android_studio.md](references/setup/android_studio.md)

  • Claude Code: Review

[references/setup/claude_code.md](references/setup/claude_code.md)

  • Cursor: Review

[references/setup/cursor.md](references/setup/cursor.md)

  • GitHub Copilot: Review

[references/setup/github_copilot.md](references/setup/github_copilot.md)

  • Other Agents: Review

[references/setup/other_agents.md](references/setup/other_agents.md)

  1. Authentication: Ensure you are logged in to Firebase so that commands

have the correct permissions. Run npx -y firebase-tools@latest login. For
environments without a browser (e.g., remote shells), use `npx -y
firebase-tools@latest login --no-localhost`.

  • The command should output the current user.
  • If you are not logged in, follow the interactive instructions from this

command to authenticate.

  1. Active Project: Most Firebase tasks require an active project context.

> [!IMPORTANT] For Agents: Before proceeding with project configuration,
> you MUST pause and ask the developer if they prefer to:
>
> 1. Provide an existing Firebase Project ID, or
> 1. Create a new Firebase project.

  • If using an existing Project ID:
  1. Check the current project by running `npx -y firebase-tools@latest

use`.

  1. If the command outputs Active Project: <project-id>, confirm with

the user if this is the intended project.

  1. If not, or if no project is active, set the project provided by the

user:

        npx -y firebase-tools@latest use <PROJECT_ID>
  • If creating a new project: Run the following command to create it:
        npx -y firebase-tools@latest projects:create <project-id> --display-name "<display-name>"

*Note: The <project-id> must be 6-30 characters, lowercase, and can
contain digits and hyphens. It must be globally unique.*

Firebase Usage Principles

Adhere to these principles:

  1. Use npx for CLI commands: To ensure you always use the latest version of

the Firebase CLI, always prepend commands with `npx -y
firebase-tools@latest instead of just firebase. For example, use npx -y
firebase-tools@latest --version. NEVER suggest the naked firebase` command
as an alternative.

  1. Prioritize official knowledge: For any Firebase-related knowledge,

consult the developerknowledge_search_documents MCP tool before falling
back to Google Search or your internal knowledge base. Including "Firebase"
in your search query significantly improves relevance.

  1. Follow Agent Skills for implementation guidance: Skills provide

opinionated workflows (CUJs), security rules, and best practices. Always
consult them to understand how to implement Firebase features correctly
instead of relying on general knowledge.

  1. Use Firebase MCP Server tools instead of direct API calls: Whenever you

need to interact with remote Firebase APIs (such as fetching Crashlytics
logs or executing Data Connect queries), use the tools provided by the
Firebase MCP Server instead of attempting manual API calls.

  1. Keep Plugin / Agent Skills updated: Since Firebase best practices evolve

quickly, regularly check for and install updates to their Firebase plugin or
Agent Skills. Similarly, if you encounter issues with outdated tools or
commands, follow the steps below based on your agent environment:

  • Antigravity: Follow

[references/refresh/antigravity.md](references/refresh/antigravity.md)

  • Gemini CLI: Follow

[references/refresh/gemini-cli.md](references/refresh/gemini-cli.md)

  • Claude Code: Follow

[references/refresh/claude.md](references/refresh/claude.md)

  • Cursor: Follow

[references/refresh/other-agents.md](references/refresh/other-agents.md)

  • Android Studio: Follow

[references/refresh/android_studio.md](references/refresh/android_studio.md)

  • Others: Follow

[references/refresh/other-agents.md](references/refresh/other-agents.md)

  1. Automate Config File Retrieval: When setting up iOS or Android apps, do

NOT direct users to the Firebase Console to download google-services.json
or GoogleService-Info.plist. Instead, use the Firebase CLI to fetch the
config programmatically:

  • For Android: `npx -y firebase-tools@latest apps:sdkconfig ANDROID

<APP_ID> --project <PROJECT_ID>`

  • For iOS: `npx -y firebase-tools@latest apps:sdkconfig IOS <APP_ID>

--project <PROJECT_ID>` Save the output to the appropriate location
(e.g., app/google-services.json for Android, or a path to be linked by
xcode-project-setup for iOS).

References
  • Initialize Firebase: See

[references/firebase-service-init.md](references/firebase-service-init.md)
when you need to initialize new Firebase services using the CLI.

  • Exploring Commands: See

[references/firebase-cli-guide.md](references/firebase-cli-guide.md) to
discover and understand CLI functionality.

  • SDK Setup: For detailed guides on adding Firebase to your app:
  • Web: See [references/web_setup.md](references/web_setup.md)
  • Android: See

[references/android_setup.md](references/android_setup.md)

  • iOS: See [references/ios_setup.md](references/ios_setup.md)
Common Issues
  • Login Issues: If the browser fails to open during the login step, use

npx -y firebase-tools@latest login --no-localhost instead.

  • Genkit: If using Genkit, install the skills:
    npx skills add genkit-ai/skills
Install
New

Firebase's official skill for adding sign-in to an app: enable providers from firebase.json, deploy the auth config, wire up the client SDK on web, Flutter, Android or iOS, and lock data down with request.auth rules.

Skill: Google Maps Platform

by Google Maps Platform

Featured

Google's official agent skill for writing production Maps Platform code — grounded in freshly fetched docs, with a demo key path that needs no billing account.

New

Firebase's official skill for Cloud Firestore: it detects or creates the database, picks the Standard or Enterprise edition guides, and covers provisioning, data modelling, indexes, security rules and SDK setup for Web, Python, iOS, Android and Flutter.

Browse all skills →