timeout-handler
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill timeout-handlerTimeout Handler - Auto-activating skill for API Integration. Triggers on: timeout handler, timeout handler Part of the API Integration skill category.
Overall
score
19%
Does it follow best practices?
Validation for skill structure
Activation
7%This description is severely underdeveloped, essentially just restating the skill name without explaining what it does or when to use it. It lacks any concrete actions, meaningful trigger terms, or explicit usage guidance. The redundant trigger terms ('timeout handler, timeout handler') suggest auto-generated content without human refinement.
Suggestions
Add specific actions the skill performs, e.g., 'Implements retry logic for failed API calls, configures timeout thresholds, handles connection failures gracefully'
Include a 'Use when...' clause with natural trigger terms like 'API timeout', 'request failed', 'connection timeout', 'retry failed requests', 'slow API response'
Remove the redundant trigger term and expand with variations users would naturally say when encountering timeout issues
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Timeout Handler') and mentions it's for 'API Integration' but provides no concrete actions. There's no explanation of what the skill actually does - no verbs describing capabilities like 'retries requests', 'manages connection timeouts', or 'handles failed API calls'. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name itself, and the 'when' guidance is just a circular repetition of the skill name. There's no explicit 'Use when...' clause or meaningful trigger guidance. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'timeout handler' repeated twice, which is redundant and overly narrow. Missing natural variations users would say like 'API timeout', 'request timeout', 'connection failed', 'retry logic', or 'slow response'. | 1 / 3 |
Distinctiveness Conflict Risk | While 'timeout handler' is somewhat specific to a particular concern, the vague 'API Integration' category could overlap with many other API-related skills. Without concrete actions described, it's unclear how this differs from general error handling or retry skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%This skill is an empty template with no actual content about timeout handling. It contains only meta-descriptions of what a skill should do without any concrete implementation guidance, code examples, or technical details. The entire content could be replaced with actual timeout handler patterns, retry logic examples, and configuration guidance.
Suggestions
Add concrete code examples showing timeout implementation patterns (e.g., exponential backoff, circuit breakers, deadline propagation)
Include specific timeout configuration values and when to use them (connection timeout vs read timeout vs overall timeout)
Provide a clear workflow for implementing timeout handling: 1) identify timeout types needed, 2) implement with specific code, 3) test failure scenarios
Remove all meta-content about 'when to use' and 'example triggers' - replace with actual technical guidance on timeout patterns
| 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 information about timeout handling that Claude doesn't already know. | 1 / 3 |
Actionability | No concrete code, commands, or specific guidance is provided. The content only describes what the skill claims to do without any executable examples or actual implementation details for timeout handling. | 1 / 3 |
Workflow Clarity | No workflow is defined. The skill mentions 'step-by-step guidance' but provides none. There are no actual steps, validation checkpoints, or process sequences for implementing timeout handlers. | 1 / 3 |
Progressive Disclosure | The content is a shallow placeholder with no meaningful structure. There are no references to detailed materials, no code examples to organize, and no actual content that would benefit from progressive disclosure. | 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.