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

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Quality

Content

65%

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 and well-sequenced with concrete commands and a strong error-reference table, but it is a lengthy monolith with implicit rather than explicit validation gates and no use of progressive disclosure to offload detail into bundle files.

Suggestions

Add explicit validation checkpoints (e.g. after sizing and after applying config, verify via a monitoring query before proceeding) to lift workflow clarity.

Move the error-handling table and/or worked examples into a referenced file under references/ and link to it from the body to improve progressive disclosure.

Trim the three Examples and the Error Handling table to the highest-value entries to reduce length without losing actionability.

Dimension	Reasoning	Score
Conciseness	The body is dense and substantive with no concept-padding fluff, but it is a long monolith whose full error table and three worked examples could be trimmed, matching 'mostly efficient but could be tightened' rather than the lean 'every token earns its place' anchor.	2 / 3
Actionability	It provides concrete SQL queries, exact config keys and values, a sizing formula with worked numbers, memory math, and a copy-paste-ready error-to-cause-to-solution table, matching 'fully executable code/commands; copy-paste ready'.	3 / 3
Workflow Clarity	Ten steps are clearly sequenced with monitoring and an error table for recovery, but validation checkpoints are reactive/implicit rather than explicit 'validate, only proceed if valid' gates; for database operations the rubric caps this at 2.	2 / 3
Progressive Disclosure	It is a single monolithic SKILL.md with the error reference, examples, and deep config all inline, and it does not reference the (placeholder) bundle files; well-organized with headers/tables but content that could be separate stays inline.	2 / 3
	Total	9 / 12 Passed

Description

75%

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 the connection-pooling niche with explicit trigger guidance and good distinctiveness, but its capability list leans on generic phrasing ('comprehensive guidance and automation') and the trigger terms lack common variations.

Suggestions

Replace 'comprehensive guidance and automation' with concrete actions such as 'size connection pools, configure PgBouncer/ProxySQL, and tune pool parameters'.

Add common trigger variations users would naturally say, e.g. 'connection pool', 'database connections', 'too many connections', or 'connection exhaustion'.

Tighten the prose so the 'what' reads as a crisp list of capabilities rather than a padded sentence.

Dimension	Reasoning	Score
Specificity	Names the domain and a couple of actions ('connection pooling and management', 'comprehensive guidance and automation'), but the latter is generic fluff and no list of multiple concrete actions is given, matching the 'names domain and some actions, but not comprehensive' anchor.	2 / 3
Completeness	It states what the skill does ('connection pooling and management') and gives an explicit when/trigger clause ('use when you need to work with connection management', 'Trigger with phrases like...'), clearly answering both what and when.	3 / 3
Trigger Term Quality	Includes relevant natural phrases ('manage connections', 'configure pooling', 'optimize connection usage'), but misses common variations like 'connection pool', 'database connections', or 'too many connections', matching the 'some relevant keywords but missing common variations' anchor.	2 / 3
Distinctiveness Conflict Risk	Scoped to database connection pooling with distinct, specific triggers ('manage connections', 'configure pooling'), giving it a clear niche unlikely to trigger for unrelated skills.	3 / 3
	Total	10 / 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
Commit: 2cafb23

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