long-polling-handler
Long Polling Handler - Auto-activating skill for API Integration. Triggers on: long polling handler, long polling handler Part of the API Integration skill category.
38
Quality
7%
Does it follow best practices?
Impact
95%
0.96xAverage 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/long-polling-handler/SKILL.mdQuality
Discovery
7%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, essentially just naming the skill without explaining what it does or when to use it. The repeated trigger term and lack of concrete actions make it nearly useless for skill selection. It reads like auto-generated boilerplate rather than a thoughtful description.
Suggestions
Add specific actions the skill performs, e.g., 'Implements long polling connections to receive real-time updates from APIs, manages connection timeouts, and handles reconnection logic.'
Include a 'Use when...' clause with natural trigger terms like 'Use when implementing real-time updates, waiting for server responses, polling APIs, or when the user mentions long polling, server-sent events alternatives, or keeping connections alive.'
Remove the duplicate trigger term and expand with user-friendly variations like 'real-time data', 'continuous polling', 'API streaming', or 'push notifications'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the concept 'Long Polling Handler' without describing any concrete actions. There are no verbs indicating what the skill actually does (e.g., 'implements', 'manages connections', 'handles timeouts'). | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond naming itself, and the 'when' is only implied through the category mention. There is no explicit 'Use when...' clause or meaningful trigger guidance. | 1 / 3 |
Trigger Term Quality | The trigger terms are redundant ('long polling handler' repeated twice) and overly technical. Missing natural variations users might say like 'real-time updates', 'server push', 'waiting for response', or 'keep connection open'. | 1 / 3 |
Distinctiveness Conflict Risk | While 'long polling' is a specific technical concept that provides some distinctiveness, the vague 'API Integration' category and lack of specific use cases could cause overlap with other API-related skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
7%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 implementation guidance for long polling. It consists entirely of generic boilerplate that could apply to any skill topic. A developer needing to implement long polling would gain nothing from this content - no code examples, no timeout strategies, no error handling patterns, no comparison with alternatives like SSE or WebSockets.
Suggestions
Add executable code examples showing a basic long polling implementation (client-side request loop with timeout handling and server-side endpoint)
Include a clear workflow: 1) Make request 2) Handle timeout/response 3) Process data 4) Reconnect with backoff strategy 5) Handle errors
Remove all generic boilerplate ('provides automated assistance', 'follows best practices') and replace with specific long polling patterns (exponential backoff, connection pooling, graceful degradation)
Add concrete guidance on when to use long polling vs WebSockets vs SSE, with specific use case examples
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains nothing Claude doesn't already know. Phrases like 'provides automated assistance' and 'follows industry best practices' are meaningless filler with zero actionable information. | 1 / 3 |
Actionability | No concrete code, commands, or specific implementation details are provided. The skill describes what it does in abstract terms but never shows how to actually implement long polling - no HTTP examples, timeout handling, or reconnection logic. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. Long polling involves specific steps (initial request, timeout handling, reconnection, error recovery) but none are documented. The 'Capabilities' section lists vague promises without any sequence or validation. | 1 / 3 |
Progressive Disclosure | The content has clear section headers and mentions related skills, but there are no references to detailed documentation. The structure exists but contains no substantive content to organize or link to. | 2 / 3 |
Total | 5 / 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.