api-response-cacher
Api Response Cacher - Auto-activating skill for API Integration. Triggers on: api response cacher, api response cacher Part of the API Integration skill category.
35
3%
Does it follow best practices?
Impact
91%
0.97xAverage 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/api-response-cacher/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 is an extremely weak description that is essentially auto-generated boilerplate. It provides no concrete actions, no natural trigger terms, and no guidance on when Claude should select this skill. The only slight positive is that the name 'API Response Cacher' hints at a specific niche, but the description completely fails to elaborate on it.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Caches API responses to reduce redundant HTTP calls, implements cache expiration policies, stores and retrieves cached responses from local storage or memory.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user wants to cache API responses, reduce API call frequency, store HTTP results locally, implement response caching, or optimize repeated API requests.'
Remove the duplicated trigger term ('api response cacher' listed twice) and replace with varied natural language terms users might actually say, such as 'cache responses', 'store API results', 'avoid duplicate API calls', 'HTTP caching'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions whatsoever. It only names the skill ('Api Response Cacher') and a category ('API Integration') without describing what it actually does—no mention of caching strategies, cache invalidation, storing responses, or any specific operations. | 1 / 3 |
Completeness | The description fails to answer both 'what does this do' and 'when should Claude use it'. There is no explanation of capabilities and no explicit 'Use when...' clause or equivalent trigger guidance. | 1 / 3 |
Trigger Term Quality | The trigger terms are just the skill name repeated twice ('api response cacher, api response cacher'). There are no natural user keywords like 'cache API responses', 'store HTTP results', 'reduce API calls', 'response caching', or similar terms a user would naturally use. | 1 / 3 |
Distinctiveness Conflict Risk | The term 'API Response Cacher' is somewhat specific to a niche (caching API responses), which provides some distinctiveness. However, the lack of concrete detail means it could overlap with general API integration or HTTP-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 template with no substantive content about API response caching. It contains only boilerplate metadata-like descriptions, trigger phrases, and vague capability claims without any actionable guidance, code examples, or technical detail. It provides no value beyond what the skill's title alone conveys.
Suggestions
Add concrete, executable code examples showing how to implement API response caching (e.g., in-memory cache with TTL, Redis-based caching, HTTP cache headers handling).
Define a clear workflow: 1) Identify cacheable endpoints, 2) Choose caching strategy, 3) Implement cache layer with specific code, 4) Validate cache behavior with test commands.
Replace the boilerplate 'Capabilities' and 'Example Triggers' sections with actual technical content such as cache invalidation strategies, cache key design patterns, and common pitfalls.
Include specific configuration examples (e.g., Redis config, cache-control headers, ETags) that are copy-paste ready rather than describing capabilities abstractly.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and boilerplate. It explains nothing Claude doesn't already know, repeats the trigger phrase multiple times, and contains no substantive technical content about API response caching. | 1 / 3 |
Actionability | There is zero concrete guidance—no code, no commands, no specific caching strategies, no examples of implementation. Every section is vague and descriptive rather than instructive. | 1 / 3 |
Workflow Clarity | No workflow, steps, or process is defined. The 'Capabilities' section claims step-by-step guidance but provides none. There are no validation checkpoints or sequenced instructions. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of placeholder text with no references to supporting files, no structured navigation, and no meaningful content organization. There are no bundle files to support it either. | 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.