firebase-rules-generator
Firebase Rules Generator - Auto-activating skill for GCP Skills. Triggers on: firebase rules generator, firebase rules generator Part of the GCP Skills skill category.
34
3%
Does it follow best practices?
Impact
86%
1.06xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/14-gcp-skills/firebase-rules-generator/SKILL.mdQuality
Discovery
7%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description is essentially a skill name repeated as a description, providing almost no useful information for Claude to determine when to select it. It lacks concrete actions, meaningful trigger terms, and any explicit guidance on when the skill should be activated. It would be nearly indistinguishable from other Firebase-related skills in a large skill library.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Generates Firebase security rules for Firestore, Realtime Database, and Cloud Storage, including read/write permissions, authentication checks, and data validation rules.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about Firebase security rules, Firestore permissions, database access control, .rules files, or needs help configuring Firebase authorization.'
Remove the duplicate trigger term ('firebase rules generator' is listed twice) and expand with varied natural language terms users might actually say, such as 'Firestore rules', 'Firebase permissions', 'security rules', 'access control'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain ('Firebase Rules') and mentions 'generator' but provides no concrete actions like 'create security rules', 'validate rule syntax', or 'generate read/write permissions'. It is essentially just a name repeated, not a description of capabilities. | 1 / 3 |
Completeness | The 'what' is extremely vague (just the skill name) and the 'when' is only implied through the repeated trigger phrase. There is no explicit 'Use when...' clause or meaningful explanation of what the skill does or when Claude should select it. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'firebase rules generator' repeated twice. It misses natural user phrases like 'Firestore rules', 'security rules', 'database permissions', 'Firebase access control', '.rules file', or 'Realtime Database rules'. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'Firebase Rules' does narrow the domain somewhat, making it unlikely to conflict with non-Firebase skills. However, the lack of specificity about what kind of Firebase rules (Firestore, Realtime Database, Storage) and what actions are performed could cause overlap with other GCP/Firebase-related skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is an empty placeholder with no substantive content. It contains only generic boilerplate text that repeats the phrase 'firebase rules generator' without providing any actual guidance on Firebase security rules syntax, patterns, common rule structures, or executable examples. It fails on every dimension of the rubric.
Suggestions
Add concrete, executable Firebase rules examples (e.g., Firestore rules for common patterns like user-owned documents, role-based access, public read/private write).
Include a clear workflow for generating and validating rules, such as writing rules → testing with Firebase emulator → deploying with `firebase deploy --only firestore:rules`.
Remove all generic filler text ('This skill provides automated assistance...') and replace with actual rule syntax, patterns, and anti-patterns specific to Firebase Security Rules.
Add references to advanced topics like custom functions in rules, granular field-level access, and rate limiting patterns, either inline or via linked files.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and boilerplate. It explains nothing Claude doesn't already know, repeats 'firebase rules generator' excessively, and provides zero actual technical content about generating Firebase security rules. | 1 / 3 |
Actionability | There are no concrete code examples, no executable commands, no rule syntax, no specific guidance whatsoever. The skill describes what it could do rather than providing any actionable instructions for generating Firebase rules. | 1 / 3 |
Workflow Clarity | No workflow, steps, or process is defined. The skill claims to provide 'step-by-step guidance' but contains none. There are no validation checkpoints or any sequenced instructions. | 1 / 3 |
Progressive Disclosure | The content is a flat, uninformative page with no references to detailed materials, no links to examples or rule templates, and no meaningful structure beyond generic placeholder headings. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Commit
4dee593
- 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.