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
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 that restates the skill name without providing any meaningful information about capabilities, use cases, or trigger conditions. It fails on all dimensions: no concrete actions, no natural trigger terms, no explicit 'when to use' guidance, and highly generic categorization that would conflict with other API-related skills.
Suggestions
Describe specific concrete actions the skill performs, e.g., 'Makes asynchronous HTTP requests to external APIs, handles polling for long-running operations, and processes API responses with retry logic.'
Add a 'Use when...' clause with natural trigger terms, e.g., 'Use when the user needs to call an external API, make async HTTP requests, fetch data from REST endpoints, or handle webhook callbacks.'
Remove the duplicate trigger term 'async api caller' and replace with varied natural language terms users would actually say, such as 'API call', 'HTTP request', 'REST API', 'fetch endpoint', 'async request'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description provides no concrete actions. 'Async Api Caller' and 'API Integration' are vague labels with no explanation of what the skill actually does (e.g., making HTTP requests, polling endpoints, handling callbacks). | 1 / 3 |
Completeness | Neither 'what does this do' nor 'when should Claude use it' is meaningfully answered. There is no 'Use when...' clause, and the description only restates the skill name without explaining functionality. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'async api caller' repeated twice, which is not a natural phrase users would say. Missing common terms like 'API request', 'HTTP call', 'fetch data', 'REST', 'webhook', etc. | 1 / 3 |
Distinctiveness Conflict Risk | 'API Integration' is extremely generic and could overlap with any skill involving APIs. There are no distinct triggers or specific use cases that would differentiate this from other API-related skills. | 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 is an empty placeholder with no substantive content. It contains only generic boilerplate descriptions that repeat the phrase 'async api caller' without providing any actual guidance, code examples, or technical detail about async API calling patterns. It fails on every dimension of the rubric.
Suggestions
Add concrete, executable code examples demonstrating async API calling patterns (e.g., using aiohttp, httpx, or fetch with async/await) with real request/response examples.
Define a clear workflow for implementing async API calls: setup, making requests, handling responses, error handling/retries, and validation of results.
Remove all boilerplate sections ('When to Use', 'Example Triggers', 'Capabilities') that describe the skill meta-information rather than teaching how to perform the task.
Include specific patterns like rate limiting, retry with backoff, concurrent request batching, and webhook handling with concrete code snippets for each.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and boilerplate. It explains nothing Claude doesn't already know, provides no specific technical content, and every section restates the same vague idea ('async api caller') without adding value. | 1 / 3 |
Actionability | There is zero concrete guidance—no code, no commands, no API patterns, no examples of async calling patterns. Every bullet is abstract and descriptive rather than instructive. | 1 / 3 |
Workflow Clarity | No workflow, steps, or process is defined. The skill claims to provide 'step-by-step guidance' but contains none. There are no validation checkpoints or sequenced instructions. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of generic text with no references to supporting files, no structured navigation, and no bundle files to support it. There is no meaningful content to disclose progressively. | 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
3a2d27d
- 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.