optimizing-database-connection-pooling
This skill optimizes database connection pooling for enhanced performance and resource management. It is activated when the user requests assistance with connection pooling, database performance tuning, or connection lifecycle management. Use this skill to implement and configure connection pools in various programming languages, identify optimal pool settings, and troubleshoot common connection-related issues. The skill is triggered by phrases like "connection pooling," "optimize database connections," or "improve database performance with connection pool."
- License 许可
- MIT
- 最近更新
- 2026-11-12
- Stars
- ★ 2
- Forks
- 0
01 前言 Front Matter
- name
- optimizing-database-connection-pooling
- description
- This skill optimizes database connection pooling for enhanced performance and resource management. It is activated when the user requests assistance with connection pooling, database performance tuning, or connection lifecycle management. Use this skill to implement and configure connection pools in various programming languages, identify optimal pool settings, and troubleshoot common connection-related issues. The skill is triggered by phrases like "connection pooling," "optimize database connections," or "improve database performance with connection pool."
03 SKILL.md 正文
Overview
This skill enables Claude to generate and configure database connection pools, ensuring optimal performance and resource utilization. It provides guidance on selecting appropriate pool settings, managing connection lifecycles, and monitoring pool performance.
How It Works
- Identify Requirements: Analyzes the user's request to determine the target database, programming language, and performance goals.
- Generate Configuration: Creates a connection pool configuration tailored to the specified environment, including settings for minimum and maximum pool size, connection timeout, and other relevant parameters.
- Implement Monitoring: Sets up monitoring for key pool metrics, such as connection usage, wait times, and error rates.
When to Use This Skill
This skill activates when you need to:
- Implement connection pooling for a database application.
- Optimize existing connection pool configurations.
- Troubleshoot connection-related performance issues.
Examples
Example 1: Implementing Connection Pooling in Python
User request: "Implement connection pooling in Python for a PostgreSQL database to improve performance."
The skill will:
- Generate a Python code snippet using a connection pool library like
psycopg2orSQLAlchemy. - Configure the connection pool with optimal settings for the PostgreSQL database, such as maximum pool size and connection timeout.
Example 2: Optimizing Connection Pool Configuration in Java
User request: "Optimize the connection pool configuration in my Java application using HikariCP to reduce connection wait times."
The skill will:
- Analyze the existing HikariCP configuration.
- Suggest adjustments to parameters like minimum idle connections, maximum pool size, and connection timeout to minimize wait times.
Best Practices
- Connection Timeout: Set a reasonable connection timeout to prevent indefinite waiting.
- Pool Size: Adjust the pool size based on the application's workload and database server capacity.
- Connection Testing: Implement connection validation to ensure connections are still valid before use.
Integration
This skill can integrate with other Claude Code plugins for database management, code generation, and performance monitoring to provide a comprehensive solution for database optimization.
04 同仓库更多 Skills
Docs Research
Use MCP Central Docs server to search, ask, and retrieve documentation (FastMCP, standards, packaging).
wrappee-drift
Read-only, single-repo audit of a repo's tool coverage against the software it wraps (its current real API/docs, not training-data memory) and against comparable/competing wrappers. Trigger when the user says "wrappee drift" followed by a repo name, "capability audit" followed by a repo name, or asks whether a repo is missing features the wrapped software or a competitor now has. Always scoped to one named repo per invocation -- never trigger this fleet-wide or unprompted; that is explicitly against the SOP. Do NOT trigger for internal fleet-standard compliance (that is drift-scan) or strategic worth/archive decisions (that is quality-check) -- this is specifically about the gap between the repo's tool list and the wrapped software's/competitors' actual current capabilities.
modules
暂无简介
mcp-standards
Use when developing MCP servers to access comprehensive standards for scaffolding, packaging, sampling, documentation, testing, error handling, monitoring, and CI/CD workflows.
webapp-cua-test
Run the pre-Tauri CUA click-through test (real browser, dev stack, OCR "Connected" wait, sidebar nav walk) for a fleet MCP server repo under D:\Dev\repos. Trigger when the user says "cua webapp test" or "webapp clickthrough" followed by a repo name, asks for an e2e click-through of a webapp, or asks whether a webapp boots and connects in a real browser. Not for the installed NSIS app (that is the nsis-build skill / cua-nsis-test) and not for DOM assertions (Playwright), and not for hunting fake data or dead buttons (fakefind).
ship
Final release gate for a fleet MCP server repo under D:\Dev\repos -- run all quality gates, build the release artifact, verify it, commit, push, and cut a GitHub release. Trigger this whenever the user says "ship it", "ship" followed by a repo name, "release" followed by a repo name, or asks to finalize and publish work that's already been done in a repo. This is the terminal step after assfix/nsis-build, not a substitute for them -- if the repo hasn't been assessed recently, say so before shipping rather than shipping blind.