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.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill http-client-configOverall
score
17%
Does it follow best practices?
Validation for skill structure
Activation
0%This description is severely underdeveloped, consisting mainly of a title and category label with no substantive content. It fails to explain what the skill actually does, provides no natural trigger terms users would say, and lacks any 'Use when' guidance. The repeated trigger term and generic category make it nearly useless for skill selection.
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 natural keywords users would actually say: 'API settings', 'request headers', 'connection timeout', 'HTTP configuration', 'REST client setup'
| 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 would conflict with many other API-related skills. Nothing distinguishes this from other HTTP, REST, or API configuration skills. | 1 / 3 |
Total | 4 / 12 Passed |
Implementation
0%This skill content is essentially a placeholder template with no actual technical value. It contains only meta-descriptions of what a skill should do without providing any concrete HTTP client configuration guidance, code examples, or actionable instructions. The content fails all dimensions by being verbose about nothing while providing zero practical information.
Suggestions
Add concrete, executable code examples showing HTTP client configuration (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) Choose client library, 2) Set base configuration, 3) Add authentication, 4) Configure error handling, 5) Validate with test request
Remove all boilerplate meta-descriptions and replace with actual technical content that teaches HTTP client configuration
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely boilerplate with no actual technical information. It repeats 'http client config' multiple times without providing any concrete guidance, wasting tokens on meta-descriptions rather than actionable content. | 1 / 3 |
Actionability | No concrete code, commands, or specific instructions are provided. The content only describes what the skill claims to do ('provides step-by-step guidance') without actually providing any guidance, examples, or executable content. | 1 / 3 |
Workflow Clarity | No workflow is defined. The skill mentions 'step-by-step guidance' but provides zero actual steps. There are no sequences, validation checkpoints, or processes described. | 1 / 3 |
Progressive Disclosure | The content is a flat, uninformative structure with no references to detailed materials, no links to related documentation, and no organization of content by complexity or use case. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
69%Validation — 11 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 11 / 16 Passed | |
- 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.