analyzing-query-performance
tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill analyzing-query-performanceExecute use when you need to work with query optimization. This skill provides query performance analysis with comprehensive guidance and automation. Trigger with phrases like "optimize queries", "analyze performance", or "improve query speed".
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 query performance content. It could apply to literally any technical task - there's nothing about EXPLAIN plans, indexes, query rewriting, execution plans, or any database-specific guidance. The entire content is boilerplate project management steps that Claude already knows.
Suggestions
Replace generic steps with specific query optimization techniques: EXPLAIN/EXPLAIN ANALYZE usage, index analysis, query rewriting patterns, and execution plan interpretation
Add concrete executable examples showing before/after query optimization with actual SQL and performance metrics
Include specific validation commands (e.g., 'EXPLAIN ANALYZE SELECT...' with expected output patterns to look for)
Remove all generic content like 'Review current configuration' and 'Define optimal approach' - focus only on query-specific knowledge Claude doesn't have
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose with generic boilerplate that applies to any task. Contains no query-specific content - phrases like 'Review current configuration, setup, and baseline metrics' and 'Define optimal approach based on best practices' are padding that Claude already knows. | 1 / 3 |
Actionability | No concrete code, commands, or query-specific examples. Everything is abstract guidance like 'Execute implementation' and 'Run comprehensive tests' without any actual SQL, EXPLAIN plans, index syntax, or specific query optimization techniques. | 1 / 3 |
Workflow Clarity | Steps are numbered and sequenced, but they're generic project management steps rather than query optimization workflow. No specific validation checkpoints for query performance (e.g., 'run EXPLAIN ANALYZE before/after'). | 2 / 3 |
Progressive Disclosure | References external files in Resources section which is good structure, but the main content is a wall of generic text. The referenced files use placeholder paths and likely don't exist. No clear quick-start section. | 2 / 3 |
Total | 6 / 12 Passed |
Activation
40%This description suffers from vague capability statements despite having reasonable trigger terms. The phrase 'comprehensive guidance and automation' is meaningless fluff that doesn't help Claude understand what the skill actually does. The description would benefit from concrete actions and specifying the domain (e.g., SQL databases, specific database engines).
Suggestions
Replace 'comprehensive guidance and automation' with specific actions like 'Analyzes query execution plans, identifies missing indexes, rewrites inefficient joins, and suggests caching strategies'
Specify the domain more clearly - what type of queries? SQL? Which databases? (e.g., 'for PostgreSQL and MySQL databases')
Add more natural trigger term variations like 'slow query', 'query taking too long', 'database performance', 'execution plan', 'index optimization'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague language like 'query performance analysis with comprehensive guidance and automation' without listing concrete actions. No specific capabilities are enumerated (e.g., what kind of analysis, what optimizations, what databases). | 1 / 3 |
Completeness | Has a 'Trigger with phrases like...' clause which partially addresses 'when', but the 'what' is extremely vague ('comprehensive guidance and automation'). The trigger guidance exists but the capability description is too weak for a score of 3. | 2 / 3 |
Trigger Term Quality | Includes some natural trigger phrases ('optimize queries', 'analyze performance', 'improve query speed') that users might say, but lacks variations like 'slow query', 'SQL performance', 'database optimization', or specific database types. | 2 / 3 |
Distinctiveness Conflict Risk | The term 'query optimization' is somewhat specific but could overlap with database administration skills, SQL skills, or general performance tuning skills. Doesn't specify what type of queries (SQL, NoSQL, GraphQL, etc.). | 2 / 3 |
Total | 7 / 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.