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

65%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./plugins/database/database-connection-pooler/skills/optimizing-database-connection-pooling/SKILL.md

Quality

Content

65%Weight 40%Scale 1-3

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

The content is highly actionable with concrete commands, formulas, and worked examples, and is well-sequenced. Its main gaps are the absence of explicit validation feedback loops in the database workflow and no use of progressive disclosure to offload the error reference and examples into bundle files.

Suggestions

Add explicit validation checkpoints, e.g. after changing max_connections or pool size, re-run the pg_stat_activity/Threads_connected audit to confirm headroom before proceeding.

Trim parenthetical over-explanations and condense the three narrative Examples to the essential numbers and outcomes.

Move the Error Handling table and worked Examples into files under references/ and link to them from the body to apply progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is mostly dense and actionable rather than padded with basics, but parenthetical over-explanations ('one backend connection serves many clients between transactions', 'fail fast rather than queue indefinitely') and lengthy narrative examples could be tightened.	2 / 3
Actionability	It provides executable SQL queries, a concrete pool-sizing formula with worked numbers, exact config values (minimumIdle 2-5, default_pool_size=20, max_client_conn=1000), and a memory-based max_connections calculation — copy-paste ready.	3 / 3
Workflow Clarity	The 10 steps are clearly sequenced with an audit baseline (step 1) and monitoring (step 8), but there is no explicit validate->fix->retry checkpoint; per the rubric, missing feedback loops in database-operation workflows caps this at 2.	2 / 3
Progressive Disclosure	Sections are well-organized, but the ~90-line body is monolithic with no file-level references or splitting of the Error Handling table and worked Examples into the (currently stub-only) references/ directory.	2 / 3
	Total	9 / 12 Passed

Description

65%Weight 40%Scale 1-3

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description covers a distinct niche and includes explicit trigger guidance, but it is weakened by a broken first sentence, second-person voice, and over-claimed fluff. Capability specifics are thin compared to the concrete actions the skill actually performs.

Suggestions

Rewrite in third person and replace fluff ('comprehensive guidance and automation') with concrete capabilities, e.g. 'Audits active connections, sizes connection pools per core count, and configures PgBouncer/ProxySQL'.

Fix the broken first sentence ('Process use when...') into a clean capability statement followed by a 'Use when...' clause.

Broaden trigger coverage with natural variations like 'connection pool', 'database connections', 'too many connections', and tool names ('PgBouncer', 'ProxySQL').

Dimension	Reasoning	Score
Specificity	It names the domain ('connection pooling and management') and a few generic verbs but pads with fluff ('comprehensive guidance and automation'); the second-person phrasing 'you need to work with' triggers the rubric's -1 voice penalty, dropping it from a base of 2 to 1.	1 / 3
Completeness	Both 'what' (connection pooling and management) and 'when' are explicitly stated, and the presence of an explicit 'Trigger with phrases like...' clause plus a 'use when'-type clause means completeness is not capped at 2.	3 / 3
Trigger Term Quality	It lists several natural phrases ('manage connections', 'configure pooling', 'optimize connection usage') but misses common variations a user would say ('connection pool', 'database connections', 'too many connections', 'PgBouncer'), so coverage is partial.	2 / 3
Distinctiveness Conflict Risk	Connection pooling is a clear, narrow niche and the triggers are pool/connection-focused, making unintended triggering of unrelated skills unlikely.	3 / 3
	Total	9 / 12 Passed

Validation

87%

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 — 14 / 16 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	14 / 16 Passed

Repository: jeremylongshore/claude-code-plugins-plus-skills
Path: plugins/database/database-connection-pooler/skills/optimizing-database-connection-pooling/SKILL.md
Commit: c4eafaf

Reviewed: 5 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.