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".
72
67%
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 strong skill description that clearly defines its scope around Firebase/Firestore operations, provides explicit trigger guidance with natural user phrases, and is highly distinctive. It covers the what, when, and trigger dimensions comprehensively with concrete, actionable language in third person voice.
| 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 | Highly distinctive with a clear niche around Firebase/Firestore specifically. The trigger terms are domain-specific ('firestore', 'missing index', 'batch write') and unlikely to conflict with generic database or other cloud service skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
35%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 high-level process document than an actionable skill. Its biggest weakness is the complete absence of concrete code examples, specific CLI commands, or actual JSON configurations—everything stays at the descriptive level. The workflow structure is reasonable but lacks the specificity and validation rigor needed for production Firestore operations.
Suggestions
Add executable code snippets for at least the core operations (CRUD, batch write, transaction) using the Firebase Admin SDK or client SDK, with copy-paste ready examples.
Include a concrete `firestore.indexes.json` example showing a composite index definition, since index management is a key use case.
Provide specific emulator commands (e.g., `firebase emulators:start --only firestore`) and a concrete smoke test snippet in the validation step.
Flesh out the Examples section with actual input/output pairs showing real code rather than just describing what the result would be.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is reasonably concise but includes some unnecessary framing (e.g., the Overview section largely restates the Instructions, and phrases like 'or permission to propose one' add little value). Some sections like Prerequisites explain things Claude can infer. | 2 / 3 |
Actionability | The skill provides no executable code, no concrete commands, no specific Firestore SDK snippets, and no actual index JSON examples. The examples section describes what the result would be rather than showing it. Everything remains at the level of abstract description rather than concrete instruction. | 1 / 3 |
Workflow Clarity | There is a numbered sequence of steps covering 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 within the workflow. | 2 / 3 |
Progressive Disclosure | The skill references a full detailed guide at `${CLAUDE_SKILL_DIR}/references/SKILL.full.md` and external Firestore docs, which is good structure. However, no bundle files were provided to verify the reference exists, and the main content itself could benefit from better separation—the Examples section is too thin to justify being inline while the Instructions section could use more detail. | 2 / 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 |
|---|---|---|
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
3a2d27d
- 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.