timeout-handler
Timeout Handler - Auto-activating skill for API Integration. Triggers on: timeout handler, timeout handler Part of the API Integration skill category.
30
0%
Does it follow best practices?
Impact
80%
1.08xAverage 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/timeout-handler/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 extremely weak across all dimensions. It reads like an auto-generated stub with no substantive content — it names a category and repeats the skill name as a trigger term but provides zero information about what the skill does, what actions it performs, or when it should be selected. It would be nearly useless for Claude to differentiate this skill from others in a multi-skill environment.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Configures timeout durations for API requests, implements retry logic with exponential backoff, and handles connection timeout errors gracefully.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user mentions request timeouts, API timeout errors, retry logic, connection failures, or needs to set timeout limits for HTTP calls.'
Diversify trigger terms beyond just 'timeout handler' — include variations like 'request timeout', 'API timeout', 'connection timeout', 'retry on failure', 'timeout error', and 'backoff strategy'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the concept 'Timeout Handler' and mentions 'API Integration' as a category, but provides no concrete actions like 'set timeout limits', 'retry failed requests', or 'handle connection timeouts'. It is entirely vague about what the skill actually does. | 1 / 3 |
Completeness | The description fails to answer both 'what does this do' (no concrete actions described) and 'when should Claude use it' (no explicit 'Use when...' clause or equivalent trigger guidance). It only states a category label. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'timeout handler' repeated twice. There are no natural variations users might say such as 'request timeout', 'connection timeout', 'API timeout', 'retry logic', or 'timeout error'. | 1 / 3 |
Distinctiveness Conflict Risk | The description is too generic — 'API Integration' could overlap with many other API-related skills, and 'timeout handler' without specifics about what kind of timeout handling (HTTP, database, queue, etc.) makes it indistinguishable from other potential API or error-handling 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 placeholder that contains no actual technical content about timeout handling. It is entirely composed of meta-descriptions and trigger phrases, offering no actionable guidance, code examples, or concrete patterns for implementing timeout handlers in API integrations. It fails on every dimension of the rubric.
Suggestions
Add concrete, executable code examples showing timeout handler implementations (e.g., retry with exponential backoff, circuit breaker pattern, request timeout configuration for common HTTP libraries).
Define a clear workflow for implementing timeout handling: identify timeout scenarios → choose strategy → implement with specific code → validate behavior under failure conditions.
Replace the meta-description sections ('Capabilities', 'Example Triggers', 'When to Use') with actual technical content covering specific timeout patterns, configuration values, and error handling approaches.
Include specific examples for common API integration scenarios (e.g., webhook delivery timeouts, third-party API call timeouts, SDK client configuration) with copy-paste ready code.
| 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 information about 'timeout handler' without adding substance. | 1 / 3 |
Actionability | There is zero concrete guidance—no code, no commands, no specific patterns, no examples of timeout handling implementations. The content only describes what it could do rather than actually doing it. | 1 / 3 |
Workflow Clarity | No workflow, steps, or process is defined. The skill claims to provide 'step-by-step guidance' but contains none. There are no validation checkpoints or any sequenced instructions. | 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 of information across sections. | 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.