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.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill connection-pool-analyzerOverall
score
19%
Does it follow best practices?
Validation for skill structure
Activation
7%This description is severely underdeveloped, essentially serving as a placeholder rather than a functional skill description. It relies entirely on the skill name without explaining capabilities, use cases, or providing meaningful trigger terms. The auto-generated format with redundant triggers and category labeling adds no value for skill selection.
Suggestions
Add specific concrete 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 'Use when diagnosing connection pool issues, database connection timeouts, pool exhaustion, connection leaks, or optimizing pool size settings.'
Add varied trigger terms users would naturally say: 'database connections', 'pool exhaustion', 'connection timeout', 'max connections', 'idle connections', 'connection leak'.
| 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 mention of analyzing, monitoring, optimizing, or any specific capabilities. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name, and provides no 'when should Claude use it' guidance. There is no 'Use when...' clause or equivalent explicit trigger guidance. | 1 / 3 |
Trigger Term Quality | The trigger terms listed are redundant ('connection pool analyzer' repeated twice) and represent the skill name itself rather than natural user language. Missing terms users would actually say like 'database connections', 'pool size', 'connection timeout', 'connection leaks', etc. | 1 / 3 |
Distinctiveness Conflict Risk | While 'connection pool' is a specific technical domain that provides some distinctiveness, the lack of detail about what aspects of connection pools it analyzes (database, HTTP, thread pools?) creates potential overlap with other performance or database-related skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%This skill is an empty template that provides no actual guidance on connection pool analysis. It contains only meta-descriptions of what a skill should do without any concrete technical content, code examples, or actionable instructions. The content would be identical if you replaced 'connection pool analyzer' with any other topic.
Suggestions
Add concrete code examples showing how to analyze connection pool metrics (e.g., pool size, wait times, connection leaks) using specific tools like k6, JMeter, or database-specific monitoring
Define a clear workflow with steps: 1) identify pool configuration, 2) set up monitoring, 3) run load test, 4) analyze metrics, 5) identify bottlenecks
Include specific metrics to monitor (active connections, idle connections, wait time, timeout rate) with threshold examples
Provide executable configuration snippets for common connection pool implementations (HikariCP, c3p0, database-native pools)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely boilerplate with no actual technical substance. It explains what the skill does in abstract terms without providing any concrete information about connection pool analysis that Claude doesn't already know. | 1 / 3 |
Actionability | No concrete code, commands, or executable guidance is provided. The content only describes what the skill claims to do ('provides step-by-step guidance', 'generates production-ready code') without actually providing any of it. | 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 structure beyond generic headings. No references to detailed materials, no examples, no links to related documentation. The content is a hollow template with no actual information to disclose. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
69%Validation — 11 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 11 / 16 Passed | |
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.