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
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 essentially a title and category label with no substantive content. It fails to describe any concrete actions the skill performs, lacks natural trigger terms users would use, and provides no explicit guidance on when Claude should select it. It reads like auto-generated boilerplate rather than a useful skill description.
Suggestions
Add concrete actions describing what the skill does, e.g., 'Profiles database query execution plans, identifies slow queries, analyzes index usage, and recommends query optimizations.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user mentions slow queries, query performance, SQL optimization, explain plans, query execution time, or database bottlenecks.'
Remove the redundant duplicate trigger term and expand with varied natural language phrases users would actually say when needing this skill.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names a domain ('Database Query Profiler') but provides no concrete actions. There is no mention of what the skill actually does—no verbs like 'analyze', 'profile', 'optimize', or 'measure'. It is essentially just a label with no capability description. | 1 / 3 |
Completeness | The description fails to answer both 'what does this do' and 'when should Claude use it'. There is no explanation of capabilities and no explicit 'Use when...' clause—only a vague category label and a redundant trigger line. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'database query profiler' repeated twice. This misses natural user phrases like 'slow query', 'query performance', 'explain plan', 'SQL optimization', 'query execution time', or 'database profiling'. Users rarely say 'database query profiler' verbatim. | 1 / 3 |
Distinctiveness Conflict Risk | The term 'Database Query Profiler' is somewhat specific to a niche (database performance profiling), which reduces conflict with unrelated skills. However, the lack of concrete actions and the generic 'Performance Testing' category could cause overlap with other performance-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 placeholder that provides no actionable content whatsoever. It describes what a database query profiler skill would do in abstract terms but contains no actual instructions, code, commands, tool references, or workflows. It fails on every dimension because it teaches Claude nothing it doesn't already know.
Suggestions
Add concrete, executable examples of database query profiling (e.g., EXPLAIN ANALYZE in PostgreSQL, slow query log analysis in MySQL, using pg_stat_statements, or k6/JMeter database load test configurations).
Define a clear multi-step workflow for profiling queries, including steps like identifying slow queries, running EXPLAIN plans, interpreting results, and validating optimizations with before/after benchmarks.
Remove the meta-description sections (Purpose, When to Use, Capabilities, Example Triggers) and replace them with actual instructional content—specific commands, code snippets, and tool usage patterns.
If the skill is meant to cover multiple databases or tools, create a concise overview with references to separate files for each (e.g., POSTGRES_PROFILING.md, MYSQL_PROFILING.md) to support progressive disclosure.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic filler that tells Claude nothing useful. Phrases like 'Provides step-by-step guidance' and 'Follows industry best practices' are vague platitudes. The entire file explains what the skill is rather than providing any actual instruction or knowledge. | 1 / 3 |
Actionability | There is zero concrete, executable guidance—no code, no commands, no specific techniques for database query profiling. The content only describes the skill abstractly without instructing Claude how to actually perform any profiling task. | 1 / 3 |
Workflow Clarity | No workflow, steps, or process is defined. There are no sequences, validation checkpoints, or any procedural content whatsoever. The skill claims to provide 'step-by-step guidance' but delivers none. | 1 / 3 |
Progressive Disclosure | There are no references to supporting files, no structured navigation, and no bundle files. The content is a shallow placeholder with no depth or layered information architecture. | 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
22f797a
- 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.