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
Quality
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 severely underdeveloped, consisting primarily of auto-generated boilerplate with no substantive content. It fails to explain what the skill actually does, provides no natural trigger terms users would say, and lacks any explicit guidance on when Claude should select this skill. The repeated trigger term suggests a template error.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Configures HTTP client settings including timeouts, headers, authentication, retry policies, and proxy settings'
Include a 'Use when...' clause with natural trigger terms like 'Use when configuring API connections, setting request headers, managing HTTP timeouts, or troubleshooting REST client issues'
Add file type or technology-specific triggers to distinguish from other API skills, e.g., 'axios config', 'fetch options', 'HttpClient settings', '.http files'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions - only 'Auto-activating skill for API Integration' which is vague and abstract. No specific capabilities like 'configure timeouts', 'set headers', or 'manage authentication' are mentioned. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond a vague category label, and has no 'Use when...' clause or explicit trigger guidance. Both what and when are very weak or missing. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'http client config' repeated twice, which is technical jargon. Missing natural user terms like 'API settings', 'request configuration', 'connection settings', 'REST client', or 'HTTP headers'. | 1 / 3 |
Distinctiveness Conflict Risk | 'API Integration' is extremely generic and could conflict with many skills involving APIs, REST calls, webhooks, or any HTTP-related functionality. No clear niche is established. | 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 a placeholder template with no actual technical content. It describes what an HTTP client config skill should do without providing any concrete guidance, code examples, configuration patterns, or actionable instructions. The entire content is meta-description that adds no value beyond what Claude already knows.
Suggestions
Add concrete HTTP client configuration examples with executable code (e.g., timeout settings, retry logic, connection pooling, authentication headers)
Include specific configuration patterns for common HTTP clients (requests, httpx, aiohttp) with copy-paste ready snippets
Define a clear workflow for configuring HTTP clients: 1) Base config, 2) Authentication, 3) Retry/timeout policies, 4) Validation/testing
Remove all meta-description content ('This skill provides...', 'When to use...') and replace with actual technical guidance
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler with no actual technical substance. It explains what the skill does in abstract terms without providing any concrete HTTP client configuration guidance, wasting tokens on meta-description rather than actionable content. | 1 / 3 |
Actionability | No concrete code, commands, or specific examples are provided. The content only describes what the skill could do ('provides step-by-step guidance') without actually providing any guidance, configuration examples, or executable instructions. | 1 / 3 |
Workflow Clarity | No workflow is defined. There are no steps, no sequence, and no validation checkpoints. The skill claims to provide 'step-by-step guidance' but contains zero actual steps for HTTP client configuration. | 1 / 3 |
Progressive Disclosure | No structure for progressive disclosure exists. There are no references to detailed documentation, no links to examples or advanced topics, and the content is a flat, uninformative placeholder with no navigation to actual technical 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
0c08951
- 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.