connection-pool-analyzer
Connection Pool Analyzer - Auto-activating skill for Performance Testing. Triggers on: connection pool analyzer, connection pool analyzer Part of the Performance Testing skill category.
36
Quality
3%
Does it follow best practices?
Impact
100%
1.09xAverage 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/connection-pool-analyzer/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 placeholder that provides almost no useful information for skill selection. It names a category ('Performance Testing') and repeats the skill name as triggers, but fails to describe what the skill actually does, what problems it solves, or when Claude should select it over other skills.
Suggestions
Add specific actions the skill performs, e.g., 'Analyzes database connection pool metrics, identifies connection leaks, monitors pool utilization, and recommends optimal pool sizing configurations.'
Include a 'Use when...' clause with natural trigger terms like 'database connections slow', 'connection timeout errors', 'pool exhaustion', 'HikariCP', 'JDBC pool', or 'connection leak'.
Remove the duplicate trigger term and replace with varied natural language users would actually say when experiencing connection pool issues.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Connection Pool Analyzer') without describing any concrete actions. There are no verbs indicating what the skill actually does - no 'analyzes', 'monitors', 'optimizes', or similar action words. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name, and provides no 'when should Claude use it' guidance. The 'Triggers on' section just repeats the skill name rather than providing meaningful trigger scenarios. | 1 / 3 |
Trigger Term Quality | The trigger terms listed are just the skill name repeated twice ('connection pool analyzer, connection pool analyzer'). No natural user language like 'database connections', 'pool size', 'connection timeout', or 'db performance' is included. | 1 / 3 |
Distinctiveness Conflict Risk | The term 'Connection Pool Analyzer' is fairly specific to database/application performance domains, which provides some distinctiveness. However, without concrete actions described, it could overlap with other performance testing or database monitoring 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 template with no actual content about connection pool analysis. It contains only boilerplate descriptions of what a skill should do without any concrete guidance, code examples, metrics to monitor, or analysis techniques. The content provides zero value to Claude for performing connection pool analysis tasks.
Suggestions
Add concrete code examples for monitoring connection pool metrics (e.g., active connections, wait times, pool exhaustion)
Include specific commands or scripts for common connection pool analysis tools (e.g., database-specific monitoring queries, JMX metrics collection)
Define a clear workflow for diagnosing connection pool issues: identify symptoms → collect metrics → analyze patterns → recommend fixes
Add example output formats showing what healthy vs problematic connection pool metrics look like
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler text with no actual technical substance. It explains what the skill does in abstract terms without providing any concrete information about connection pool analysis. | 1 / 3 |
Actionability | No concrete code, commands, or executable guidance is provided. The content only describes vague capabilities ('provides step-by-step guidance', 'generates production-ready code') without actually delivering any of them. | 1 / 3 |
Workflow Clarity | No workflow, steps, or process is defined. The skill claims to provide 'step-by-step guidance' but contains zero actual steps for analyzing connection pools. | 1 / 3 |
Progressive Disclosure | No meaningful structure or references to additional resources. The content is a template placeholder with no actual technical content to organize or reference. | 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.