firebase-rules-generator
Generate firebase rules generator operations. Auto-activating skill for GCP Skills. Triggers on: firebase rules generator, firebase rules generator Part of the GCP Skills skill category. Use when working with firebase rules generator functionality. Trigger with phrases like "firebase rules generator", "firebase generator", "firebase". '
npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill firebase-rules-generator --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Firebase Rules Generator ## Overview This skill provides automated assistance for firebase rules generator tasks within the GCP Skills domain. ## When to Use This skill activates automatically when you: - Mention "firebase rules generator" in your request - Ask about firebase rules generator patterns or best practices - Need help with google cloud platform skills covering compute, storage, bigqu
What does the firebase-rules-generator skill do?
Generate firebase rules generator operations. Auto-activating skill for GCP Skills. Triggers on: firebase rules generator, firebase rules generator Part of the GCP Skills skill category. Use when working with firebase rules generator functionality. Trigger with phrases like "firebase rules generator", "firebase generator", "firebase". '
How do I install it?
Run `npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill firebase-rules-generator --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From jeremylongshore/claude-code-plugins-plus-skills, a repository with 2,596 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.