firebase-rules-generator
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill firebase-rules-generatorFirebase Rules Generator - Auto-activating skill for GCP Skills. Triggers on: firebase rules generator, firebase rules generator Part of the GCP Skills skill category.
Overall
score
19%
Does it follow best practices?
Validation for skill structure
Activation
7%This description is essentially a placeholder that provides almost no useful information for skill selection. It repeats the skill name as its only trigger term and fails to describe any concrete capabilities or use cases. Claude would struggle to know when to select this skill over others or what it can actually accomplish.
Suggestions
Add specific actions the skill performs, e.g., 'Generates Firestore security rules, validates rule syntax, creates read/write permissions for collections'
Include a proper 'Use when...' clause with natural trigger terms like 'firestore rules', 'security rules', 'database permissions', 'firebase access control', '.rules files'
Specify which Firebase products are covered (Firestore, Realtime Database, Storage) to distinguish from other GCP skills
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the domain ('Firebase Rules Generator') but provides no concrete actions. It doesn't explain what the skill actually does - no mention of generating, validating, or modifying rules. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name, and the 'when' clause is just a repetition of the skill name rather than meaningful trigger guidance. No explicit 'Use when...' clause with actionable triggers. | 1 / 3 |
Trigger Term Quality | The trigger terms are redundant ('firebase rules generator' listed twice) and overly narrow. Missing natural variations users might say like 'firestore rules', 'security rules', 'database rules', 'realtime database rules', or 'firebase permissions'. | 1 / 3 |
Distinctiveness Conflict Risk | The Firebase-specific focus provides some distinctiveness from generic document or code skills, but the lack of detail about what kind of rules (Firestore, Realtime Database, Storage) could cause confusion within GCP/Firebase skill categories. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%This skill content is essentially a placeholder template with no actual substance. It contains no Firebase-specific knowledge, no code examples, no rule syntax, and no actionable guidance. The entire content could be replaced with a single sentence 'This skill helps with Firebase rules' without losing any information.
Suggestions
Add concrete Firebase security rules examples showing common patterns (e.g., user-only access, role-based access, data validation rules)
Include executable code snippets showing the actual Firestore/Realtime Database rules syntax with before/after examples
Define a clear workflow: 1) Identify data structure, 2) Define access patterns, 3) Write rules, 4) Test with Firebase emulator, 5) Deploy
Remove all generic boilerplate text and replace with Firebase-specific guidance that Claude doesn't already know
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that provides no actual value. Phrases like 'provides automated assistance' and 'follows industry best practices' are meaningless filler that Claude doesn't need. | 1 / 3 |
Actionability | There is zero concrete guidance - no code examples, no Firebase rules syntax, no actual instructions on how to generate rules. The content describes what the skill does rather than instructing how to do it. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. There are no steps, no validation checkpoints, and no actual process for generating Firebase security rules. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of unhelpful text with no references to detailed materials, no examples file, and no actual Firebase rules documentation or patterns. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
69%Validation — 11 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 11 / 16 Passed | |
Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.