agentsclimarketplace
Sign in

Firebase basics

Skill JordanChoo/acfs-agent-skills/firebase-basics

Bootstrap and product reference for any Firebase project — CLI login, project selection, MCP wiring, and authoritative Firebase product docs (core concepts, CLI, client/admin SDKs, IaC, IAM/security). Use at the start of work on a Firebase repo, when you need to look up a Firebase product concept, or when setting up the Firebase MCP server. For deploy/rules/secrets discipline see `firebase-stack`. For emulator-backed testing see `firebase-emulator-e2e-harness`.From its SKILL.md

Install
npx -y skills add JordanChoo/acfs-agent-skills --skill firebase-basics

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

5.3 KB, ~1.1k tokens by cl100k_base, as published. Nobody here has run it

firebase-basics

Bootstrap and product-reference layer for Firebase work. This skill is the entry point: it covers logging into the Firebase CLI, picking an active project, wiring the Firebase MCP server, and points to authoritative product docs under references/.

This skill is intentionally generic and non-opinionated. For environment-specific discipline (deploy gates, rules tests, index hygiene, secret rotation), load firebase-stack. For emulator-backed E2E harness work, load firebase-emulator-e2e-harness.

Triggers

Load this skill when:

  • Starting work on a repo with firebase.json / .firebaserc and no Firebase context yet
  • User asks a Firebase product question (what is X, how is it priced, what regions, what SDK)
  • Setting up or repairing the Firebase MCP server
  • A teammate-handoff repo has no scripts/ wrapper and you need the bare-CLI baseline

If the repo already has project-specific scripts and firebase-stack triggers fire, prefer firebase-stack.

Bootstrap

1. Verify the CLI is reachable

npx -y firebase-tools@latest --version

Always invoke as npx -y firebase-tools@latest <cmd> rather than bare firebase — this pins to the latest published CLI and avoids "works on my machine" version drift. (Yes, even in Bun-default repos; firebase-tools is npm-distributed.)

2. Log in (interactive)

npx -y firebase-tools@latest login

The login flow opens a browser. If you're an agent in a non-interactive shell, stop and ask the user to run this themselves — do not attempt to script around the browser flow.

3. Pick an active project

npx -y firebase-tools@latest use

  • If output is Active Project: <PROJECT_ID>, proceed.

  • If no active project, ask the user for an existing project ID and run:

    npx -y firebase-tools@latest use --add <PROJECT_ID>

  • If the user has no project yet, create one (only with explicit user approval — project creation is billable scope):

    npx -y firebase-tools@latest projects:create <PROJECT_ID> --display-name <DISPLAY_NAME>

4. Wire the Firebase MCP server (optional)

The Firebase CLI ships a local MCP server. To make it available to this agent, see references/mcp-usage.md. Detect first — many setups already have a firebase entry in their MCP config and re-adding it would overwrite siblings.

Reference docs

Authoritative Firebase product references, mirrored from google/skills firebase-basics. Read on demand:

Extension: Google's full skill bundle

google/skills firebase-basics also instructs the agent to install Google's broader Firebase skill set:

npx -y skills add firebase/agent-skills -y

That bundle adds skills for firebase-firestore, firebase-hosting-basics, firebase-auth-basics, firebase-app-hosting-basics, firebase-data-connect-basics, firebase-ai-logic-basics, firebase-security-rules-auditor, and Genkit (developing-genkit-{js,go,dart}).

This is opt-in here, not mandatory. Reasons to skip it: those skills are generic and don't know about this user's environment conventions (emulator-first testing in firebase-emulator-e2e-harness, project-script discipline in firebase-stack, beads single-writer policy, Bun defaults). Reasons to run it: you're starting a brand-new Firebase project that needs Firestore data-modeling or Genkit guidance and the existing skills don't cover it. Ask the user before installing.

See also

  • firebase-stack — environment-specific discipline: deploy targets, rules-test gates, index/query consistency, secret rotation, infra provisioning scripts
  • firebase-emulator-e2e-harness — deterministic emulator harnesses for Playwright/Vitest E2E

Attribution

references/*.md are mirrored from google/skills (Apache 2.0 / per repo LICENSE) and may diverge from upstream over time. Re-fetch from https://raw.githubusercontent.com/google/skills/main/skills/cloud/firebase-basics/references/<file> to refresh.

What ships with it: 6 files

11.8 KB alongside SKILL.md

references/

Gives 0 of the 12 instructions most mcp tooling skills give in ~1.1k tokens

Counted across 638 of the 750 authors here whose files we hold, read 2026-08-07

  • Create ten complex or independent read-only evaluation questionsin 69 of 638, across 15 files
  • Test servers using MCP Inspectorin 61 of 638, across 19 files
  • Provide actionable error messages with specific next stepsin 54 of 638, across 12 files
  • Prioritize comprehensive API coverage over specific workflows or workflow toolsin 54 of 638, across 12 files
  • Use TypeScript and Streamable HTTP for remote servers or clientsin 54 of 638, across 8 files
  • Define structured output schemas where possiblein 50 of 638, across 8 files
  • Use Zod or Pydantic for input schemasin 47 of 638, across 5 files
  • Fetch MCP specification pages with markdown suffixin 46 of 638, across 4 files
  • Load framework documentation using WebFetchin 45 of 638, across 3 files
  • Verify each evaluation answer independentlyin 45 of 638, across 3 files
  • Implement API client with authentication and paginationin 45 of 638, across 3 files
  • Define input schemas with validationin 27 of 638, across 9 files

Said here and by no other author read

  • Invoke CLI as npx firebase-tools@latest
  • Log in using the interactive command
  • Ask user to run login in non-interactive shells
  • Select active project or ask for project ID
  • Ask explicit approval before creating billable projects
  • Detect existing MCP config before wiring Firebase MCP

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 326,764. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.