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.
36
3%
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
7%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 just a skill name repeated with minimal context. It lacks concrete actions, meaningful trigger terms, and explicit usage guidance. It reads as auto-generated boilerplate rather than a thoughtfully crafted description that would help Claude select the right skill.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Creates and manages Firestore composite indexes, generates index configuration files, and deploys index definitions to GCP projects.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user needs to create Firestore indexes, configure composite indexes, manage index.yaml files, or troubleshoot Firestore query indexing errors.'
Expand trigger terms to include natural variations users would say: 'firestore composite index', 'index.yaml', 'firestore query index', 'GCP indexing', 'database index configuration'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description says 'Firestore Index Creator' but does not describe any concrete actions beyond the name itself. There are no specific capabilities listed like 'creates composite indexes', 'manages index configurations', or 'generates index YAML files'. | 1 / 3 |
Completeness | The description barely answers 'what does this do' beyond the name, and the 'when' clause is just a repetition of the skill name as trigger terms rather than meaningful usage guidance. There is no explicit 'Use when...' clause. | 1 / 3 |
Trigger Term Quality | The trigger terms are just 'firestore index creator' repeated twice. Missing natural variations users would say like 'firestore indexes', 'composite index', 'index.yaml', 'GCP Firestore', 'create index', or 'database indexing'. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'Firestore' and 'Index Creator' does narrow the domain somewhat to a specific GCP service, but the lack of detail about what exactly it does could cause overlap with other Firestore-related or GCP-related skills. | 2 / 3 |
Total | 5 / 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 is an empty template/placeholder with no actual content about creating Firestore indexes. It contains only generic boilerplate that describes what the skill would do without providing any actionable instructions, code, commands, or concrete guidance. It fails on every dimension of the rubric.
Suggestions
Add concrete, executable examples showing how to create Firestore indexes (e.g., gcloud CLI commands like `gcloud firestore indexes composite create`, or firebase.json index configuration, or Terraform/Pulumi IaC snippets).
Provide a clear workflow: 1) Identify query patterns needing indexes, 2) Define the index configuration, 3) Deploy the index, 4) Verify the index status with a specific command.
Remove all the generic boilerplate sections (Purpose, When to Use, Capabilities, Example Triggers) and replace with actual technical content—field ordering rules, composite vs single-field indexes, exemptions, and common error patterns.
Add references to related files or documentation for advanced topics like index merge behavior, TTL policies interaction, or cost implications of over-indexing.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler with no substantive information. It explains what the skill does in abstract terms without providing any actual guidance on creating Firestore indexes. Every section restates the same vague concept. | 1 / 3 |
Actionability | There is zero concrete guidance—no commands, no code, no API calls, no configuration examples. The skill describes rather than instructs, offering nothing executable or copy-paste ready. | 1 / 3 |
Workflow Clarity | No workflow steps are provided at all. There is no sequence, no validation, and no process for actually creating a Firestore index. The bullet 'Provides step-by-step guidance' is a claim with no substance. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of boilerplate with no references to detailed materials, no links to related files, and no structured navigation to deeper content. | 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
4dee593
- 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.