firestore-operations-manager
Manage Firebase/Firestore operations including CRUD, queries, batch processing, and index/rule guidance. Use when you need to create/update/query Firestore documents, run batch writes, troubleshoot missing indexes, or plan migrations. Trigger with phrases like "firestore operations", "create firestore document", "batch write", "missing index", or "fix firestore query".
75
71%
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 ./plugins/community/jeremy-firestore/skills/firestore-operations-manager/SKILL.mdQuality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a well-crafted skill description that covers all key dimensions effectively. It specifies concrete actions, provides explicit 'Use when' and 'Trigger with' clauses, and is clearly scoped to the Firebase/Firestore domain, making it easy to distinguish from other database-related skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: CRUD operations, queries, batch processing, index/rule guidance, batch writes, troubleshooting missing indexes, and planning migrations. | 3 / 3 |
Completeness | Clearly answers both 'what' (manage Firebase/Firestore operations including CRUD, queries, batch processing, index/rule guidance) and 'when' (explicit 'Use when' clause and 'Trigger with phrases like' clause providing concrete trigger scenarios). | 3 / 3 |
Trigger Term Quality | Includes strong natural trigger terms users would actually say: 'firestore operations', 'create firestore document', 'batch write', 'missing index', 'fix firestore query', plus domain terms like Firebase, Firestore, CRUD, migrations. | 3 / 3 |
Distinctiveness Conflict Risk | Clearly scoped to Firebase/Firestore specifically, with distinct trigger terms like 'firestore', 'missing index', 'batch write' that are unlikely to conflict with generic database or other cloud service skills. | 3 / 3 |
Total | 12 / 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.
The skill has good structural organization and appropriate progressive disclosure with a reference to a detailed guide. However, it critically lacks actionable, executable content—there are no code snippets, no concrete index JSON examples, no actual emulator commands, and no real batch write patterns. The examples section describes outcomes rather than showing them, making this more of an abstract checklist than a practical skill.
Suggestions
Add executable code examples for at least the most common operations (e.g., a batch write with checkpointing in Python/Node, a composite index JSON definition, an emulator test command).
Replace the abstract examples with concrete input/output pairs showing actual Firestore code and index configurations.
Include specific emulator commands (e.g., `firebase emulators:start --only firestore`) and smoke test snippets in the validation step.
Add a concrete feedback loop for batch migrations: check progress → handle failures → resume from checkpoint → verify completion.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is reasonably concise but includes some unnecessary framing (e.g., the Overview section largely restates the Instructions). Phrases like 'Operate Firestore safely in production' and 'Use this skill to design Firestore data access patterns' add little value for Claude. The Prerequisites section explains things Claude can infer. | 2 / 3 |
Actionability | The skill provides no executable code, no concrete commands, no specific examples of index JSON, no actual batch write code, and no real Firestore snippets. Everything is described abstractly ('propose sharding', 'provide the exact composite index') without actually demonstrating how. The examples section describes what the result would be rather than showing it. | 1 / 3 |
Workflow Clarity | There is a numbered sequence (identify → confirm → implement → check indexes → validate) which provides reasonable structure. However, validation steps are vague ('run emulator tests or a minimal smoke query') with no specific commands, and there's no explicit feedback loop for error recovery during batch operations or migrations, which the rubric says should cap this at 2. | 2 / 3 |
Progressive Disclosure | The skill is well-structured with clear sections and a single-level reference to a full detailed guide in `references/SKILL.full.md` plus external Firestore docs. Navigation is straightforward and content is appropriately split between overview and detailed reference. | 3 / 3 |
Total | 8 / 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 |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Commit
3e83543
- 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.