analyzing-database-indexes
tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill analyzing-database-indexesProcess use when you need to work with database indexing. This skill provides index design and optimization with comprehensive guidance and automation. Trigger with phrases like "create indexes", "optimize indexes", or "improve query performance".
Validation
81%| Criteria | Description | Result |
|---|---|---|
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 |
Total | 13 / 16 Passed | |
Implementation
20%This skill is a generic template with no actual database indexing content. It describes a general software development workflow that could apply to any task, completely failing to provide the specific SQL commands, index analysis techniques, query plan interpretation, or optimization strategies that a 'Database Index Advisor' skill requires. The content wastes tokens on obvious advice while providing zero actionable database guidance.
Suggestions
Add concrete SQL examples for analyzing existing indexes (e.g., querying pg_stat_user_indexes, sys.dm_db_index_usage_stats) and creating indexes with specific syntax
Include specific index analysis workflow: identify slow queries → analyze query plans → recommend index columns → validate with EXPLAIN ANALYZE → measure improvement
Provide executable code for common index advisor tasks: finding unused indexes, identifying missing indexes from query patterns, detecting duplicate indexes
Remove all generic software development advice and focus exclusively on database-specific indexing knowledge that Claude doesn't already have
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose with generic boilerplate that applies to any task. Contains no database-specific content despite being a 'Database Index Advisor' skill. Every section is padded with obvious advice Claude already knows (e.g., 'backup critical data', 'test in non-production'). | 1 / 3 |
Actionability | No concrete code, SQL examples, or specific commands for index analysis. Entirely abstract guidance like 'Review current configuration' and 'Define optimal approach' without any executable database indexing instructions, query analysis techniques, or index creation syntax. | 1 / 3 |
Workflow Clarity | Steps are numbered and sequenced, but they're generic project management phases rather than database indexing workflows. No specific validation checkpoints for index operations (e.g., checking query plans, measuring index usage, validating index creation). | 2 / 3 |
Progressive Disclosure | References external files in Resources section with clear paths, but the main content is a monolithic wall of generic text. The referenced files use placeholder paths that may not exist, and the 'Examples' section is empty placeholder text. | 2 / 3 |
Total | 6 / 12 Passed |
Activation
82%The description has good trigger term coverage and explicit 'when to use' guidance, which are its strongest aspects. However, it lacks specific concrete actions (what exactly does it do beyond 'guidance and automation'?) and uses some vague filler language. The domain is reasonably distinct but could have minor overlap with general database performance skills.
Suggestions
Replace 'comprehensive guidance and automation' with specific actions like 'analyze query plans, recommend index columns, generate CREATE INDEX statements, identify unused indexes'
Add more specific database-related trigger terms like 'slow queries', 'index strategy', 'covering index', or specific database names if applicable
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (database indexing) and mentions 'index design and optimization' but lacks concrete specific actions. 'Comprehensive guidance and automation' is vague filler rather than specific capabilities. | 2 / 3 |
Completeness | Explicitly answers both what ('index design and optimization') and when ('Trigger with phrases like...'). The trigger guidance is explicit and actionable, though the 'what' portion could be more detailed. | 3 / 3 |
Trigger Term Quality | Includes natural trigger phrases users would say: 'create indexes', 'optimize indexes', 'improve query performance'. These are realistic terms a user would use when needing this skill. | 3 / 3 |
Distinctiveness Conflict Risk | Database indexing is a specific niche, but 'improve query performance' could overlap with general database optimization or query tuning skills. The triggers are mostly distinct but not fully isolated. | 2 / 3 |
Total | 10 / 12 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.