database-query-profiler
Database Query Profiler - Auto-activating skill for Performance Testing. Triggers on: database query profiler, database query profiler Part of the Performance Testing skill category.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill database-query-profilerOverall
score
19%
Does it follow best practices?
Validation for skill structure
Activation
7%This description is essentially a placeholder that provides almost no useful information for skill selection. It only states the skill name and category without describing capabilities, use cases, or natural trigger terms. Claude would have difficulty knowing when to select this skill over others or understanding what it actually does.
Suggestions
Add specific actions the skill performs, e.g., 'Analyzes SQL query execution plans, identifies slow queries, measures query performance metrics, and suggests index optimizations.'
Include a 'Use when...' clause with natural trigger terms like 'Use when the user mentions slow queries, query optimization, database performance, execution plans, SQL profiling, or needs to analyze query bottlenecks.'
Remove the duplicate trigger term and expand with variations users would naturally say: 'query performance', 'slow database', 'optimize SQL', 'query analysis', 'database profiling'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Database Query Profiler') without describing any concrete actions. There are no verbs indicating what the skill actually does - no mention of analyzing queries, identifying bottlenecks, measuring execution time, or any other specific capabilities. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name, and provides no 'when should Claude use it' guidance. There is no 'Use when...' clause or equivalent explicit trigger guidance. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'database query profiler' repeated twice, which is the skill name itself. Missing natural user terms like 'slow query', 'query performance', 'SQL optimization', 'execution plan', 'database bottleneck', or 'query analysis'. | 1 / 3 |
Distinctiveness Conflict Risk | While 'Database Query Profiler' is somewhat specific to a niche (database performance), the lack of detail means it could overlap with general database skills, SQL skills, or other performance testing tools. The category mention helps slightly but doesn't provide clear boundaries. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%This skill content is essentially a placeholder template with no actual substance. It contains no executable code, no specific profiling techniques, no tool recommendations (like EXPLAIN ANALYZE, pg_stat_statements, slow query logs), and no actionable guidance. The entire content could be replaced with 'This skill helps with database query profiling' without losing any information.
Suggestions
Add concrete code examples for common profiling scenarios (e.g., PostgreSQL EXPLAIN ANALYZE, MySQL slow query log analysis, query plan interpretation)
Include specific tool recommendations with executable commands (e.g., pgBadger, pt-query-digest, database-specific profiling extensions)
Provide a clear workflow: identify slow queries → analyze execution plans → identify bottlenecks → optimize → validate improvements
Remove all generic boilerplate ('provides automated assistance', 'follows best practices') and replace with actual profiling techniques and metrics to look for
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains nothing Claude doesn't already know. Phrases like 'provides automated assistance' and 'follows industry best practices' are meaningless filler with no actual information about database query profiling. | 1 / 3 |
Actionability | There is zero concrete guidance - no code, no commands, no specific tools, no actual profiling techniques. The content describes what the skill supposedly does but never instructs how to actually profile database queries. | 1 / 3 |
Workflow Clarity | No workflow is provided whatsoever. There are no steps for profiling queries, no validation checkpoints, and no process to follow. The 'Capabilities' section promises 'step-by-step guidance' but delivers 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 profiling documentation or tools. | 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.