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.
32
0%
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
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 repeats the skill name as its own trigger term, provides no concrete actions or capabilities, and lacks any 'Use when...' guidance. It would be nearly impossible for Claude to correctly select this skill from a pool of similar API-related skills.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Caches API responses to reduce redundant HTTP calls, manages cache expiration and invalidation, stores and retrieves cached responses from local storage.'
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, or implement response caching for REST endpoints.'
Remove the duplicated trigger term and replace with diverse natural keywords users might say, such as 'cache responses', 'store API results', 'avoid repeated API calls', 'HTTP caching', 'response memoization'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions whatsoever. It only names the skill ('Api Response Cacher') and a vague 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 'Use when...' clause or equivalent trigger guidance. The phrase 'Auto-activating skill for API Integration' is too vague to serve as either. | 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 description is extremely generic—'API Integration' could overlap with dozens of other API-related skills. Without specific actions or clear triggers, there is nothing to distinguish this from any other API-related skill. | 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 is a boilerplate placeholder skill with no actual content about API response caching. It contains no executable code, no concrete guidance, no workflow steps, and no technical substance whatsoever. Every section is generic filler that could apply to any topic by swapping the skill name.
Suggestions
Add concrete, executable code examples showing how to implement API response caching (e.g., using Redis, in-memory caches, or HTTP cache headers with specific libraries)
Define a clear workflow for implementing response caching: identify cacheable endpoints → choose cache strategy (TTL, invalidation) → implement cache layer → validate cache behavior
Include specific patterns and configuration examples such as cache key generation, TTL strategies, cache invalidation approaches, and handling stale data
Remove all the meta-description sections ('When to Use', 'Example Triggers', 'Capabilities') that describe the skill rather than teaching the actual technique
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler with no substantive information. It explains what the skill does in vague, repetitive terms without providing any actual technical content about API response caching. Every section restates the same thing in different words. | 1 / 3 |
Actionability | There is zero concrete guidance—no code, no commands, no specific patterns, no examples of caching strategies, no library recommendations. The content only describes what it claims to do without actually doing any of it. | 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 any sequenced instructions. | 1 / 3 |
Progressive Disclosure | The content is a flat, shallow placeholder with no meaningful structure. There are no references to detailed files, no layered content, and the sections that exist contain no real information to organize. | 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
c8a915c
- 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.