optimizing-database-connection-pooling
tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill optimizing-database-connection-poolingProcess use when you need to work with connection management. This skill provides connection pooling and management with comprehensive guidance and automation. Trigger with phrases like "manage connections", "configure pooling", or "optimize connection usage".
Validation
81%| Criteria | Description | Result |
|---|---|---|
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 |
Total | 13 / 16 Passed | |
Implementation
20%This skill is a generic template with no actual connection pooling content. It describes a general software development process that could apply to any task, without providing any specific guidance on connection pool configuration, sizing, timeout settings, library usage (like HikariCP, PgBouncer, etc.), or monitoring pool health. The skill fails to teach Claude anything it doesn't already know.
Suggestions
Add concrete code examples showing how to configure connection pools in specific libraries (e.g., HikariCP, PgBouncer, SQLAlchemy pool settings) with actual configuration parameters
Include specific pool sizing formulas, timeout recommendations, and validation queries for health checks
Replace generic process steps with pooler-specific guidance like 'Set minPoolSize to 5, maxPoolSize to 20, connectionTimeout to 30000ms' with explanations of when to adjust these values
Add executable diagnostic commands to check pool health, identify connection leaks, and monitor pool metrics
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose with generic boilerplate that applies to any task. Contains no database connection pooler-specific information - just generic software development process steps that Claude already knows. | 1 / 3 |
Actionability | No concrete code, commands, or specific examples for connection pooling. Everything is abstract guidance like 'Review current configuration' and 'Execute implementation' without any actual pooler configuration, SQL, or library usage. | 1 / 3 |
Workflow Clarity | Steps are clearly numbered and sequenced with validation checkpoints mentioned, but the workflow is entirely generic and not specific to connection pooling. No actual validation commands or pooler-specific checks are provided. | 2 / 3 |
Progressive Disclosure | References external files for templates, docs, and examples, but the main content is a wall of generic text. The referenced files use placeholder paths and the skill body itself contains no useful quick-start content. | 2 / 3 |
Total | 6 / 12 Passed |
Activation
40%This description suffers from vague, buzzword-heavy language ('comprehensive guidance and automation') without specifying concrete actions. While it includes explicit trigger phrases which is positive, the actual capabilities remain unclear. The description would benefit from listing specific operations and clarifying what type of connections (database, network, API) it handles.
Suggestions
Replace vague phrases like 'comprehensive guidance and automation' with specific actions such as 'create connection pools, monitor active connections, configure timeout settings, handle connection failures'
Specify the type of connections this skill handles (database, HTTP, WebSocket, etc.) to improve distinctiveness and help users understand when to use it
Add more natural trigger terms users might say, such as 'database pool', 'connection timeout', 'max connections', or specific technology names like 'PostgreSQL connections'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague language like 'work with connection management' and 'comprehensive guidance and automation' without listing any concrete actions. No specific capabilities like 'create pools', 'monitor connections', or 'handle timeouts' are mentioned. | 1 / 3 |
Completeness | Has explicit trigger phrases which partially addresses 'when', but the 'what' is extremely weak - 'connection pooling and management with comprehensive guidance' is too vague to understand actual capabilities. | 2 / 3 |
Trigger Term Quality | Includes some relevant trigger phrases ('manage connections', 'configure pooling', 'optimize connection usage') but these are somewhat technical. Missing common variations users might say like 'database connections', 'connection limits', 'pool size', or specific technologies. | 2 / 3 |
Distinctiveness Conflict Risk | The focus on 'connection pooling' provides some specificity, but 'connection management' is broad enough to potentially overlap with database skills, network skills, or API management skills. | 2 / 3 |
Total | 7 / 12 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.