async-api-caller
Async Api Caller - Auto-activating skill for API Integration. Triggers on: async api caller, async api caller Part of the API Integration skill category.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill async-api-callerOverall
score
17%
Does it follow best practices?
Validation for skill structure
Activation
0%This description is severely lacking across all dimensions. It provides no concrete actions, no natural trigger terms, no explicit usage guidance, and is too generic to be distinguishable from other API-related skills. The description appears to be auto-generated boilerplate with no meaningful content.
Suggestions
Add specific concrete actions the skill performs (e.g., 'Makes asynchronous HTTP requests, handles rate limiting, manages request queues, processes batch API calls')
Include a 'Use when...' clause with natural trigger terms users would say (e.g., 'Use when the user needs to make multiple API calls, handle async requests, or batch process API operations')
Add distinguishing details about what makes this skill unique compared to other API skills (e.g., specific protocols supported, async patterns handled, or particular use cases)
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions whatsoever. 'Auto-activating skill for API Integration' is entirely abstract with no indication of what the skill actually does. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the vague 'API Integration' and completely lacks any 'when should Claude use it' guidance. No 'Use when...' clause is present. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'async api caller' repeated twice, which is technical jargon unlikely to match natural user language. Missing common variations like 'call API', 'make request', 'fetch data', etc. | 1 / 3 |
Distinctiveness Conflict Risk | 'API Integration' is extremely generic and would conflict with any other API-related skills. There are no distinguishing features or specific use cases that would help differentiate this skill. | 1 / 3 |
Total | 4 / 12 Passed |
Implementation
0%This skill is a placeholder template with no actual content. It describes what an async API caller skill would do without providing any concrete guidance, code examples, or actionable instructions. The content is entirely meta-description rather than useful instruction.
Suggestions
Add executable code examples showing async API patterns (e.g., using asyncio/aiohttp in Python, or fetch with async/await in JavaScript)
Include specific guidance on error handling, retry logic, rate limiting, and timeout management for async API calls
Provide concrete examples of common async patterns: parallel requests, request batching, callback handling, and response aggregation
Remove the meta-description sections ('When to Use', 'Example Triggers') and replace with actual implementation guidance
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains nothing specific about async API calling. Every section describes what the skill does abstractly rather than providing actual guidance Claude could use. | 1 / 3 |
Actionability | No concrete code, commands, or executable guidance is provided. The content only describes when the skill activates and what it claims to do, without any actual implementation details or examples. | 1 / 3 |
Workflow Clarity | No workflow, steps, or process is defined. The skill claims to provide 'step-by-step guidance' but contains zero actual steps for performing async API calls. | 1 / 3 |
Progressive Disclosure | No structure beyond generic headings. No references to detailed documentation, no examples, and no navigation to related resources despite mentioning 'Related Skills'. | 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.