http-client-config
Http Client Config - Auto-activating skill for API Integration. Triggers on: http client config, http client config Part of the API Integration skill category.
34
0%
Does it follow best practices?
Impact
100%
1.04xAverage 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/http-client-config/SKILL.mdQuality
Discovery
0%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 essentially a label with no substantive content. It fails to describe what the skill actually does, provides no natural trigger terms beyond a repeated phrase, and lacks any explicit guidance on when Claude should select it. It would be nearly indistinguishable from other API-related skills.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Configures HTTP client settings including timeouts, retry policies, base URLs, authentication headers, and proxy settings.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user needs to set up HTTP clients, configure API request defaults, manage connection pooling, or adjust REST client settings.'
Remove the duplicate trigger term ('http client config' is listed twice) and expand with natural variations users would say, such as 'HTTP requests', 'API client setup', 'REST configuration', 'request headers', 'connection timeout'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description provides no concrete actions. 'Http Client Config' and 'API Integration' are domain labels but no specific capabilities like 'configure timeouts', 'set headers', 'manage authentication' are mentioned. | 1 / 3 |
Completeness | Neither 'what does this do' nor 'when should Claude use it' is meaningfully answered. There is no 'Use when...' clause and no description of actual functionality beyond the category label. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'http client config' repeated twice. Missing natural variations users would say like 'HTTP request', 'API client', 'REST client', 'configure HTTP', 'request headers', 'connection settings', etc. | 1 / 3 |
Distinctiveness Conflict Risk | 'API Integration' is extremely broad and could conflict with many other skills. 'Http Client Config' is slightly more specific but without concrete actions or clear scope, it remains ambiguous and could overlap with general API, networking, or configuration skills. | 1 / 3 |
Total | 4 / 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 template/placeholder with no actual technical content. It repeatedly references 'http client config' without ever defining what that means, how to do it, or providing any concrete guidance. It fails on every dimension because it contains no actionable information whatsoever.
Suggestions
Add concrete, executable code examples showing HTTP client configuration (e.g., configuring timeouts, retries, base URLs, authentication headers) in at least one language/framework.
Define a clear workflow for setting up an HTTP client: e.g., 1) Choose library, 2) Configure base settings, 3) Add authentication, 4) Set up error handling/retries, 5) Validate with a test request.
Remove all meta-description sections ('When to Use', 'Example Triggers', 'Capabilities') that describe the skill itself rather than teaching how to perform the task.
Add specific guidance for common HTTP client libraries (e.g., axios, requests, HttpClient) with production-ready configuration patterns including timeouts, retry policies, and connection pooling.
| 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. Every section restates the same vague idea ('http client config') without adding substance. | 1 / 3 |
Actionability | There is zero concrete guidance—no code examples, no specific commands, no configuration snippets, no library recommendations. The content only describes rather than instructs, offering nothing executable or copy-paste ready. | 1 / 3 |
Workflow Clarity | No workflow steps are defined at all. The skill claims to provide 'step-by-step guidance' but contains none. There are no sequences, validation checkpoints, or any procedural content. | 1 / 3 |
Progressive Disclosure | The content is a flat, repetitive structure with no references to detailed materials, no links to related files, and no meaningful organization beyond boilerplate headings that all say the same thing. | 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
c8a915c
- 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.