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
Quality
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 only provides the skill name, a generic category label, and repeats the skill name as trigger terms. There are no concrete actions, no natural user keywords, and no guidance on when to use this skill.
Suggestions
Add specific actions the skill performs, e.g., 'Caches API responses to reduce redundant calls, manages cache expiration, retrieves cached data, and invalidates stale entries.'
Include a 'Use when...' clause with natural trigger terms like 'cache API response', 'store API result', 'avoid repeated API calls', 'reduce API requests', 'cache expiration'.
Differentiate from other API skills by specifying the caching focus: 'Use when optimizing API performance through response caching, not for making new API calls or authentication.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions whatsoever. 'Api Response Cacher' is just a name, and 'Auto-activating skill for API Integration' is vague abstract language with no specific capabilities listed. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' (no actions described) and 'when should Claude use it' (no explicit use cases or triggers beyond the skill name). Both components are missing or extremely weak. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'api response cacher' repeated twice, which is the skill name itself rather than natural keywords users would say. Missing terms like 'cache', 'caching', 'store response', 'API calls', 'reduce requests', etc. | 1 / 3 |
Distinctiveness Conflict Risk | 'API Integration' is extremely generic and could conflict with many other API-related skills. There's nothing distinguishing this caching skill from other API skills without describing what caching operations it performs. | 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 template with no actual content about API response caching. It contains only generic boilerplate describing what a skill should do without providing any concrete implementation guidance, code examples, caching strategies, or workflow steps. The skill fails to teach Claude anything actionable about the topic.
Suggestions
Add concrete code examples showing how to implement API response caching (e.g., using Redis, in-memory caches, or HTTP cache headers)
Define a clear workflow for when and how to cache responses, including cache invalidation strategies and TTL considerations
Include specific patterns like cache-aside, write-through, or stale-while-revalidate with executable code snippets
Remove generic boilerplate sections ('When to Use', 'Example Triggers') and replace with actual technical content
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains nothing specific about API response caching. Phrases like 'provides automated assistance' and 'follows industry best practices' are filler that Claude doesn't need. | 1 / 3 |
Actionability | No concrete code, commands, or specific implementation guidance is provided. The skill describes what it does abstractly ('provides step-by-step guidance') without actually providing any guidance. | 1 / 3 |
Workflow Clarity | No workflow, steps, or process is defined. The content only describes trigger phrases and vague capabilities without any actual procedure for implementing API response caching. | 1 / 3 |
Progressive Disclosure | No structure beyond generic headings. No references to detailed documentation, examples, or related files. The content is a shallow placeholder with no depth or navigation to actual implementation details. | 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.