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 is an extremely weak description that reads like auto-generated boilerplate rather than a useful skill description. It provides no concrete actions, no natural trigger terms, no 'when to use' guidance, and is too generic to be distinguishable from other API-related skills. It fails on every dimension of the rubric.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Configures HTTP client settings including base URLs, authentication headers, timeouts, retry policies, and proxy settings for API integrations.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user needs to set up HTTP client configuration, configure API request defaults, manage authentication tokens, or adjust connection settings.'
Remove the duplicate trigger term ('http client config' listed twice) and expand with natural variations users might say, such as 'REST client setup', 'API headers', 'HTTP timeout', 'request configuration'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions whatsoever. It only states 'Http Client Config' and 'API Integration' without describing what the skill actually does (e.g., configure HTTP clients, set headers, manage timeouts, etc.). | 1 / 3 |
Completeness | The description fails to answer both 'what does this do' and 'when should Claude use it'. There is no 'Use when...' clause and no explanation of capabilities beyond the vague category label 'API Integration'. | 1 / 3 |
Trigger Term Quality | The trigger terms are just 'http client config' repeated twice. These are not natural phrases users would say; users are more likely to say things like 'configure API requests', 'set HTTP headers', 'REST client setup', or 'API authentication'. | 1 / 3 |
Distinctiveness Conflict Risk | 'API Integration' is extremely broad and could conflict with many other skills involving APIs, REST calls, HTTP requests, or web services. Nothing distinguishes this skill's specific niche. | 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 placeholder with no substantive content. It contains only boilerplate meta-descriptions that repeat the phrase 'http client config' without ever explaining what an HTTP client config is, how to create one, or providing any actionable code, commands, or configuration examples. It fails on every dimension of the rubric.
Suggestions
Add concrete, executable code examples showing HTTP client configuration (e.g., timeout settings, retry policies, connection pooling, TLS config) in at least one language/framework.
Define a clear workflow for configuring an HTTP client: e.g., 1) Choose base settings, 2) Configure timeouts/retries, 3) Set authentication, 4) Validate with a test request.
Remove all boilerplate meta-sections ('When to Use', 'Example Triggers', 'Capabilities') and replace with actual technical content—specific patterns, code snippets, and configuration examples.
If the skill covers multiple frameworks or patterns, create referenced sub-files (e.g., AXIOS.md, FETCH.md, RETRY_PATTERNS.md) and link to them from a concise overview.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and boilerplate. It explains nothing Claude doesn't already know, repeats 'http client config' excessively, and provides zero domain-specific information. Every section restates the same vague idea. | 1 / 3 |
Actionability | There are no concrete code examples, commands, configurations, or specific instructions. The skill describes what it could do in abstract terms ('provides step-by-step guidance') without actually providing any guidance whatsoever. | 1 / 3 |
Workflow Clarity | No workflow, steps, or process is defined. There are no sequences, validation checkpoints, or any procedural content at all—just meta-descriptions of capabilities. | 1 / 3 |
Progressive Disclosure | No bundle files exist, no references to external documents, and the content itself is a flat, shallow placeholder with no meaningful structure or navigation to deeper material. | 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.