firebase
Firebase Firestore, Auth, Storage, real-time listeners, security rules
44
32%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/firebase/SKILL.mdQuality
Discovery
22%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description is essentially a comma-separated list of Firebase-related keywords with no verbs, no concrete actions, and no 'Use when...' clause. While the Firebase domain focus provides some natural trigger terms, the lack of specificity about what the skill does and when to use it makes it inadequate for reliable skill selection among many options.
Suggestions
Add concrete action verbs describing what the skill does, e.g., 'Configures Firestore collections, writes security rules, sets up Firebase Auth providers, manages Storage buckets, and implements real-time listeners.'
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about Firebase setup, Firestore queries, authentication flows, storage uploads, or writing security rules.'
Include additional natural trigger terms users might say, such as 'Firebase project', 'authentication', 'NoSQL database', 'Firebase SDK', or 'cloud storage'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description lists Firebase service names (Firestore, Auth, Storage) and concepts (real-time listeners, security rules) but does not describe any concrete actions. There are no verbs indicating what the skill actually does—it reads like a keyword list rather than a capability description. | 1 / 3 |
Completeness | The description partially addresses 'what' (Firebase-related topics) but only as a keyword list without concrete actions, and completely lacks any 'when' guidance or explicit trigger clause. Per the rubric, a missing 'Use when...' clause caps completeness at 2, and the weak 'what' brings it down to 1. | 1 / 3 |
Trigger Term Quality | It includes relevant keywords a user might mention such as 'Firebase', 'Firestore', 'Auth', 'Storage', 'security rules', and 'real-time listeners'. However, it misses common variations like 'authentication', 'database', 'cloud functions', 'Firebase project', or 'NoSQL', limiting coverage. | 2 / 3 |
Distinctiveness Conflict Risk | The Firebase ecosystem focus provides some distinctiveness, but the broad listing of services (Auth, Storage) without specificity could overlap with general backend, authentication, or cloud storage skills. It's somewhat specific to Firebase but not sharply delineated. | 2 / 3 |
Total | 6 / 12 Passed |
Implementation
42%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is a comprehensive Firebase reference but suffers from being a near-complete rewrite of Firebase documentation rather than a targeted skill. It's highly actionable with excellent executable code examples, but its extreme length (~500+ lines) wastes token budget on patterns Claude already knows. The monolithic structure with no progressive disclosure means the entire document must be loaded even when only security rules or auth patterns are needed.
Suggestions
Reduce content by 60-70%: remove the Firebase stack table, basic CLI commands, project structure, and standard auth patterns that Claude already knows. Focus only on non-obvious patterns like denormalization strategies, transaction gotchas, and security rule validation.
Split into separate files (e.g., security-rules.md, data-modeling.md, cloud-functions.md) and make SKILL.md a concise overview with links, matching the 'Load with: base.md + security.md' pattern already hinted at.
Add explicit workflow sequences with validation checkpoints, e.g., 'Write rules → Test with emulator → Verify all tests pass → Only then deploy' with specific commands at each step.
Remove explanatory comments like '// Denormalized for display' and '// Use subcollections for: 1. Unbounded lists...' — these are concepts Claude understands; instead, show the pattern and let the code speak.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is extremely verbose at ~500+ lines, covering Firebase CLI setup, project structure, full CRUD operations, auth, cloud functions, batch operations, indexes, and more. Much of this is standard Firebase documentation that Claude already knows. The Firebase stack table, CLI quick reference, and basic auth patterns add little unique value. | 1 / 3 |
Actionability | All code examples are fully executable TypeScript/JavaScript with proper imports, complete function signatures, and copy-paste ready patterns. The security rules, CRUD operations, transactions, and Cloud Functions examples are concrete and specific. | 3 / 3 |
Workflow Clarity | While individual operations are clear, there's no explicit workflow sequencing for multi-step processes like deploying security rules (write → test locally → deploy). The rules testing section mentions emulators but doesn't enforce a validate-before-deploy workflow. Batch operations lack validation checkpoints. | 2 / 3 |
Progressive Disclosure | The content is a monolithic wall of text with everything inline. The header mentions 'Load with: base.md + security.md' suggesting a multi-file structure exists, but the skill itself dumps all content (data modeling, auth, functions, security rules, indexes, CLI reference) into one massive file with no references to separate detailed documents. | 1 / 3 |
Total | 7 / 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 |
|---|---|---|
skill_md_line_count | SKILL.md is long (749 lines); consider splitting into references/ and linking | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Repository
- alinaqi/claude-bootstrap
- Commit
d4ddb03
- 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.