[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AH8D3JK7BFPPEPTFMFBACF":3,"skill-same:01M7AH8D3JK7BFPPEPTFMFBACF":54},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":13,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":29,"install":30,"resources":43},"01M7AH8D3JK7BFPPEPTFMFBACF","firebase-remote-config-basics",null,"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.","navalkashyapp\u002Fcareer-manager","navalkashyapp","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F262655051?v=4","01M7AH780EACQ1NGMWVZFY45CW","01M7AH781J8K4KTV64YH3G31MK",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fnavalkashyapp\u002Fcareer-manager\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ffirebase_remote_config_basics\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: firebase-remote-config-basics\ndescription: 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.\ncompatibility: This skill is best used with the Firebase CLI, but does not require it. Firebase CLI can be accessed through `npx -y firebase-tools@latest`.\n---\n\n# Remote Config\n\nThis skill provides a complete guide for getting started with Remote Config on\nAndroid or iOS. Remote Config allows you to change the behavior and appearance\nof your app without publishing an app update by maintaining a cloud-based\nconfiguration template.\n\n## Prerequisites\n\nProvisioning Remote Config requires both a Firebase project and a Firebase app,\neither Android or iOS. To manage the Remote Config template and conditions via\nthe command line, use the Firebase CLI. See the `firebase-basics` skill for\nreferences on project initialization.\n\n## Troubleshooting Execution\n\n### Handling npx 403 Forbidden Errors\n\nIf `npx -y firebase-tools@latest` fails due to registry permissions (403 error):\n\n1. **Inform the user**: \"I am unable to fetch the latest Firebase tools via npx\n   due to a registry error.\"\n1. **Fallback**: Attempt to use the local `firebase` command directly if the\n   user confirms it is installed globally (`npm install -g firebase-tools`).\n\n### Handling Project Context Issues\n\nIf a command fails because \"no active project is selected\":\n\n1. **Check login**: Run `npx -y firebase-tools@latest login:list`.\n1. **Prompt for ID**: If logged in but no project is active, ask the user:\n   \"Please provide your Firebase Project ID to proceed.\"\n1. **Use Flag**: Append `--project \u003CPROJECT_ID>` to every subsequent command.\n\n## SDK Setup\n\nTo learn how to set up Remote Config in your application code, choose your\nplatform:\n\n- **Android**: [android_setup.md](references\u002Fandroid_setup.md)\n- **iOS**: [ios_setup.md](references\u002Fios_setup.md)\n\n## Best Practices and Template Management\n\nFollow these guidelines and use the associated CLI tools to ensure efficient and\nsafe use of Remote Config.\n\n### Fetching Strategies\n\nTo optimize app performance and user experience, follow these recommended\npatterns (see\n[Loading Strategies](https:\u002F\u002Ffirebase.google.com\u002Fdocs\u002Fremote-config\u002Floading)):\n\n- **Load new values for next startup**: The most effective pattern is to\n  activate previously fetched values immediately on startup and fetch new values\n  in the background to be used next time. This minimizes user wait time.\n- **Real-time Updates**: Use the SDK's real-time listener to update the app\n  instantly without a refresh when server-side configuration changes.\n\n### Template Management via CLI\n\nUse the following commands to manage your Remote Config template and version\nhistory through the terminal:\n\n### Template Management via CLI\n\nUse the following commands to manage your Remote Config template and version\nhistory through the terminal:\n\n- **Get current template**: Save the remote template to a local JSON file for\n  auditing or modification.\n\n  ```bash\n  npx -y firebase-tools@latest remoteconfig:get -o remote_config.json\n  ```\n\n- **Autonomous Editing & Discovery** : Modify the local `remote_config.json`\n  directly. Determine the correct signal (e.g., device.country or percent) and\n  update the \"conditions\" array and \"parameters\" map accordingly.\n\n- **MANDATORY: User Review and Verification** : STOP and ask the user to verify\n  your changes before proceeding to deployment.\n\n  - Action: Inform the user: \"I have prepared the changes in remote_config.json.\n    Please review the file for accuracy. Once you are satisfied, tell me to\n    'deploy' to make the changes live.\"\n\n- **Deployment Orchestration** : To push changes, you must ensure the\n  environment is configured for deployment.\n\n  - Config Mapping: If a firebase.json file is missing, create one to map the\n    local JSON to the Remote Config service:\n\n  ```json\n    { \"remoteconfig\": { \"template\": \"remote_config.json\" } }\n  ```\n\n  - Deploy: Execute the partial deployment command\n    ```bash\n    npx -y firebase-tools@latest deploy --only remoteconfig\n    ```\n\n- **Verification**: After deployment, verify the update by listing the version\n  history.\n\n  ```bash\n  npx -y firebase-tools@latest remoteconfig:versions:list\n  ```\n\nThe SDK provides a number of features to make your application dynamic and\nresponsive to user segments.\n\n- **Set In-App Defaults**: Define baseline values to ensure the app functions\n  offline or before the first fetch.\n- **Fetch and Activate**: Retrieve values from the Firebase backend and apply\n  them to the local UI\u002FLogic.\n- **Template Management**: Use the Firebase CLI to version-control, get, and\n  deploy your config JSON files.\n","# Remote Config\n\nThis skill provides a complete guide for getting started with Remote Config on\nAndroid or iOS. Remote Config allows you to change the behavior and appearance\nof your app without publishing an app update by maintaining a cloud-based\nconfiguration template.\n\n## Prerequisites\n\nProvisioning Remote Config requires both a Firebase project and a Firebase app,\neither Android or iOS. To manage the Remote Config template and conditions via\nthe command line, use the Firebase CLI. See the `firebase-basics` skill for\nreferences on project initialization.\n\n## Troubleshooting Execution\n\n### Handling npx 403 Forbidden Errors\n\nIf `npx -y firebase-tools@latest` fails due to registry permissions (403 error):\n\n1. **Inform the user**: \"I am unable to fetch the latest Firebase tools via npx\n   due to a registry error.\"\n1. **Fallback**: Attempt to use the local `firebase` command directly if the\n   user confirms it is installed globally (`npm install -g firebase-tools`).\n\n### Handling Project Context Issues\n\nIf a command fails because \"no active project is selected\":\n\n1. **Check login**: Run `npx -y firebase-tools@latest login:list`.\n1. **Prompt for ID**: If logged in but no project is active, ask the user:\n   \"Please provide your Firebase Project ID to proceed.\"\n1. **Use Flag**: Append `--project \u003CPROJECT_ID>` to every subsequent command.\n\n## SDK Setup\n\nTo learn how to set up Remote Config in your application code, choose your\nplatform:\n\n- **Android**: [android_setup.md](references\u002Fandroid_setup.md)\n- **iOS**: [ios_setup.md](references\u002Fios_setup.md)\n\n## Best Practices and Template Management\n\nFollow these guidelines and use the associated CLI tools to ensure efficient and\nsafe use of Remote Config.\n\n### Fetching Strategies\n\nTo optimize app performance and user experience, follow these recommended\npatterns (see\n[Loading Strategies](https:\u002F\u002Ffirebase.google.com\u002Fdocs\u002Fremote-config\u002Floading)):\n\n- **Load new values for next startup**: The most effective pattern is to\n  activate previously fetched values immediately on startup and fetch new values\n  in the background to be used next time. This minimizes user wait time.\n- **Real-time Updates**: Use the SDK's real-time listener to update the app\n  instantly without a refresh when server-side configuration changes.\n\n### Template Management via CLI\n\nUse the following commands to manage your Remote Config template and version\nhistory through the terminal:\n\n### Template Management via CLI\n\nUse the following commands to manage your Remote Config template and version\nhistory through the terminal:\n\n- **Get current template**: Save the remote template to a local JSON file for\n  auditing or modification.\n\n  ```bash\n  npx -y firebase-tools@latest remoteconfig:get -o remote_config.json\n  ```\n\n- **Autonomous Editing & Discovery** : Modify the local `remote_config.json`\n  directly. Determine the correct signal (e.g., device.country or percent) and\n  update the \"conditions\" array and \"parameters\" map accordingly.\n\n- **MANDATORY: User Review and Verification** : STOP and ask the user to verify\n  your changes before proceeding to deployment.\n\n  - Action: Inform the user: \"I have prepared the changes in remote_config.json.\n    Please review the file for accuracy. Once you are satisfied, tell me to\n    'deploy' to make the changes live.\"\n\n- **Deployment Orchestration** : To push changes, you must ensure the\n  environment is configured for deployment.\n\n  - Config Mapping: If a firebase.json file is missing, create one to map the\n    local JSON to the Remote Config service:\n\n  ```json\n    { \"remoteconfig\": { \"template\": \"remote_config.json\" } }\n  ```\n\n  - Deploy: Execute the partial deployment command\n    ```bash\n    npx -y firebase-tools@latest deploy --only remoteconfig\n    ```\n\n- **Verification**: After deployment, verify the update by listing the version\n  history.\n\n  ```bash\n  npx -y firebase-tools@latest remoteconfig:versions:list\n  ```\n\nThe SDK provides a number of features to make your application dynamic and\nresponsive to user segments.\n\n- **Set In-App Defaults**: Define baseline values to ensure the app functions\n  offline or before the first fetch.\n- **Fetch and Activate**: Retrieve values from the Firebase backend and apply\n  them to the local UI\u002FLogic.\n- **Template Management**: Use the Firebase CLI to version-control, get, and\n  deploy your config JSON files.\n",{"name":5,"description":7,"compatibility":23},"This skill is best used with the Firebase CLI, but does not require it. Firebase CLI can be accessed through `npx -y firebase-tools@latest`.","main","2692e7fec5c1e4033e71ae062ad6a3c622650a2c",".agents\u002Fskills\u002Ffirebase_remote_config_basics","https:\u002F\u002Fgithub.com\u002Fnavalkashyapp\u002Fcareer-manager","https:\u002F\u002Fgithub.com\u002Fnavalkashyapp","2026-11-13 00:25:38",{"source":8,"skillName":5,"commands":31,"prompt":41,"zipAvailable":42},[32,35,38],{"tool":33,"command":34},"npx","npx skills add navalkashyapp\u002Fcareer-manager --skill firebase-remote-config-basics",{"tool":36,"command":37},"bunx","bunx skills add navalkashyapp\u002Fcareer-manager --skill firebase-remote-config-basics",{"tool":39,"command":40},"pnpm","pnpm dlx skills add navalkashyapp\u002Fcareer-manager --skill firebase-remote-config-basics","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fnavalkashyapp\u002Fcareer-manager\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ffirebase_remote_config_basics\u002FSKILL.md",true,[44,50],{"path":45,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":48,"sourceHtmlUrl":49},"references\u002Fandroid_setup.md","REFERENCE","参考文档",3484,"https:\u002F\u002Fgithub.com\u002Fnavalkashyapp\u002Fcareer-manager\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ffirebase_remote_config_basics\u002Freferences\u002Fandroid_setup.md",{"path":51,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":52,"sourceHtmlUrl":53},"references\u002Fios_setup.md",2678,"https:\u002F\u002Fgithub.com\u002Fnavalkashyapp\u002Fcareer-manager\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ffirebase_remote_config_basics\u002Freferences\u002Fios_setup.md",[55,63,70,77,85,91],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":59,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":18},"01M7AH9MM5XWGNSJA5J1Z308QA","career-ops-plugin-notion","How to mirror the career-ops tracker to a Notion database and read records back as job leads.","MIT","https:\u002F\u002Fgithub.com\u002Fnavalkashyapp\u002Fcareer-manager\u002Fblob\u002Fmain\u002Fcareer-ops\u002Fplugins\u002Fnotion\u002Fskill.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":59,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":18},"01M7AH9HJHKW065CFTKYZSPA45","career-ops-plugin-gmail","How to pull job leads from a Gmail label into the career-ops pipeline.","https:\u002F\u002Fgithub.com\u002Fnavalkashyapp\u002Fcareer-manager\u002Fblob\u002Fmain\u002Fcareer-ops\u002Fplugins\u002Fgmail\u002Fskill.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":59,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":18},"01M7AH9FSXMBR88B8R13QQJ9RQ","career-ops-plugin-apify","How to scan a job source through an Apify actor as a keyed provider.","https:\u002F\u002Fgithub.com\u002Fnavalkashyapp\u002Fcareer-manager\u002Fblob\u002Fmain\u002Fcareer-ops\u002Fplugins\u002Fapify\u002Fskill.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":59,"licenseFileUrl":81,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":18},"01M7AH9CQGE2QRNDY9H8R1V9CA","career-ops-plugin-{{NAME}}","How to use the {{NAME}} plugin and the data it produces.","https:\u002F\u002Fgithub.com\u002Fnavalkashyapp\u002Fcareer-manager\u002Fblob\u002Fmain\u002Fcareer-ops\u002Fplugins\u002F_template\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fnavalkashyapp\u002Fcareer-manager\u002Fblob\u002Fmain\u002Fcareer-ops\u002Fplugins\u002F_template\u002Fskill.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":18},"01M7AH9B90WAXH4KBBV6MM9HBR","career-ops","https:\u002F\u002Fgithub.com\u002Fnavalkashyapp\u002Fcareer-manager\u002Fblob\u002Fmain\u002Fcareer-ops\u002F.qwen\u002Fskills\u002Fcareer-ops\u002FSKILL.md",[],[],{"skillNo":92,"name":87,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":18},"01M7AH98FTERMDZT7AN7W37A94","https:\u002F\u002Fgithub.com\u002Fnavalkashyapp\u002Fcareer-manager\u002Fblob\u002Fmain\u002Fcareer-ops\u002F.opencode\u002Fskills\u002Fcareer-ops\u002FSKILL.md",[],[]]