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
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 extremely thin and formulaic, appearing to be auto-generated boilerplate rather than a thoughtfully crafted skill description. It fails to describe any concrete capabilities, lacks meaningful trigger terms, and provides no guidance on when Claude should select this skill. The repeated identical trigger term suggests a template error.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Analyzes database connection pool configurations, detects connection leaks, measures pool utilization, and recommends optimal pool sizing parameters.'
Add a 'Use when...' clause with natural trigger terms like 'Use when the user asks about connection pool tuning, database connection issues, pool exhaustion, JDBC/HikariCP/DBCP configuration, or connection timeout problems.'
Include varied natural keywords users might actually say, such as 'database connections', 'pool size', 'connection leak', 'HikariCP', 'DBCP', 'connection timeout', 'pool exhaustion'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names a domain ('Connection Pool Analyzer') but describes no concrete actions. There are no specific capabilities listed such as analyzing pool sizes, detecting leaks, measuring connection wait times, or generating reports. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond naming itself, and the 'when' clause is essentially just restating the skill name as a trigger. There is no explicit 'Use when...' guidance with meaningful trigger scenarios. | 1 / 3 |
Trigger Term Quality | The trigger terms are just 'connection pool analyzer' repeated twice. It lacks natural variations users might say like 'connection pooling', 'database connections', 'pool size', 'connection timeout', 'connection leak', or 'JDBC pool'. | 1 / 3 |
Distinctiveness Conflict Risk | The term 'connection pool' is somewhat specific to a niche area, which provides some distinctiveness. However, the vague description and mention of 'Performance Testing' category could overlap with other performance testing 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 shell with no actual content. It consists entirely of generic boilerplate that repeats the skill name without providing any actionable information about connection pool analysis, performance testing techniques, or concrete tools/code. It fails on every dimension because it teaches Claude nothing.
Suggestions
Add concrete, executable code examples for connection pool analysis (e.g., k6 scripts to test pool exhaustion, JMeter configurations for connection pool monitoring, or Python scripts using psycopg2/HikariCP metrics).
Define a clear workflow: e.g., 1) Identify pool configuration, 2) Set up monitoring metrics, 3) Run load test with specific parameters, 4) Analyze results against thresholds, 5) Recommend tuning adjustments.
Include specific metrics and thresholds to monitor (e.g., pool wait time, active/idle connections, connection acquisition time, pool exhaustion events) with concrete examples of what good vs. bad looks like.
Remove all boilerplate sections ('When to Use', 'Example Triggers', 'Capabilities') that just restate the skill name and replace with actual technical content about connection pool analysis patterns.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and boilerplate. It explains nothing Claude doesn't already know and provides zero domain-specific information about connection pool analysis. Every section restates the skill name without adding substance. | 1 / 3 |
Actionability | There is no concrete guidance, no code, no commands, no specific techniques for analyzing connection pools. The content only describes what the skill claims to do in vague terms like 'provides step-by-step guidance' without actually providing any. | 1 / 3 |
Workflow Clarity | No workflow, steps, or process is defined. There are no instructions for how to actually perform connection pool analysis, no validation checkpoints, and no sequenced operations. | 1 / 3 |
Progressive Disclosure | The content is a flat, uninformative page with no references to detailed materials, no links to examples or configuration files, and no structured navigation to deeper content. | 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
3076d78
- 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.