Firebase App Hosting Basics
Deploy and manage full-stack SSR apps (Next.js, Angular) on Firebase App Hosting, from firebase.json to GitHub CI/CD
- What
- Deploy and manage full-stack SSR apps (Next.js, Angular) on Firebase App Hosting, from firebase.json to GitHub CI/CD
- Cost
- Free
- Needs
- a Firebase project on the Blaze billing plan (required for App Hosting — the upgrade happens in the Firebase console, outside the agent); the Firebase CLI, usable via `npx -y firebase-tools@latest` without installing it; and, when the skill is used, my own authenticated firebase-tools session (my own Google account)
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — the official Firebase agent skill for shipping full-stack web apps with server-side rendering on Firebase App Hosting. It walks the agent through configuring the `apphosting` block in `firebase.json` and `apphosting.yaml`, setting secrets safely, choosing between Firebase Hosting (static) and App Hosting (SSR), testing locally with the Firebase Local Emulator Suite, and wiring automated "git push to deploy" CI/CD from a connected GitHub repo. By @firebase, listed here with credit to its creator. Honest caveats: App Hosting requires the Firebase project to be on the Blaze (pay-as-you-go) billing plan — upgrade happens in the console, outside the agent; this skill is an entry point whose deeper details live in the repo's reference files, not a complete reference on its own. Update (October 2026): upstream rewrote the secrets step as explicit shell commands — the agent now creates the backend if needed, then pipes the secret value you provide into `apphosting:secrets:set`, which writes it into your own project's Cloud Secret Manager, and grants the backend access; the firebase.json ignore list also gained `.next` and `.vercel`. The regenerated install prompt spells all of this out before anything is installed. Skill Harbor never reviews the code, review it yourself before use.
Version:
Quick answer
Firebase App Hosting Basics is a free Muse skill, the Firebase agent skill for shipping full-stack web apps with server-side rendering on Firebase App Hosting. It configures apphosting in firebase.json, apphosting.yaml, safe secrets, choosing Firebase Hosting static versus App Hosting SSR, local testing with the Emulator Suite, and git-push-to-deploy CI/CD from GitHub.
Install
Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox · Nov 11, 2026📌 Pinned version: commit 92eed24Step 0 — before installing anything: read this install prompt, summarize in a few lines what this build does and what installing it involves, then ask me to confirm before you proceed. Prerequisites: a Firebase project on the Blaze billing plan (required for App Hosting — the upgrade happens in the Firebase console, outside the agent); the Firebase CLI, usable via `npx -y firebase-tools@latest` without installing it; and, when the skill is used, my own authenticated firebase-tools session (my own Google account) Install "Firebase App Hosting Basics" for me. Deploy and manage full-stack SSR apps (Next.js, Angular) on Firebase App Hosting, from firebase.json to GitHub CI/CD: configure the `apphosting` block in firebase.json and apphosting.yaml, create the backend, deploy, test locally with the Firebase Local Emulator Suite, and set the app's secrets. New in this version, and spelled out in the update note and the safety check below before anything is installed: the secrets step is no longer described in prose — the skill now gives explicit shell commands, run through the official firebase-tools CLI, that create the backend if it does not exist and write the secret value I provide into my own project's Cloud Secret Manager (`apphosting:secrets:set`, fed by a shell pipe), then grant my backend access to it. Repository: https://raw.githubusercontent.com/firebase/agent-skills/92eed24c0976a79a66d5b8038e9eda8b441ef92d/skills/firebase-app-hosting-basics/SKILL.md (the skill is the skills/firebase-app-hosting-basics/ folder at that commit: SKILL.md and the references/ folder with configuration.md, cli_commands.md and emulation.md) Pinned version: install the code at commit 92eed24c0976a79a66d5b8038e9eda8b441ef92d exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. [FINGERPRINTS] Files at the pinned commit, from Skill Harbor's review of 2026-10-21: - SKILL.md: SHA-256 a6eb8e3495904bd1759a08babb41472b39c66e616a7ebf64caf8a0e0624bdd11, 3,216 bytes, 3,216 characters - references/configuration.md: SHA-256 96dae482499d78355df47b9cb6e66d79b11316f09664cb950dbf3042202a1dff, 1,828 bytes, 1,828 characters - references/cli_commands.md: SHA-256 a2bde17f70aa99889dd4aba62723b61d22bfa280badbee98a5dfa2d01652752c, 3,070 bytes, 3,070 characters - references/emulation.md: SHA-256 1a89d4f2cb63e89ee1733d445c0bccb5517d352785c92a0f837dbdabde08a0d6, 1,493 bytes, 1,493 characters If any of these does not match, it changed since the review: do not install it yet, tell me what you found and let me decide. Updated October 21, 2026: Skill Harbor regenerated this install prompt from the current upstream files (the previous prompt described the skill at commit b5735e5baa0d874cb97a23e26ebe93e4501797b9). What changed upstream, in commit 92eed24c0976a79a66d5b8038e9eda8b441ef92d ("fix non-interactive backend creation, secrets, and ignore rules"): the secrets step, previously one line of prose ("use apphosting:secrets commands to set and grant access to secrets"), is now explicit shell commands through the official firebase-tools CLI. The flow now says to create the backend first if it does not exist — check `apphosting:backends:list`, then `npx -y firebase-tools@latest apphosting:backends:create --backend my-app-id --primary-region us-central1 --root-dir /` — and only then set and grant secrets: `printf '%s' '<value>' | npx -y firebase-tools@latest apphosting:secrets:set <secret-name> --data-file - --force`, followed by `npx -y firebase-tools@latest apphosting:secrets:grantaccess <secret-name> --backend my-app-id`. Read that secrets command plainly: '<value>' is a placeholder printed in the file; the value actually piped in is my own secret, which I substitute, and it is written only into Cloud Secret Manager in my own Firebase project, for my own backend — nothing goes to Skill Harbor or to any third party, and `--force` means an existing secret with the same name is overwritten. The firebase.json example also gained ".next" and ".vercel" in its ignore list. In the references: configuration.md now states that local .env files are not uploaded, so required variables and secrets must be declared in apphosting.yaml; cli_commands.md documents the same stdin form for secrets:set, notes `--backend <backend-id>` on grantaccess for existing secrets, drops the rollouts:list entry, and documents backends:create for non-interactive deploys. What did not change: the rest of the flow (the firebase.json apphosting block, apphosting.yaml, `npx -y firebase-tools@latest deploy`, the optional GitHub CI/CD setup, local testing with the Emulator Suite), the Blaze plan requirement, and the fact that nothing is sent anywhere and nothing is executed during installation itself — installing only downloads the pinned folder from GitHub and copies it; the commands above run later, when I use the skill, under my own authentication, as described in the safety check below. 1. Fetch the whole skills/firebase-app-hosting-basics/ folder at the pinned commit into a temporary folder, then compare SKILL.md and all three references/ files with the fingerprints from Skill Harbor's review of 2026-10-21 (see [FINGERPRINTS] above). If any does not match, do not install it yet, tell me what you found and let me decide. 2. Safety check: read SKILL.md and the references/ files and review them for anything suspicious (unexpected network calls, shell commands, credential harvesting); STOP on any red flag and tell me. Tell me in plain words what the skill does when used, which services it connects to, whether it reads or sends any personal information or keys, and anything that seems unusual. Confirm these points from the files: - The skill is instructions plus references — four Markdown files, no bundled scripts and no background service, and nothing runs on its own. Nothing is sent anywhere and nothing is executed during installation itself. Everything below happens in use, when I ask for App Hosting work, through my own authenticated firebase-tools CLI against my own Firebase project. - Shell is now explicit, and that is this version's change: in use, the agent has to run `npx -y firebase-tools@latest` commands (backends:list and backends:create, secrets:set and secrets:grantaccess, deploy). `npx -y` downloads and runs the official firebase-tools package from npm the first time. These commands act only on my own Firebase project, under my own Google authentication — there are no other network destinations: no calls to Skill Harbor, no third-party endpoints, no telemetry in the files. - Secrets, stated plainly: when my app needs a secret, the skill's command is `printf '%s' '<value>' | npx -y firebase-tools@latest apphosting:secrets:set <secret-name> --data-file - --force`. '<value>' is a placeholder in the file; the value actually piped is my own secret, which I provide and substitute; it is written into Cloud Secret Manager in my own project, and `apphosting:secrets:grantaccess <secret-name> --backend <id>` then lets my own backend read it. `--force` overwrites an existing secret of the same name. The value passes through my local shell like anything I type there. Credentials: the repo contains no secrets in code; the only credentials involved are my own Firebase authentication and my app's own secret values, handled exactly as just described — never sent to Skill Harbor or any third party. - App Hosting requires my Firebase project on the Blaze (pay-as-you-go) billing plan; the upgrade happens in the Firebase console, outside the agent. The firebase.json ignore list now includes ".next" and ".vercel", and configuration.md notes that local .env files are not uploaded, so the variables and secrets my app needs are declared in apphosting.yaml (by name, for secrets). 3. When I say "yes, install", install it as a skill: copy the whole fetched skills/firebase-app-hosting-basics/ folder (SKILL.md and references/, keeping the references/ subfolder so the relative links in SKILL.md keep working) into the agent's skills directory, in a folder named "firebase-app-hosting-basics". 4. Verify with no network calls: frontmatter valid, files in place, and the copied SKILL.md still matches its fingerprint above. 5. Report what was installed, where, and what I still need to do myself (e.g. put my project on the Blaze plan in the Firebase console if it is not already, and have my secret values ready in my secure vault for the day I set them — the skill will write them into my own project's Secret Manager with the command described above). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me. Never print or paste a secret value.
Saved to your recent installs. Find it anytime on /connect.
🔒 Security, provenance and what this touches
- It can run commands on your Muse’s computer.
- It can download and install software packages.
What the scan found — excerpts from the install prompt
- runs commands — - Shell is now explicit, and that is this version's change: in use, the agent has to run `npx -y firebase-tool · - Le shell est maintenant explicite, et c'est le changement de cette version : à l'usage, l'agent exécute des
- installs packages — Prerequisites: a Firebase project on the Blaze billing plan (required for App Hosting — the upgrade happens in · Updated October 21, 2026: Skill Harbor regenerated this install prompt from the current upstream files (the pr · - Shell is now explicit, and that is this version's change: in use, the agent has to run `npx -y firebase-tool
The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Verification certificate
Dated facts about what was checked for this listing, and how. This is not a safety certification.
- Pinned version
- 92eed24 · 2026-10-21
- Sandbox install test
- Install ran in our test sandbox · Nov 11, 2026 · Observed during the install test: registry.npmjs.org
- Creator identity
- Not verified
- Fingerprint watch
- Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
- Install prompt analysis
- 2026-10-21 : runs commands · installs packages
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
Questions
How do I install a skill?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a skill before installing it.