PluginBench
Skill
Official
Review
Audit score 70

firebase-local-env-setup

firebase/agent-skills

Bare minimum initial setup for Firebase: Node.js, CLI, and first-time login.

What is firebase-local-env-setup?

This skill handles the essential one-time setup required to start using Firebase with an agent. It covers Node.js verification (v20+), Firebase CLI installation, and authentication. Use this only for initial setup; for updates or troubleshooting on existing environments, use firebase-basics instead.

  • Verify Node.js is installed and version 20 or higher
  • Install Firebase CLI via npx
  • Authenticate with Firebase using login or no-localhost mode
  • Guide Node.js installation via nvm (macOS/Linux) or nvm-windows (Windows)
  • Provide agent-specific setup references for Gemini CLI, Antigravity, Claude Code, Cursor, GitHub Copilot, and other agents

How to install firebase-local-env-setup

npx skills add https://github.com/firebase/agent-skills --skill firebase-local-env-setup
Claude Code
Cursor
Windsurf
Cline

How to use firebase-local-env-setup

  1. 1.Run `node --version` to verify Node.js is installed and >= v20; install via nvm or official installer if needed
  2. 2.Run `npx -y firebase-tools@latest --version` to verify Firebase CLI is available
  3. 3.Run `npx -y firebase-tools@latest login` (or `--no-localhost` for remote environments) to authenticate
  4. 4.Review the setup document for your specific agent (Gemini CLI, Claude Code, Cursor, etc.) to install skills and MCP server
  5. 5.Confirm all steps are complete before proceeding with other Firebase tasks

Use cases

Good for
  • Setting up a new development machine for Firebase projects
  • Initializing a fresh agent environment before any Firebase work
  • Ensuring CLI and authentication are ready before deploying or managing Firebase services
  • Preparing a remote or headless environment for Firebase management
Who it's for
  • Developers starting their first Firebase project
  • Teams setting up new agent environments
  • DevOps engineers configuring CI/CD pipelines with Firebase
  • Anyone initializing Firebase on a fresh machine or agent

firebase-local-env-setup FAQ

What if Node.js is not installed?

Install Node.js v20 or higher using nvm (recommended to avoid permission issues) or the official installer from nodejs.org. For macOS/Linux, use nvm; for Windows, use nvm-windows or the official installer.

Can I use an older version of Node.js?

No, Node.js must be v20 or higher. If you have an older version, upgrade using your Node version manager or reinstall from nodejs.org.

What if I'm in a remote or headless environment?

Use `npx -y firebase-tools@latest login --no-localhost` instead of the standard login command to authenticate without requiring browser access.

When should I use this skill vs. firebase-basics?

Use firebase-local-env-setup only for initial one-time setup. For updating, troubleshooting, or refreshing an existing Firebase environment, use the firebase-basics skill instead.

Do I need to install the MCP server?

Yes, after completing the four verification steps, review the setup document for your specific agent (Claude Code, Cursor, etc.) to install the required skills and Firebase MCP server.

Full instructions (SKILL.md)

Source of truth, from firebase/agent-skills.


name: firebase-local-env-setup description: Bare minimum INITIAL setup for getting started with Firebase (Node.js, CLI installation, first-time login). Use ONLY for first-time setup. For updating, troubleshooting, or refreshing an existing environment, use the firebase-basics skill instead.

Firebase Local Environment Setup

This skill documents the bare minimum setup required for a full Firebase experience for the agent. Before starting to use any Firebase features, you MUST verify that each of the following steps has been completed.

1. Verify Node.js

  • Action: Run node --version.

  • Handling: Ensure Node.js is installed and the version is >= 20. If Node.js is missing or < v20, install it based on the operating system:

    Recommended: Use a Node Version Manager This avoids permission issues when installing global packages.

    For macOS or Linux:

    1. Guide the user to the official nvm repository.
    2. Request the user to manually install nvm and reply when finished. Stop and wait for the user's confirmation.
    3. Make nvm available in the current terminal session by sourcing the appropriate profile:
      # For Bash
      source ~/.bash_profile
      source ~/.bashrc
      
      # For Zsh
      source ~/.zprofile
      source ~/.zshrc
      
    4. Install Node.js:
      nvm install 24
      nvm use 24
      

    For Windows:

    1. Guide the user to download and install nvm-windows.
    2. Request the user to manually install nvm-windows and Node.js, and reply when finished. Stop and wait for the user's confirmation.
    3. After the user confirms, verify Node.js is available:
      node --version
      

    Alternative: Official Installer

    1. Guide the user to download and install the LTS version from nodejs.org.
    2. Request the user to manually install Node.js and reply when finished. Stop and wait for the user's confirmation.

2. Verify Firebase CLI

The Firebase CLI is the primary tool for interacting with Firebase services.

  • Action: Run npx -y firebase-tools@latest --version.
  • Handling: Ensure this command runs successfully and outputs a version number.

3. Verify Firebase Authentication

You must be authenticated to manage Firebase projects.

  • Action: Run npx -y firebase-tools@latest login.
  • Handling: If the environment is remote or restricted (no browser access), run npx -y firebase-tools@latest login --no-localhost instead.

4. Install Agent Skills and MCP Server

To fully manage Firebase, the agent needs specific skills and the Firebase MCP server installed. Identify the agent environment you are currently running in and follow the corresponding setup document strictly.

Read the setup document for your current agent:


CRITICAL AGENT RULE: Do NOT proceed with any other Firebase tasks until EVERY step above has been successfully verified and completed.