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.
36
Quality
3%
Does it follow best practices?
Impact
100%
1.26xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/10-performance-testing/database-query-profiler/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 severely underdeveloped, consisting only of the skill name, a redundant trigger term, and a category label. It provides no information about what the skill actually does, what specific capabilities it offers, or when Claude should select it. Users searching for query optimization help would have no way to know this skill could help them.
Suggestions
Add specific concrete actions the skill performs, such as '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 'slow query', 'query performance', 'SQL optimization', 'database bottleneck', 'explain plan', or 'query execution time'
Remove the duplicate trigger term and replace with varied natural language phrases users would actually say when needing database query profiling help
| 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 both 'what does this do' and 'when should Claude use it'. It only states the category ('Performance Testing') without explaining capabilities or providing explicit trigger guidance beyond the redundant skill name. | 1 / 3 |
Trigger Term Quality | The trigger terms listed are just the skill name repeated twice ('database query profiler, database query profiler'). This provides no natural keyword variations users might say like 'slow query', 'SQL performance', 'query optimization', 'explain plan', or 'database bottleneck'. | 1 / 3 |
Distinctiveness Conflict Risk | The term 'Database Query Profiler' is somewhat specific to database performance analysis, which provides some distinctiveness. However, without concrete actions described, it could overlap with general database skills or other performance testing tools. | 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 a placeholder template with no actual content. It describes what a database query profiler skill would do without providing any concrete guidance, code examples, tool usage, or workflows. The entire content could be replaced with actual profiling instructions, SQL EXPLAIN examples, or tool-specific commands.
Suggestions
Add concrete code examples for query profiling (e.g., EXPLAIN ANALYZE in PostgreSQL, query execution plans, slow query log analysis)
Include specific tool commands or configurations (e.g., pg_stat_statements setup, MySQL slow query log configuration, or profiling with k6/JMeter as mentioned in tags)
Define a clear workflow: identify slow queries → analyze execution plan → optimize → validate improvement
Remove all generic boilerplate sections (Purpose, When to Use, Capabilities, Example Triggers) and replace with actionable content
| 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 filler with no actionable information. | 1 / 3 |
Actionability | No concrete code, commands, or specific guidance is provided. The skill describes what it does abstractly ('provides step-by-step guidance') but never actually provides any guidance, examples, or executable content. | 1 / 3 |
Workflow Clarity | No workflow, steps, or process is defined. The content only describes capabilities in vague terms without any actual sequence of actions for database query profiling. | 1 / 3 |
Progressive Disclosure | No structure beyond generic headings. No references to detailed documentation, no examples, and no navigation to related materials despite mentioning 'Related Skills' without linking to them. | 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
0c08951
- 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.