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.
32
Quality
0%
Does it follow best practices?
Impact
90%
1.13xAverage 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/async-api-caller/SKILL.mdQuality
Discovery
0%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 essentially a placeholder with no substantive content. It provides only the skill name, a redundant trigger, and a generic category label without explaining what the skill does, what specific capabilities it offers, or when it should be selected. This would be nearly useless for skill selection among multiple options.
Suggestions
Add specific concrete actions the skill performs (e.g., 'Makes asynchronous HTTP requests, handles rate limiting, manages request queues, processes API responses').
Include a 'Use when...' clause with natural trigger terms users would actually say (e.g., 'Use when the user needs to call external APIs, make HTTP requests, fetch remote data, or integrate with web services').
Remove the duplicate trigger term and replace with varied natural language keywords (e.g., 'API call', 'HTTP request', 'REST endpoint', 'fetch data', 'web service').
| 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 (e.g., make requests, handle responses, retry logic). | 1 / 3 |
Completeness | The description fails to answer both 'what does this do' and 'when should Claude use it'. There is no 'Use when...' clause and no explanation of capabilities beyond the vague category label 'API Integration'. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'async api caller' repeated twice, which is the skill name itself rather than natural user language. Users would say things like 'call an API', 'make HTTP request', 'fetch data from endpoint' - none of which are present. | 1 / 3 |
Distinctiveness Conflict Risk | 'API Integration' is extremely generic and would conflict with any other API-related skill. There are no distinguishing features mentioned that would help Claude select this skill over others in the same domain. | 1 / 3 |
Total | 4 / 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 content is entirely meta-descriptive boilerplate with no actual instructional value. It describes what the skill should do without providing any concrete guidance, code examples, or actionable steps for implementing async API calls. The content would need to be completely rewritten with actual implementation details.
Suggestions
Add executable code examples showing async API calling patterns (e.g., using aiohttp, httpx, or fetch with async/await)
Include concrete workflow steps: setup, making requests, handling responses, error handling, and retry logic
Provide specific examples of common async patterns like concurrent requests, rate limiting, and timeout handling
Remove all meta-descriptions ('This skill provides...', 'Capabilities include...') and replace with actual instructional content
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that provides no actual information about async API calling. Every section describes what the skill does abstractly rather than providing concrete guidance. | 1 / 3 |
Actionability | No concrete code, commands, or executable guidance is provided. The content only describes capabilities in vague terms like 'provides step-by-step guidance' without actually providing any steps 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 implementing async API calls. | 1 / 3 |
Progressive Disclosure | No structure for discovery or navigation. The content is a flat list of meta-descriptions with no references to detailed materials, examples, or related documentation. | 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
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.