firestore-index-creator
Firestore Index Creator - Auto-activating skill for GCP Skills. Triggers on: firestore index creator, firestore index creator Part of the GCP Skills skill category.
41
Quality
11%
Does it follow best practices?
Impact
99%
1.15xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/14-gcp-skills/firestore-index-creator/SKILL.mdQuality
Discovery
22%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 description is essentially a placeholder that provides almost no useful information for skill selection. It names the skill and its category but fails to explain what actions it performs, what problems it solves, or when Claude should select it. The duplicated trigger term suggests incomplete or auto-generated content.
Suggestions
Add specific actions the skill performs, e.g., 'Creates and manages Firestore composite indexes, generates index configuration files, troubleshoots index-related query errors.'
Add an explicit 'Use when...' clause with natural trigger scenarios, e.g., 'Use when the user needs to create composite indexes, encounters FAILED_PRECONDITION errors, or asks about Firestore query optimization.'
Include natural keyword variations users might say: 'composite index', 'index.yaml', 'query requires an index', 'Firestore indexing', 'GCP Firestore'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the tool ('Firestore Index Creator') without describing any concrete actions. There are no verbs explaining what it actually does - no mention of creating, managing, configuring, or any specific capabilities. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name itself, and provides no 'when should Claude use it' guidance. The 'Triggers on' field just repeats the skill name rather than describing actual use cases. | 1 / 3 |
Trigger Term Quality | Contains 'firestore index creator' (duplicated) and 'GCP Skills' which are relevant technical terms, but lacks natural variations users might say like 'create firestore index', 'composite index', 'query optimization', or 'index configuration'. | 2 / 3 |
Distinctiveness Conflict Risk | The 'Firestore Index' terminology is fairly specific to a particular GCP service, reducing conflict with unrelated skills. However, the vague description could still conflict with other Firestore-related skills or general GCP database skills. | 2 / 3 |
Total | 6 / 12 Passed |
Implementation
0%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill content is essentially a placeholder template with no actual instructional value. It contains only meta-descriptions of what a skill should do without providing any concrete guidance on Firestore index creation. The content fails on all dimensions by being verbose yet empty of actionable information.
Suggestions
Add actual gcloud CLI commands or Firebase console steps for creating Firestore indexes (e.g., `gcloud firestore indexes composite create --collection-group=users --field-config=...`)
Include a concrete example of a firestore.indexes.json file with proper field configurations and query scopes
Provide a workflow showing: 1) Identify query patterns, 2) Define index configuration, 3) Deploy index, 4) Verify index status with specific commands
Remove all generic boilerplate ('provides automated assistance', 'follows best practices') and replace with actual Firestore index creation patterns
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that provides no actual information about Firestore index creation. Phrases like 'provides automated assistance' and 'follows industry best practices' are meaningless filler that waste tokens. | 1 / 3 |
Actionability | There is zero concrete guidance - no code, no commands, no actual steps for creating Firestore indexes. The content only describes what the skill claims to do without providing any executable instructions. | 1 / 3 |
Workflow Clarity | No workflow is defined. There are no steps, no sequence, and no validation checkpoints. The skill mentions 'step-by-step guidance' but provides none. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of vague descriptions with no references to detailed materials, no links to examples, and no structured navigation to actual implementation details. | 1 / 3 |
Total | 4 / 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
0c08951
- 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.