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.
34
0%
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
0%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 lacks concrete actions, natural trigger terms, explicit usage guidance, and any distinguishing detail that would help Claude select it appropriately from a pool of skills.
Suggestions
Add specific concrete actions the skill performs, 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 duplicate trigger term and expand the trigger list to include natural variations users would say, such as 'slow SQL', 'query tuning', 'database performance', 'index optimization', '.sql profiling'.
| 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. The phrase 'Auto-activating skill for Performance Testing' is vague and does not constitute a meaningful trigger condition. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'database query profiler' repeated twice. There are no natural user keywords like 'slow query', 'query performance', 'SQL optimization', 'explain plan', 'query execution time', or other terms users would naturally use when needing this skill. | 1 / 3 |
Distinctiveness Conflict Risk | The description is too vague to be distinctive. 'Performance Testing' is a broad category, and without specific actions or clear triggers, this could easily conflict with other performance-related skills (e.g., load testing, APM, general database skills). | 1 / 3 |
Total | 4 / 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 hollow template with no actual content. It contains only meta-descriptions of what the skill would do without providing any actionable guidance, code, commands, or concrete information about database query profiling. It fails on every dimension because it teaches nothing.
Suggestions
Add concrete, executable code examples for profiling database queries (e.g., EXPLAIN ANALYZE in PostgreSQL, slow query log configuration in MySQL, or using tools like pg_stat_statements).
Define a clear multi-step workflow for profiling queries: identify slow queries → analyze execution plans → optimize → validate improvements with benchmarks.
Remove the meta-description sections (When to Use, Example Triggers, Capabilities) and replace them with actual profiling techniques, tool configurations, and interpretation guidance.
Include specific tool integration examples (e.g., k6 database load testing scripts, JMeter JDBC sampler configurations) that align with the stated performance testing category.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler with no substantive information. It explains what the skill does in abstract terms without providing any actual guidance, commands, or code. Every section restates the same vague concept. | 1 / 3 |
Actionability | There is zero concrete, executable guidance. No code examples, no commands, no specific steps for profiling database queries. The content only describes what the skill could do rather than instructing how to do it. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. There are no steps, no sequence, no validation checkpoints. The 'Capabilities' section mentions 'step-by-step guidance' but none is actually provided. | 1 / 3 |
Progressive Disclosure | The content has section headers but they contain no meaningful content to organize. There are no references to detailed files, no examples, and no structured navigation to deeper material. | 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
c8a915c
- 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.