CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

firebase-firestore

Sets up, manages, queries, and configures Cloud Firestore databases (Standard/Enterprise edition), including data modeling, security rules, indexes, and SDK integrations (Web, Admin, Python, iOS, Android, Flutter). Use when adding or migrating app databases, creating/listing Firestore databases, defining data models/indexes, writing SDK queries, or integrating Firestore SDKs. For authoring or modifying Firestore Security Rules (firestore.rules), delegate to the firestore-rules-author subagent if subagent delegation is available, or use firestore-rules-creation otherwise. Don't use for Data Connect, BigQuery, or standalone Hosting, Auth, Storage/GCS, Crashlytics, or Functions tasks.

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

93%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 an exemplary hub-and-spoke skill: lean routing logic with copy-paste CLI commands, explicit user decision points, and perfect progressive disclosure verified against the actual bundle (every reference file exists and is linked exactly one level deep). The single gap is the absence of a post-create verification step, which keeps workflow clarity one notch below the top anchor.

DimensionReasoningScore

Conciseness

Quotes: "Run the following command to list current Firestore databases:" followed directly by `npx -y firebase-tools@latest firestore:databases:list`, and "If the **`edition`** is `STANDARD`, follow the guides under `references/standard/`" — the body is commands, branch logic, and file lists with zero explanation of concepts Claude already knows. Not 4: the few intro phrases are functional, not over-explanation that needs trimming.

5 / 5

Actionability

Quotes: "npx -y firebase-tools@latest firestore:databases:create <database-id> --edition=\"enterprise\" --location=\"<selected-location>\"" and "npx -y firebase-tools@latest firestore:databases:get <database-id>" — fully executable, copy-paste-ready commands with clearly marked placeholders covering the common provisioning flow. Not 4: no gaps; platform-specific detail is appropriately delegated to the referenced guides.

5 / 5

Workflow Clarity

Quotes: "Before setting up dependencies, writing data models, or configuring security rules, you MUST always identify the Firestore instance edition", "Ask the user which database instance they wish to target", "Run `npx -y firebase-tools@latest firestore:locations` to get the list of options" — a clear sequence with explicit branching and user-interaction checkpoints, matching anchor 4. Not 5: there is no verification step after database creation (e.g., re-running `firestore:databases:get` to confirm the instance is active), so explicit validation checkpoints are incomplete. Not 3: the operations here are read-only or single non-destructive creates with user confirmation at each decision point, so the missing-feedback-loop cap for destructive/batch operations does not apply.

4 / 5

Progressive Disclosure

Quotes: "Read [provisioning.md](references/standard/provisioning.md)", "Read [data_model.md](references/enterprise/data_model.md)", plus the edition-based routing "follow the guides under `references/enterprise/`" — a clear overview with well-signaled, one-level-deep references. Verified against the actual bundle: all 14 files linked in the body exist under references/standard/ and references/enterprise/, every bundle file is reachable from SKILL.md, and reference files only cross-link siblings (no 2+ level nesting). Not 4: navigation is complete and unambiguous, with a mandatory-reading callout for the Enterprise SDK guides.

5 / 5

Total

19

/

20

Passed

Description

92%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 is a strong example: it states concrete capabilities comprehensively, provides an explicit 'Use when' trigger clause with concrete phrases, adds negative boundary guidance, and handles cross-skill delegation cleanly. The only weakness is modest trigger-synonym coverage (e.g., 'Firebase', 'NoSQL') that keeps trigger term quality just below the top anchor.

DimensionReasoningScore

Specificity

Quotes: "Sets up, manages, queries, and configures Cloud Firestore databases", "including data modeling, security rules, indexes, and SDK integrations (Web, Admin, Python, iOS, Android, Flutter)" — multiple concrete actions with comprehensive coverage across editions and platforms, matching the anchor 5 example's breadth. Not 4: there are no meaningful gaps in the action coverage.

5 / 5

Completeness

Quotes: "Use when adding or migrating app databases, creating/listing Firestore databases, defining data models/indexes, writing SDK queries, or integrating Firestore SDKs" plus an explicit negative scope ("Don't use for Data Connect, BigQuery, or standalone Hosting, Auth, Storage/GCS, Crashlytics, or Functions tasks") — both what and when are answered explicitly with concrete trigger phrases. Not 4: the when-clause is already fully explicit, not merely present.

5 / 5

Trigger Term Quality

Quotes: "adding or migrating app databases", "creating/listing Firestore databases", "writing SDK queries", "firestore.rules" — natural trigger phrasing plus a file name, matching anchor 4 ("good keyword coverage; a few natural terms missing"). Not 5: common user synonyms like "Firebase" or "NoSQL database" are absent from the trigger set.

4 / 5

Distinctiveness Conflict Risk

Quotes: "Cloud Firestore databases (Standard/Enterprise edition)" and "Don't use for Data Connect, BigQuery, or standalone Hosting, Auth, Storage/GCS, Crashlytics, or Functions tasks" — a clear niche with distinct triggers and an explicit exclusion list for adjacent Firebase products. Not 4: overlap risk is further reduced by delegating rules authoring ("delegate to the firestore-rules-author subagent... or use firestore-rules-creation"), leaving minimal conflict.

5 / 5

Total

19

/

20

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

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

relative_links

Relative link issues: 14 deeper-than-1-level

Warning

referenced_paths_exist

Referenced path issues: 14 deeper-than-1-level

Warning

Total

13

/

16

Passed

Repository

firebase/agent-skills

Path

skills/firebase-firestore/SKILL.md

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.