firebase-remote-config-basics
byfirebase· 35 skills
Comprehensive guide for Firebase Remote Config, including template management and SDK usage. Use this skill when the user needs help setting up Remote Config, managing feature flags, or updating app behavior dynamically.
How to install firebase-remote-config-basics?
firebase/agent-skills/firebase-remote-config-basics
$npx -y skills add firebase/agent-skills --skill firebase-remote-config-basicsInstalls into the current project.
›Prefer a prompt? Paste this to your agent
Run `npx skills use "https://github.com/firebase/agent-skills" --skill "firebase/agent-skills/firebase-remote-config-basics"` and follow the generated skill instructions now. Read its complete output, redirecting it to a temporary file first if necessary. Resolve relative paths from the supporting-files directory it provides.
Use the skills in "https://github.com/firebase/agent-skills" that are relevant to the current task. Run `npx skills add "https://github.com/firebase/agent-skills"` and select the relevant skills, then follow their instructions.
SKILL.md
| 1 | # Remote Config |
| 2 | |
| 3 | This skill provides a complete guide for getting started with Remote Config on |
| 4 | Android or iOS. Remote Config allows you to change the behavior and appearance |
| 5 | of your app without publishing an app update by maintaining a cloud-based |
| 6 | configuration template. |
| 7 | |
| 8 | ## Prerequisites |
| 9 | |
| 10 | Provisioning Remote Config requires both a Firebase project and a Firebase app, |
| 11 | either Android or iOS. To manage the Remote Config template and conditions via |
| 12 | the command line, use the Firebase CLI. See the `firebase-basics` skill for |
| 13 | references on project initialization. |
| 14 | |
| 15 | ## Troubleshooting Execution |
| 16 | |
| 17 | ### Handling npx 403 Forbidden Errors |
| 18 | |
| 19 | If `npx -y firebase-tools@latest` fails due to registry permissions (403 error): |
| 20 | |
| 21 | 1. **Inform the user**: "I am unable to fetch the latest Firebase tools via npx |
| 22 | due to a registry error." |
| 23 | 1. **Fallback**: Attempt to use the local `firebase` command directly if the |
| 24 | user confirms it is installed globally (`npm install -g firebase-tools`). |
| 25 | |
| 26 | ### Handling Project Context Issues |
| 27 | |
| 28 | If a command fails because "no active project is selected": |
| 29 | |
| 30 | 1. **Check login**: Run `npx -y firebase-tools@latest login:list`. |
| 31 | 1. **Prompt for ID**: If logged in but no project is active, ask the user: |
| 32 | "Please provide your Firebase Project ID to proceed." |
| 33 | 1. **Use Flag**: Append `--project <PROJECT_ID>` to every subsequent command. |
| 34 | |
| 35 | ## SDK Setup |
| 36 | |
| 37 | To learn how to set up Remote Config in your application code, choose your |
| 38 | platform: |
| 39 | |
| 40 | - **Android**: [android_setup.md](references/android_setup.md) |
| 41 | - **iOS**: [ios_setup.md](references/ios_setup.md) |
| 42 | |
| 43 | ## Best Practices and Template Management |
| 44 | |
| 45 | Follow these guidelines and use the associated CLI tools to ensure efficient and |
| 46 | safe use of Remote Config. |
| 47 | |
| 48 | ### Fetching Strategies |
| 49 | |
| 50 | To optimize app performance and user experience, follow these recommended |
| 51 | patterns (see |
| 52 | [Loading Strategies](https://firebase.google.com/docs/remote-config/loading)): |
| 53 | |
| 54 | - **Load new values for next startup**: The most effective pattern is to |
| 55 | activate previously fetched values immediately on startup and fetch new values |
| 56 | in the background to be used next time. This minimizes user wait time. |
| 57 | - **Real-time Updates**: Use the SDK's real-time listener to update the app |
| 58 | instantly without a refresh when server-side configuration changes. |
| 59 | |
| 60 | ### Template Management via CLI |
| 61 | |
| 62 | Use the following commands to manage your Remote Config template and version |
| 63 | history through the terminal: |
| 64 | |
| 65 | ### Template Management via CLI |
| 66 | |
| 67 | Use the following commands to manage your Remote Config template and version |
| 68 | history through the terminal: |
| 69 | |
| 70 | - **Get current template**: Save the remote template to a local JSON file for |
| 71 | auditing or modification. |
| 72 | |
| 73 | ```bash |
| 74 | npx -y firebase-tools@latest remoteconfig:get -o remote_config.json |
| 75 | ``` |
| 76 | |
| 77 | - **Autonomous Editing & Discovery** : Modify the local `remote_config.json` |
| 78 | directly. Determine the correct signal (e.g., device.country or percent) and |
| 79 | update the "conditions" array and "parameters" map accordingly. |
| 80 | |
| 81 | - **MANDATORY: User Review and Verification** : STOP and ask the user to verify |
| 82 | your changes before proceeding to deployment. |
| 83 | |
| 84 | - Action: Inform the user: "I have prepared the changes in remote_config.json. |
| 85 | Please review the file for accuracy. Once you are satisfied, tell me to |
| 86 | 'deploy' to make the changes live." |
| 87 | |
| 88 | - **Deployment Orchestration** : To push changes, you must ensure the |
| 89 | environment is configured for deployment. |
| 90 | |
| 91 | - Config Mapping: If a firebase.json file is missing, create one to map the |
| 92 | local JSON to the Remote Config service: |
| 93 | |
| 94 | ```json |
| 95 | { "remoteconfig": { "template": "remote_config.json" } } |
| 96 | ``` |
| 97 | |
| 98 | - Deploy: Execute the partial deployment command |
| 99 | ```bash |
| 100 | npx -y firebase-tools@latest deploy --only remoteconfig |
| 101 | ``` |
| 102 | |
| 103 | - **Verification**: After deployment, verify the update by listing the version |
| 104 | history. |
| 105 | |
| 106 | ```bash |
| 107 | npx -y firebase-tools@latest remoteconfig:versions:list |
| 108 | ``` |
| 109 | |
| 110 | The SDK provides a number of features to make your application dynamic and |
| 111 | responsive to user segments. |
| 112 | |
| 113 | - **Set In-App Defaults**: Define baseline values to ensure the app functions |
| 114 | offline or before the first fetch. |
| 115 | - **Fetch and Activate**: Retrieve values from the Firebase backend and apply |
| 116 | them to the local UI/Logic. |
| 117 | - **Template Management**: Use the Firebase CLI to version-control, get, and |
| 118 | deploy your config JSON files. |
Related
6 picksType
- setup-matt-pocock-skillsConfigure this repo for the engineering skills — set up its issue tracker, triage label vocabulary, and domain doc layout.Jul 2026
- microsoft-foundryDeploy, evaluate, fine-tune, and manage Foundry agents end-to-end with azd: hosted agent scaffold/run/deploy, prompt agent create, batch eval, continuous eval,…Jul 2026
- azure-deployExecute Azure deployments for ALREADY-PREPARED applications that have existing .azure/deployment-plan.md and infrastructure files.Jul 2026
- azure-preparePrepare azd-based Azure projects for deployment: generates azure.yaml, infrastructure (Bicep/Terraform), and Dockerfiles for the Azure Developer CLI (azd)…Jul 2026
- azure-validatePre-deployment validation for Azure readiness. Run deep checks on configuration, infrastructure (Bicep or Terraform), RBAC role assignments, managed identity…Jul 2026
- azure-aigatewayConfigure Azure API Management as an AI Gateway for AI models, MCP tools, and agents.Jul 2026
