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.
35
3%
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 extremely weak—it is essentially just a skill name repeated with boilerplate template language. It provides no concrete actions, no meaningful trigger terms beyond the skill name itself, and no guidance on when Claude should select this skill. It reads like an auto-generated placeholder rather than a useful skill description.
Suggestions
Add concrete actions the skill performs, e.g., 'Implements long polling endpoints, manages connection timeouts, handles reconnection logic, and processes deferred server responses.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user needs to implement long polling, server push via HTTP, real-time updates without WebSockets, or comet-style communication patterns.'
Remove the duplicated trigger term ('long polling handler' appears twice) and expand with natural variations users might say, such as 'HTTP polling', 'deferred response', 'hold request', or 'polling API'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names 'long polling handler' but provides no concrete actions—it doesn't explain what the skill actually does (e.g., implements long polling endpoints, manages connection timeouts, handles retry logic). 'Auto-activating skill for API Integration' is vague filler. | 1 / 3 |
Completeness | The 'what' is essentially absent—there are no described capabilities beyond the name. There is no explicit 'when' clause or trigger guidance; the 'Triggers on' line just repeats the skill name rather than describing usage scenarios. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'long polling handler' repeated twice. It misses natural variations users would say like 'long poll', 'polling endpoint', 'server push', 'HTTP long polling', 'real-time updates', or 'comet pattern'. | 1 / 3 |
Distinctiveness Conflict Risk | The term 'long polling' is somewhat niche and unlikely to conflict with many other skills, but the generic 'API Integration' category label and lack of specificity could cause overlap with other API-related skills. | 2 / 3 |
Total | 5 / 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—a template placeholder that contains no actual technical content about long polling. It consists entirely of self-referential meta-descriptions ('this skill provides guidance for long polling handler') without any implementation details, code examples, API patterns, or actionable instructions. It fails on every dimension of the rubric.
Suggestions
Add concrete, executable code examples showing a long polling implementation (e.g., a Python/Node.js client that polls an endpoint with exponential backoff, timeout handling, and reconnection logic).
Define a clear workflow: 1) Set up the polling endpoint, 2) Implement the polling loop with timeout, 3) Handle responses and errors, 4) Validate connection stability—with specific code at each step.
Remove all meta-description sections (Purpose, When to Use, Capabilities, Example Triggers) and replace with actual technical content: connection parameters, retry strategies, comparison with SSE/WebSockets, and common pitfalls.
If advanced patterns exist (e.g., long polling with authentication, rate limiting, or webhook fallback), reference them via clearly signaled links to separate files rather than leaving the skill as a hollow overview.
| 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 'long polling handler' without adding substance. | 1 / 3 |
Actionability | There is zero concrete guidance—no code, no commands, no specific implementation details, no examples of long polling patterns. The content only describes rather than instructs, offering nothing executable or copy-paste ready. | 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 flat, monolithic block of meta-descriptions with no structure pointing to detailed resources, no references to external files, and no meaningful organization of content layers. | 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
4dee593
- 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.