optimizing-database-connection-pooling

Process 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".

Quality

41%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./plugins/database/database-connection-pooler/skills/optimizing-database-connection-pooling/SKILL.md

Quality

Discovery

40%

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 vague and lacks concrete actions, relying on buzzwords like 'comprehensive guidance and automation' without specifying what the skill actually does. While it includes some trigger phrases, the domain is underspecified (what kind of connections?), and the capabilities listed are too abstract to help Claude distinguish this skill from other potentially related skills.

Suggestions

Replace vague language like 'comprehensive guidance and automation' with specific concrete actions (e.g., 'Configure connection pool sizes, manage idle/active connections, handle connection timeouts, monitor pool health').

Specify the type of connections this skill handles (e.g., database connections, HTTP connections, WebSocket connections) to reduce conflict risk with other skills.

Add more natural trigger terms users would actually say, such as 'connection pool size', 'too many connections', 'connection timeout', 'database pool', or specific technology names.

Dimension	Reasoning	Score
Specificity	The description uses vague language like 'connection pooling and management' and 'comprehensive guidance and automation' without listing any concrete actions. No specific operations (e.g., 'set pool size', 'monitor idle connections', 'handle timeouts') are mentioned.	1 / 3
Completeness	It attempts to answer both 'what' and 'when' — the 'what' is vague ('connection pooling and management') and the 'when' is present via trigger phrases, but the 'what' is too weak to earn full marks. The 'Use when' equivalent exists via 'Process use when' and 'Trigger with phrases like'.	2 / 3
Trigger Term Quality	It includes some relevant trigger phrases like 'manage connections', 'configure pooling', and 'optimize connection usage', but these are somewhat generic and miss common variations like 'database connections', 'connection pool size', 'connection timeout', or specific technologies.	2 / 3
Distinctiveness Conflict Risk	The term 'connection management' is somewhat specific but could overlap with database skills, network skills, or API management skills. It doesn't specify what type of connections (database, HTTP, WebSocket, etc.), creating potential conflict.	2 / 3
	Total	7 / 12 Passed

Implementation

42%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This skill provides solid domain knowledge about connection pooling with useful formulas, parameter recommendations, and error handling. However, it suffers from being a monolithic document without progressive disclosure, lacks executable configuration snippets (actual config files), and is missing validation checkpoints between steps that could cause production issues if done incorrectly.

Suggestions

Split detailed PgBouncer, ProxySQL, and application pool configurations into separate referenced files (e.g., PGBOUNCER.md, PROXYSQL.md) with the SKILL.md serving as an overview with navigation links.

Add executable configuration file examples — a complete pgbouncer.ini snippet, ProxySQL SQL setup commands, and a Spring Boot application.yml block — instead of listing parameters in prose.

Add explicit validation checkpoints after key steps, e.g., 'After configuring PgBouncer, verify with: `psql -h pgbouncer_host -p 6432 pgbouncer -c "SHOW POOLS"` — confirm active connections match expectations before proceeding.'

Trim the parenthetical explanations in the monitoring section (e.g., '(saturation indicator)') and the narrative examples into more concise tabular or bullet formats.

Dimension	Reasoning	Score
Conciseness	The content is reasonably efficient but includes some explanatory padding (e.g., explaining what transaction pooling mode does, describing what each metric indicates in parentheses). Some sections like the examples are verbose narratives rather than concise reference material. However, most content is genuinely informative and not explaining things Claude would already know.	2 / 3
Actionability	Provides specific SQL queries, formulas, and configuration parameter names with recommended values, which is good. However, it lacks executable configuration file examples (no actual PgBouncer .ini snippet, no ProxySQL SQL commands, no Spring Boot YAML/properties). The guidance is concrete but stops short of copy-paste ready configuration blocks.	2 / 3
Workflow Clarity	The 10-step sequence is logically ordered (audit → calculate → configure → deploy → monitor), but there are no explicit validation checkpoints or feedback loops. After configuring PgBouncer or changing pool sizes, there's no 'verify by running X' step. For operations that can cause connection exhaustion or outages, this is a significant gap.	2 / 3
Progressive Disclosure	The skill is a monolithic wall of text with no bundle files and no references to separate detailed guides. PgBouncer configuration, ProxySQL setup, application pool configuration, and monitoring queries could each be separate referenced files. Everything is inline in one long document, making it hard to navigate.	1 / 3
	Total	7 / 12 Passed

Validation

81%

Warnings & errors only

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

Repository: jeremylongshore/claude-code-plugins-plus-skills
Commit: 69c73e9

Reviewed: 4 days ago

Table of Contents

Discovery Implementation Validation

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.