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 description is extremely weak across all dimensions. It reads as auto-generated boilerplate that merely restates the skill name without describing any concrete capabilities, use cases, or meaningful trigger terms. It would be nearly useless for Claude to distinguish this skill from others or know when to select it.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Configures database connection pool settings including pool size, idle timeout, max connections, and connection lifecycle management.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about database connection pooling, pool size tuning, connection timeouts, max connections, HikariCP config, or connection pool optimization.'
Include diverse natural keywords users would actually say, such as 'database pool', 'connection limit', 'pool size', 'idle connections', 'connection reuse', and specific technologies like 'HikariCP', 'c3p0', 'pgbouncer' if applicable.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the topic 'Connection Pooling Config' but lists no concrete actions like configuring pool sizes, setting timeouts, managing connections, or tuning parameters. It is entirely abstract. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond naming the topic, and the 'when' clause is essentially just restating the skill name as a trigger. There is no explicit 'Use when...' guidance with meaningful context. | 1 / 3 |
Trigger Term Quality | The trigger terms are just 'connection pooling config' repeated twice. It misses natural variations users would say like 'database pool', 'connection pool size', 'pool timeout', 'max connections', 'db connection management', etc. | 1 / 3 |
Distinctiveness Conflict Risk | The topic 'connection pooling config' is somewhat specific and unlikely to conflict with many other skills, but the vague 'API Integration' category and lack of concrete scope could cause overlap with general database configuration or API setup skills. | 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 essentially a placeholder template with no substantive content. It contains no actual guidance on connection pooling configuration—no code examples, no configuration parameters, no specific tools or libraries, and no workflow steps. The entire body is meta-description about what the skill theoretically does rather than actually doing it.
Suggestions
Add concrete, executable code examples for connection pooling configuration (e.g., configuring pool size, timeout, max connections for common libraries like SQLAlchemy, HikariCP, or HTTP client pools)
Include specific configuration parameters with recommended values and their tradeoffs (e.g., min/max pool size, idle timeout, connection lifetime)
Define a clear workflow for diagnosing and configuring connection pools: assess requirements → configure pool → validate with load testing → monitor in production
Remove all meta-description sections (Purpose, When to Use, Capabilities, Example Triggers) and replace with actionable technical content
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and meta-description. It explains what the skill does in abstract terms without providing any actual technical content about connection pooling configuration. Every section restates the same vague information. | 1 / 3 |
Actionability | There is zero concrete guidance—no code, no commands, no configuration examples, no specific parameters or settings. The skill describes rather than instructs, offering only vague promises like 'provides step-by-step guidance' without actually providing any. | 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. | 1 / 3 |
Progressive Disclosure | The content is a flat, repetitive structure with no meaningful organization. There are no references to detailed materials, no links to related files, and the sections contain redundant information rather than progressively deeper content. | 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
b8a3b3e
- 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.