api-caching-strategy
Api Caching Strategy - Auto-activating skill for API Development. Triggers on: api caching strategy, api caching strategy Part of the API Development skill category.
35
3%
Does it follow best practices?
Impact
94%
1.00xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/15-api-development/api-caching-strategy/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 description is extremely weak across all dimensions. It reads as an auto-generated stub with no concrete actions, no natural trigger terms beyond the skill name repeated, and no explicit guidance on when Claude should select it. It would be nearly useless for skill selection among a large set of available skills.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Designs and implements caching strategies for REST and GraphQL APIs, including cache invalidation policies, TTL configuration, and HTTP cache header setup.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about caching API responses, cache invalidation, Redis/Memcached setup, HTTP caching headers, CDN caching, or improving API response times.'
Remove the duplicated trigger term and expand with natural variations users would actually say, such as 'cache layer', 'response caching', 'cache-control headers', 'cache busting', 'ETag', 'stale-while-revalidate'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions whatsoever. It merely names the topic 'API Caching Strategy' without describing what the skill actually does—no verbs like 'implements', 'configures', 'designs', or 'evaluates' are present. | 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—only a vague category label and a redundant trigger phrase. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'api caching strategy' repeated twice. This misses natural variations users would say such as 'cache API responses', 'caching layer', 'Redis cache', 'HTTP caching headers', 'cache invalidation', 'TTL', 'CDN caching', etc. | 1 / 3 |
Distinctiveness Conflict Risk | The phrase 'API Caching Strategy' is somewhat specific to a niche topic, which provides some distinctiveness. However, without concrete actions or clear triggers, it could overlap with general API development or performance optimization 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 shell with no substantive content. It consists entirely of boilerplate meta-descriptions about what the skill would do, without any actual caching strategy guidance, code examples, or actionable instructions. It provides no value beyond restating its own title in various ways.
Suggestions
Replace the meta-description sections with actual API caching strategy content: HTTP cache headers (Cache-Control, ETag, Last-Modified), CDN caching, application-level caching (Redis/Memcached), and cache invalidation patterns with concrete code examples.
Add executable code examples showing cache implementation, e.g., setting Cache-Control headers in Express/FastAPI, Redis caching middleware, and ETag validation logic.
Include a workflow for choosing and implementing a caching strategy: 1) Identify cacheable endpoints, 2) Choose caching layer (HTTP/CDN/application), 3) Implement with specific configuration, 4) Validate with cache hit/miss metrics.
Remove all 'When to Use', 'Example Triggers', and 'Capabilities' boilerplate sections—these waste tokens describing the skill rather than teaching the skill.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and meta-description. It explains what the skill does in abstract terms without providing any actual caching strategy content. Every section restates the same vague idea with no substantive information. | 1 / 3 |
Actionability | There is zero concrete guidance—no code, no commands, no specific caching strategies, no examples of cache headers, TTL configurations, or any executable instructions. It only describes rather than instructs. | 1 / 3 |
Workflow Clarity | No workflow is defined. There are no steps, no sequence, no validation checkpoints. The skill claims to provide 'step-by-step guidance' but contains none. | 1 / 3 |
Progressive Disclosure | The content is a flat, monolithic block of meta-descriptions with no references to detailed materials, no links to related files, and no meaningful structural organization of actual content. | 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
4dee593
- 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.