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
Quality
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 severely underdeveloped, essentially just restating the skill name without explaining capabilities or providing useful trigger guidance. The duplicate trigger term and lack of concrete actions make it nearly useless for skill selection. It reads more like a placeholder than a functional skill description.
Suggestions
Add specific capabilities: 'Generates Firebase security rules for Firestore, Realtime Database, and Cloud Storage. Creates read/write permissions, validates rule syntax, and implements role-based access patterns.'
Add a proper 'Use when...' clause: 'Use when the user needs to create, modify, or debug Firebase security rules, mentions database permissions, or asks about Firestore/RTDB access control.'
Expand trigger terms to include natural variations: 'firestore rules', 'database security', 'firebase permissions', 'storage rules', 'access control rules', '.rules files'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Firebase Rules Generator') without describing any concrete actions. There are no specific capabilities listed like 'generate security rules', 'validate rules syntax', or 'create Firestore/Storage rules'. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name itself, and the 'when' guidance is just a duplicate trigger phrase. There is no explicit 'Use when...' clause or meaningful trigger guidance. | 1 / 3 |
Trigger Term Quality | The trigger terms are redundant ('firebase rules generator' listed twice) and overly narrow. Missing natural variations users would say like 'firestore rules', 'security rules', 'database rules', 'firebase permissions', or 'realtime database rules'. | 1 / 3 |
Distinctiveness Conflict Risk | The 'Firebase Rules' focus provides some distinctiveness from generic GCP skills, but the lack of specificity about what types of rules (Firestore, Realtime Database, Storage) could cause confusion with other 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 template with no actual content about Firebase security rules. It contains only generic boilerplate text that could apply to any skill, with no executable code, no rule syntax examples, no workflow guidance, and no references to Firebase documentation or patterns.
Suggestions
Add concrete Firebase security rules syntax examples (e.g., Firestore rules for read/write permissions, RTDB rules structure)
Include a workflow for generating and testing rules: write rules -> deploy to emulator -> test -> deploy to production
Provide specific patterns like user-owned data rules, role-based access, and validation rules with copy-paste ready code
Add references to Firebase documentation and link to example rule files for common use cases (auth, user data, admin access)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains nothing specific about Firebase rules. Phrases like 'automated assistance' and 'industry best practices' are filler that Claude doesn't need. | 1 / 3 |
Actionability | No concrete code, commands, or examples of actual Firebase security rules syntax. The content describes what the skill does abstractly rather than providing executable guidance. | 1 / 3 |
Workflow Clarity | No workflow steps are provided. There's no sequence for generating rules, no validation steps, and no guidance on how to actually create or test Firebase rules. | 1 / 3 |
Progressive Disclosure | No references to detailed documentation, no links to examples or advanced topics. The content is a shallow placeholder with no structure for discovery. | 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
0c08951
- 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.