firebase

Firebase Firestore, Auth, Storage, real-time listeners, security rules

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

65%

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

The content is highly actionable with complete, executable code across the Firebase stack, but it is a large monolithic reference rather than a progressive-disclosure overview, and reference-style sections lack sequenced validation workflows for risky database/batch operations.

Suggestions

Split detailed API references (full CRUD, real-time listeners, security rules, Cloud Functions) into separate reference files under references/ and keep SKILL.md as a concise overview with one-level-deep links.

Add an explicit end-to-end workflow with validate→fix→retry checkpoints for destructive or batch Firestore operations (deploy rules -> run rules-unit-tests -> fix -> redeploy).

Trim inline code volume by pointing long examples to reference files so the core SKILL.md respects the token budget while preserving clarity.

Dimension	Reasoning	Score
Conciseness	Each section is lean with no basic-concept padding, but the body is a very large single-file dump (~740 lines) of code and patterns that does not respect the token budget and could be tightened or split.	2 / 3
Actionability	The body provides fully executable, copy-paste-ready TypeScript, security-rules JavaScript, JSON index configs, and bash CLI commands with specific imports and concrete examples.	3 / 3
Workflow Clarity	Content is organized as topical reference sections rather than a sequenced workflow; the rules-testing section offers a validate feedback loop, but batch/transaction and database operations lack explicit validate→fix→retry checkpoints, capping this at 2.	2 / 3
Progressive Disclosure	Sections are well-organized with clear headers, but the skill is a monolithic 700+ line SKILL.md with no bundle files (references/scripts/assets absent) and content that could be split into separate reference files.	2 / 3
	Total	9 / 12 Passed

Description

72%

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 concrete and Firebase-distinct with good trigger terms, but it only states capabilities without an explicit "Use when..." trigger clause in the description field itself, leaving completeness at the mid level.

Suggestions

Add an explicit "Use when working with Firebase..." trigger clause to the description field so it answers both what and when.

Reframe the capability list with action verbs (e.g., "Model Firestore data, manage Auth, handle Storage uploads, subscribe to real-time listeners, enforce security rules") to lift specificity.

Dimension	Reasoning	Score
Specificity	The description "Firebase Firestore, Auth, Storage, real-time listeners, security rules" names the Firebase domain and several concrete capabilities, but as a noun list rather than action-verbs, so it is not comprehensive in the way the top anchor's "Extract... fill... merge..." actions are.	2 / 3
Completeness	It answers "what" (Firestore, Auth, Storage, listeners, rules) but the description field contains no "Use when..." clause; the when-guidance lives only in the separate when-to-use field, so completeness is capped at 2.	2 / 3
Trigger Term Quality	"Firebase", "Firestore", "Auth", "Storage", and "security rules" are natural terms a user would say when needing this skill, giving good coverage of relevant trigger keywords.	3 / 3
Distinctiveness Conflict Risk	The Firebase-specific vocabulary carves out a clear niche unlikely to trigger for unrelated skills, matching the distinct-trigger anchor.	3 / 3
	Total	10 / 12 Passed

Validation

87%

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 — 14 / 16 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	14 / 16 Passed

Repository: alinaqi/claude-bootstrap
Commit: 9dacc46

Reviewed: about 5 hours 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.