firebase
Firebase Firestore, Auth, Storage, real-time listeners, security rules
35
32%
Does it follow best practices?
Impact
—
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 provides some natural distinctiveness, the lack of actionable detail and trigger guidance 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 common user-facing variations like 'authentication', 'database queries', 'cloud storage', 'Firebase project configuration' to improve trigger term coverage.
| 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 reads more like a comprehensive Firebase tutorial than a targeted skill file. While the code examples are excellent and fully executable, the content is far too verbose for a skill context — it explains many concepts Claude already knows and packs everything into a single massive file. The lack of progressive disclosure and workflow sequencing for multi-step operations (like rule deployment or project setup) are significant weaknesses.
Suggestions
Reduce content by 60-70%: remove the Firebase Stack table, basic concept explanations, and standard patterns Claude already knows. Focus only on project-specific conventions, gotchas, and non-obvious patterns.
Split into multiple files: create separate references for security rules, data modeling patterns, Cloud Functions, and auth — keep SKILL.md as a concise overview with links to each.
Add explicit workflow sequences with validation checkpoints for critical paths like 'deploy security rules' (write rules → test with emulator → run unit tests → deploy) and 'set up new Firebase project'.
Move the anti-patterns section higher and make it more prominent — these non-obvious gotchas are the highest-value content for Claude, unlike the standard CRUD examples.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is extremely verbose at ~500+ lines, explaining many concepts Claude already knows (what Firestore is, what Authentication does, basic CRUD patterns, OAuth flows). The Firebase Stack table, project structure, and much of the boilerplate code are standard knowledge that don't need to be spelled out. This is essentially a Firebase tutorial rather than a concise skill reference. | 1 / 3 |
Actionability | The skill provides fully executable TypeScript code examples throughout — initialization, CRUD operations, real-time listeners, security rules, Cloud Functions, batch operations, and transactions are all copy-paste ready with proper imports and type annotations. | 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) or setting up a new project. The rules testing section mentions emulators but doesn't provide a clear validate-fix-retry loop. Batch operations lack validation checkpoints. | 2 / 3 |
Progressive Disclosure | Everything is crammed into a single monolithic file with no references to supporting documents. The content covers setup, data modeling, SDK usage, security rules, auth, Cloud Functions, batch operations, indexes, and CLI reference — all inline. This would benefit enormously from splitting into separate files (e.g., SECURITY_RULES.md, DATA_MODELING.md, CLOUD_FUNCTIONS.md) with the SKILL.md serving as a concise overview. | 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 (748 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
65efb33
- 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.