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 is an extremely weak, likely auto-generated description that provides almost no useful information for skill selection. It lacks concrete actions, meaningful trigger terms, explicit 'when to use' guidance, and any distinguishing details. The repeated trigger term 'timeout handler' twice is a clear sign of template-based generation without human refinement.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Configures timeout limits for API requests, implements retry logic with exponential backoff, and handles connection timeout errors gracefully.'
Add a 'Use when...' clause with natural trigger terms like 'Use when the user needs to handle API timeouts, set request time limits, implement retry strategies, or troubleshoot connection timeout errors.'
Include natural keyword variations users might say: 'request timeout', 'API timeout', 'connection timeout', 'retry logic', 'timeout error', 'slow API response', 'hanging request'.
| 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 'what does this do' beyond the name itself, and the 'when' guidance is limited to a redundant trigger phrase. There is no explicit 'Use when...' clause or meaningful trigger guidance. | 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'. The repetition suggests auto-generated content with no thought to user language. | 1 / 3 |
Distinctiveness Conflict Risk | The description is so vague that it could overlap with any API-related skill. 'API Integration' is a broad category, and without specific actions or clear scope, it would be difficult to distinguish this from other API error handling or retry 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 shell with no substantive content. It contains only generic boilerplate descriptions that could apply to literally any topic, with no actual timeout handling guidance, code examples, patterns, or technical information. It fails on every dimension because it teaches Claude nothing actionable about timeout handlers or API integration.
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: e.g., 1) identify timeout scenarios, 2) choose strategy, 3) implement with specific code, 4) validate with test cases.
Replace all generic placeholder text with specific technical content about timeout patterns (connection timeouts, read timeouts, idle timeouts), including concrete configuration values and error handling examples.
Remove the meta-description sections ('When to Use', 'Example Triggers', 'Capabilities') that waste tokens on self-description rather than providing actionable technical guidance.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and boilerplate. It explains nothing Claude doesn't already know, provides no specific technical content about timeout handling, and every section is generic placeholder text that could apply to any skill. | 1 / 3 |
Actionability | There is zero concrete guidance—no code, no commands, no specific timeout patterns, no configuration examples, no API-specific instructions. Every bullet point is vague and abstract (e.g., 'Provides step-by-step guidance' without any actual steps). | 1 / 3 |
Workflow Clarity | No workflow is defined at all. There are no steps, no sequence, no validation checkpoints. The skill claims to provide 'step-by-step guidance' but contains none. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of generic text with no references to supporting files, no structured navigation, and no meaningful content organization. There are no bundle files to reference either. | 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.