Name: firebase
Rating: 39.2 (1 reviews)
Author: administrakt0r

firebase

You're a developer who has shipped dozens of Firebase projects. You've seen the "easy" path lead to security breaches, runaway costs, and impossible migrations. You know Firebase is powerful, but you also know its sharp edges.

Quality

38%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/firebase/SKILL.md

The canonical home for this skill is firebase in administrakt0r/AI-Agents-Safe-Coding-Skills

Quality

Content

41%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is structurally clean and token-efficient but substantively thin: no executable code, no sequenced workflow or validation, a truncated sentence, and a generic placeholder 'When to Use'. It reads as an outline rather than actionable guidance.

Suggestions

Add concrete, executable examples for each pattern (e.g., a modular SDK import snippet, a sample Firestore security-rules file, a query-oriented data model).

Replace the placeholder 'When to Use' with real trigger guidance and complete the truncated 'You advocate for Firebase w' sentence.

Provide a short validation/verification step for the destructive-adjacent operations (security rules, listener sizing) so the workflow has a checkpoint.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence, but the duplicated persona intro and a truncated sentence ('You advocate for Firebase w') waste some tokens, sitting just below the top anchor.	4 / 5
Actionability	Patterns are high-level one-liners ('Import only what you need for smaller bundles', 'Secure your data with proper rules from day one') with no code, commands, or specific steps, matching the minimal-concrete-guidance anchor.	2 / 5
Workflow Clarity	There is no sequence of steps and no validation checkpoints anywhere; the body lists categories (Capabilities, Patterns, Anti-Patterns) rather than a workflow, matching the steps-missing anchor.	1 / 5
Progressive Disclosure	The body is under 50 lines with no bundle files and well-organized sections, satisfying the simple-skill exception, but the truncated sentence and placeholder 'When to Use' section keep it below the top anchor.	4 / 5
	Total	11 / 20 Passed

Description

35%Weight 40%Scale 1-5

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 reads as a second-person persona narrative rather than a capability/trigger statement, listing no concrete actions and no 'Use when' guidance. Firebase-specificity gives it a clear niche, but specificity and completeness are weak.

Suggestions

Rewrite in third person listing concrete actions (e.g., 'Designs Firestore security rules, models data for query patterns, and sizes listener usage for cost control').

Add an explicit 'Use when...' clause with natural trigger phrases like 'Firebase, Firestore, security rules, Realtime Database, Cloud Functions'.

Replace the persona framing with what the skill does and when to invoke it.

Dimension	Reasoning	Score
Specificity	The description names the Firebase domain but frames a persona ('You're a developer who has shipped dozens of Firebase projects') with no concrete actions; base anchor 2 reduced by 1 for second-person voice per the rubric guideline.	1 / 5
Completeness	It offers a vague persona 'what' with no concrete actions and no 'Use when...' trigger guidance, matching the 'vague what and no when' anchor.	2 / 5
Trigger Term Quality	'Firebase' is the natural term a user would say, but the description lacks common variations, sub-products, or synonyms, matching the 'some relevant keywords but missing variations' anchor.	3 / 5
Distinctiveness Conflict Risk	Firebase is a clear, distinct niche unlikely to trigger the wrong skill, though no explicit trigger phrases are given, so it sits just below the top anchor.	4 / 5
	Total	10 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: plugins/AI-Agents-Safe-Coding-Skills-claude/skills/firebase/SKILL.md
Commit: 57c135b

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.