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.
Overall
score
23%
Does it follow best practices?
Validation for skill structure
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill long-polling-handlerActivation
7%This description is severely underdeveloped, essentially just naming the skill without explaining its purpose or capabilities. It lacks any concrete actions, meaningful trigger terms, or guidance on when to use it. The repetitive trigger terms and boilerplate category mention provide no value for skill selection.
Suggestions
Add specific actions the skill performs, e.g., 'Implements long polling connections to wait for server responses, handles timeout management, and processes delayed API responses'
Include a 'Use when...' clause with natural trigger scenarios like 'Use when implementing real-time updates, waiting for async API responses, or when the user mentions polling, server-sent events, or delayed responses'
Add varied trigger terms users might naturally say: 'polling', 'wait for response', 'real-time API', 'async updates', 'server push'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the concept 'Long Polling Handler' without describing any concrete actions. There are no verbs or specific capabilities listed - it doesn't explain what the skill actually does. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond naming itself, and provides no 'when should Claude use it' guidance. The 'Triggers on' section just repeats the skill name rather than providing meaningful context. | 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', 'polling API', or 'wait for response'. | 1 / 3 |
Distinctiveness Conflict Risk | While 'long polling' is a specific technical concept that provides some distinctiveness, the lack of detail about what actions it performs could cause confusion with other API-related skills. The category mention 'API Integration' is too broad. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
7%This skill is essentially a placeholder with no substantive content. It describes what long polling handler assistance would do in abstract terms but provides zero actual guidance on implementing long polling - no code examples, no timeout strategies, no reconnection patterns, no error handling. A developer reading this would learn nothing they couldn't infer from the skill's title alone.
Suggestions
Add executable code examples showing a basic long polling implementation (e.g., fetch loop with timeout, retry logic, and connection management)
Include specific guidance on handling common long polling challenges: timeout configuration, reconnection backoff strategies, and graceful degradation
Provide concrete validation steps for testing long polling implementations (e.g., simulating server delays, connection drops)
Remove generic boilerplate sections ('Capabilities', 'Example Triggers') and replace with actual technical content
| 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. There are no steps, no sequence, and no validation checkpoints. The content only describes when the skill activates, not how to perform long polling tasks. | 1 / 3 |
Progressive Disclosure | The content has some structure with clear sections, but there are no references to detailed documentation. For a topic like long polling that could benefit from examples and edge cases, the lack of any linked resources is a missed opportunity. | 2 / 3 |
Total | 5 / 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.