connection-pooling-config
Connection Pooling Config - Auto-activating skill for API Integration. Triggers on: connection pooling config, connection pooling config Part of the API Integration skill category.
36
3%
Does it follow best practices?
Impact
100%
1.03xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/16-api-integration/connection-pooling-config/SKILL.mdQuality
Discovery
7%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 is a very weak description that essentially just repeats the skill name without providing any meaningful detail about what the skill does or when it should be used. It lacks concrete actions, natural trigger terms, and explicit usage guidance, making it nearly useless for skill selection among multiple options.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Configures database connection pool settings including pool size, idle timeout, max lifetime, and connection validation parameters for API backends.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about database connection pools, pool sizing, max connections, connection timeouts, HikariCP, pgBouncer, or API backend database configuration.'
Remove the duplicate trigger term and replace with diverse natural language variations users might actually say, such as 'DB pool', 'connection limits', 'pool exhaustion', 'connection leak'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the topic 'Connection Pooling Config' but lists no concrete actions. There are no specific capabilities like 'configure pool sizes', 'set timeout parameters', or 'manage database connections'. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond naming the topic, and the 'when' clause is just a redundant repetition of the skill name rather than meaningful trigger guidance. There is no explicit 'Use when...' clause with real scenarios. | 1 / 3 |
Trigger Term Quality | The trigger terms are just 'connection pooling config' repeated twice. Missing natural variations users would say like 'database pool', 'connection pool size', 'max connections', 'pool timeout', 'DB connections', etc. | 1 / 3 |
Distinctiveness Conflict Risk | While 'connection pooling' is a somewhat specific domain, the description is so vague that it could overlap with general database configuration skills, API configuration skills, or infrastructure setup skills. The mention of 'API Integration' category adds slight context but doesn't clearly carve out a niche. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is an empty shell with no substantive content. It consists entirely of generic boilerplate that describes what a connection pooling config skill would do without providing any actual technical guidance, code examples, configuration snippets, or actionable instructions. It fails on every dimension of the rubric.
Suggestions
Add concrete, executable code examples for configuring connection pools (e.g., Python's `sqlalchemy.create_engine(pool_size=10, max_overflow=20)`, HikariCP config, or HTTP client pool settings with specific parameters).
Define a clear workflow: 1) Assess connection requirements, 2) Configure pool parameters (min/max size, timeout, idle settings), 3) Validate with a health check or test query, 4) Monitor pool metrics.
Remove all meta-description sections ('Purpose', 'When to Use', 'Capabilities', 'Example Triggers') and replace with actual technical content covering common pooling libraries, recommended defaults, and tuning guidance.
Include specific configuration examples for at least 2-3 common scenarios (database connection pools, HTTP client pools, Redis connection pools) with production-ready settings and explanations of key parameters.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and boilerplate. It explains nothing Claude doesn't already know, provides no specific technical content about connection pooling, and pads with generic meta-descriptions ('Provides step-by-step guidance', 'Follows industry best practices') that add zero value. | 1 / 3 |
Actionability | There is no concrete guidance whatsoever—no code, no commands, no configuration examples, no specific parameters or settings for connection pooling. The entire skill describes what it could do rather than instructing how to do anything. | 1 / 3 |
Workflow Clarity | No workflow, steps, or process is defined. There are no sequences, no validation checkpoints, and no actual instructions for configuring connection pooling. The phrase 'step-by-step guidance' is promised but never delivered. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of generic text with no structure pointing to detailed resources, no references to supporting files, and no meaningful organization beyond boilerplate headings. There are no bundle files to support it either. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
81%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 | |
- Commit
3a2d27d
- 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.