firebase
Skill38 starsChanged 8 months agoMITView on GitHub
Manage Firebase projects, Firestore, Auth users and Hosting via REST API
9 other projects use a version of this.
Adopted by
Most recently taken up by
- darknecrocities/SkillBuildertheir own version, first seen Nov 1, 2026
- xfstudio/skillstheir own version, first seen Oct 13, 2026
- G1Joshi/Agent-Skillstheir own version, first seen Oct 13, 2026
- alinaqi/claude-bootstraptheir own version, first seen Oct 8, 2026
- muxammadmamajonov/dot-claudetheir own version, first seen Jul 6, 2026
- alinaqi/maggytheir own version, first seen Jun 12, 2026
Used with
Projects with it also use react-native, gcp and 2 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
VercelSkillreact-native
React Native renderer for json-render that turns JSON specs into native mobile UIs. Use when working with @json-render/react-native, building React Native UIs from JSON, creating mobile component catalogs, or rendering AI-generated specs on mobile.
Also in 4 projects that use this
ffsshhttiikkSkillgcp
Google Cloud Platform services and best practices
Also in 3 projects that use this
ffsshhttiikkSkillflutter
Flutter cross-platform framework
Also in 3 projects that use this
0xSeroSkillsecurity
Also in 4 projects that use this
Other versions9 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 9
- alinaqi/maggy★ 711same name
- alinaqi/claude-bootstrap★ 708same name
- Fandry96/k3-agentic-skills★ 27same name
- G1Joshi/Agent-Skills★ 15same name
- darknecrocities/SkillBuilder★ 13same name
- xfstudio/skills★ 9same name
- ai4brands-design/claude-skills★ 2same name
- tuannv14/claude-team-toolkit★ 1same name
- muxammadmamajonov/dot-claude★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository36 other files it gives its agents.
- abacatepaySkill
- appsignalSkill
- clickupSkill
- cloudflareSkill
- cloudinarySkill
- datadogSkill
- digitaloceanSkill
- discordSkill
- flyioSkill
- google-sheetsSkill
- herokuSkill
- honeybadgerSkill
- hostingerSkill
- hubspotSkill
- intercomSkill
- jiraSkill
- linearSkill
- mercadopagoSkill
- n8nSkill
- notionSkill
- openaiSkill
- planetscaleSkill
- posthogSkill
- railwaySkill
- resendSkill
- rewriteSkill
- sentrySkill
- shopifySkill
- slackSkill
- stripeSkill
- supabaseSkill
- trelloSkill
- twilioSkill
- vercelSkill
- xSkill
- zendeskSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 2 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 9 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 34
If the output is OK, proceed to the Flow section.
- Very specific: line 36
If the output is SETUP_NEEDED, guide the user step by step.
- Distinctive: line 61
If the script outputs an error, the file is invalid.
- Distinctive: line 96
Before running, ask: "This will list Firebase Auth users which contains personal information (emails, phone numbers).
“Common” is measured: kept by at least 6 in 10 of the 9 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
/firebase
Connect to Firebase and Google Cloud APIs to manage projects, Firestore databases, Authentication users and Hosting deployments. Pure Ruby, zero gems — stdlib only (json, net/http, uri, openssl, base64, fileutils).
Structure
scripts/
├── auth.rb # JWT-based OAuth2 + firebase_request helper (required by all scripts)
├── check_setup.rb # Check if service account JSON exists (outputs OK or SETUP_NEEDED)
├── save_token.rb # Copy a service account JSON file to the config directory
├── projects.rb # List Firebase projects
├── firestore_collections.rb # List top-level Firestore collections
├── firestore_documents.rb # List documents in a Firestore collection
├── firestore_document.rb # Get a single Firestore document
├── auth_users.rb # List Firebase Auth users (requires confirmation — contains PII)
├── hosting_sites.rb # List Hosting sites for a project
└── hosting_releases.rb # List releases for a Hosting siteSetup (check before using)
ruby ~/.claude/skills/firebase/scripts/check_setup.rbIf the output is OK, proceed to the Flow section.
If the output is SETUP_NEEDED, guide the user step by step. Present ONE step at a time, wait for the user to confirm before moving to the next.
Step 1 — Ask the user to create a service account key:
You need a Google Cloud service account key with Firebase access.
- Go to the Google Cloud Console > IAM & Admin > Service Accounts: https://console.cloud.google.com/iam-admin/serviceaccounts
- Select your project (or create one).
- Click Create Service Account. Give it a name like
hitank-firebase.- Grant it the Editor role (or more restrictive roles:
Firebase Admin,Cloud Datastore User,Firebase Hosting Admin).- Click on the created service account, go to Keys > Add Key > Create new key > JSON.
- A
.jsonfile will be downloaded. Tell me the path to that file.
Step 2 — When the user provides the path to the JSON key file, save it:
ruby ~/.claude/skills/firebase/scripts/save_token.rb '/path/to/downloaded-key.json'If the script outputs an error, the file is invalid. Ask the user to double-check and try again.
If setup is not complete, DO NOT proceed to the Flow. Complete all steps first.
Flow
The argument $ARGUMENTS may contain a Firebase project ID.
Step 1: List projects
ruby ~/.claude/skills/firebase/scripts/projects.rbPresent the projects to the user. If $ARGUMENTS matches a project ID, use that project. Otherwise ask which project to work with.
Step 2: Actions
List top-level Firestore collections (documents at root):
ruby ~/.claude/skills/firebase/scripts/firestore_collections.rb PROJECT_IDList documents in a Firestore collection:
ruby ~/.claude/skills/firebase/scripts/firestore_documents.rb PROJECT_ID COLLECTION_NAMEGet a single Firestore document:
ruby ~/.claude/skills/firebase/scripts/firestore_document.rb PROJECT_ID COLLECTION_NAME DOCUMENT_IDList Firebase Auth users (requires user confirmation — this returns PII):
Before running, ask: "This will list Firebase Auth users which contains personal information (emails, phone numbers). Do you want to proceed?" Only execute after a "yes".
ruby ~/.claude/skills/firebase/scripts/auth_users.rb PROJECT_IDList Hosting sites:
ruby ~/.claude/skills/firebase/scripts/hosting_sites.rb PROJECT_IDList Hosting releases:
ruby ~/.claude/skills/firebase/scripts/hosting_releases.rb PROJECT_ID SITE_NAMENotes
- Pure Ruby, zero gems — stdlib only (json, net/http, uri, openssl, base64, fileutils)
- Auth via Google OAuth2 using a service account JSON key and JWT (RS256)
- Service account key file:
~/.config/firebase/service_account.json(outside the repo, never commit) - Access token cached at
~/.config/firebase/access_tokenwith expiry check - The JWT is signed locally using the service account's private key, then exchanged for an access token via
https://oauth2.googleapis.com/token - Listing Auth users requires explicit user confirmation because it returns PII
- OAuth2 scope:
https://www.googleapis.com/auth/cloud-platform https://www.googleapis.com/auth/firebase
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

