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.
Overall
score
24%
Does it follow best practices?
Validation for skill structure
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill firestore-index-creatorActivation
22%This description is essentially a placeholder that relies entirely on the skill name without providing meaningful content. It fails to explain what Firestore index creation involves, what specific actions the skill performs, or when users should invoke it beyond repeating the skill name. The duplicate trigger term suggests auto-generated content without human review.
Suggestions
Add specific actions the skill performs, e.g., 'Generates composite index definitions, creates index.yaml configurations, analyzes queries for missing indexes'
Replace the redundant trigger with a proper 'Use when...' clause describing scenarios like 'Use when queries fail with missing index errors, when optimizing Firestore query performance, or when setting up new collections'
Include natural trigger terms users would say: 'composite index', 'index.yaml', 'query requires an index', 'Firestore performance', 'collection group index'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the tool ('Firestore Index Creator') without describing any concrete actions. There's no explanation of what creating a Firestore index actually involves or what specific operations the skill performs. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name, and the 'when' clause only repeats the skill name verbatim rather than describing actual use cases or scenarios when this skill should be selected. | 1 / 3 |
Trigger Term Quality | Includes 'firestore index creator' as a trigger term (duplicated), which is relevant but narrow. Missing natural variations users might say like 'create index', 'composite index', 'query optimization', 'index.yaml', or 'firestore queries'. | 2 / 3 |
Distinctiveness Conflict Risk | The 'Firestore Index' terminology is fairly specific to GCP/Firebase, reducing conflict with unrelated skills. However, it could overlap with other GCP or database indexing skills due to lack of specific scope definition. | 2 / 3 |
Total | 6 / 12 Passed |
Implementation
0%This skill content is essentially a placeholder template with no actual instructional value. It contains no concrete information about Firestore indexes - no gcloud commands, no index configuration syntax, no examples of composite vs single-field indexes, and no guidance on when indexes are needed. The entire content could be replaced with actual executable guidance in fewer tokens.
Suggestions
Add concrete gcloud commands for creating Firestore indexes, e.g., `gcloud firestore indexes composite create --collection-group=users --field-config=...`
Include example index configuration JSON/YAML showing field paths, order, and query scope
Provide a workflow for: identifying needed indexes from query errors -> creating index -> verifying index status
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 describes what the skill supposedly does rather than instructing how to do anything. | 1 / 3 |
Workflow Clarity | No workflow is provided whatsoever. There are no steps, no sequence, and no validation checkpoints for creating Firestore indexes despite this being a task that involves specific CLI commands or console actions. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of unhelpful text with no structure pointing to detailed materials. There are no references to actual documentation, examples, or related files that would contain useful information. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
69%Validation — 11 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 11 / 16 Passed | |
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.