etag-handler
Etag Handler - Auto-activating skill for API Development. Triggers on: etag handler, etag handler Part of the API Development skill category.
36
3%
Does it follow best practices?
Impact
100%
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/etag-handler/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 essentially a placeholder with no substantive content. It names the topic (ETag handling) but provides zero detail about what actions the skill performs, what technologies or patterns it covers, or when it should be triggered. The repeated trigger term and boilerplate category labeling add no value.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Generates and validates ETag headers for HTTP responses, implements conditional GET/PUT requests with If-None-Match and If-Modified-Since headers, and configures cache validation logic.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about ETags, HTTP caching, conditional requests, 304 responses, cache validation, If-None-Match, or If-Modified-Since headers.'
Remove the duplicated trigger term ('etag handler' listed twice) and replace with diverse, natural keywords users would actually use when needing this skill.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description provides no concrete actions. 'Etag Handler' and 'Auto-activating skill for API Development' are vague labels with no explanation of what the skill actually does (e.g., generate ETags, validate conditional requests, implement caching headers). | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name itself, and the 'when' clause is just a repeated trigger phrase with no meaningful guidance on when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'etag handler' repeated twice. It misses natural user terms like 'ETag', 'conditional requests', 'If-None-Match', 'HTTP caching', 'cache validation', '304 Not Modified', etc. | 1 / 3 |
Distinctiveness Conflict Risk | The term 'etag' is fairly niche and unlikely to conflict with many other skills, but the description is so vague that it could overlap with general API development or HTTP caching skills without clear differentiation. | 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 actual technical content about ETag handling. It contains only generic boilerplate descriptions and trigger phrases without any executable code, concrete guidance, or meaningful workflow. It provides zero value beyond what Claude already knows about ETags.
Suggestions
Add concrete, executable code examples showing ETag generation (e.g., hashing response bodies), setting ETag headers, and handling If-None-Match / If-Match request headers in at least one framework (Express, FastAPI, etc.).
Define a clear workflow for implementing ETag support: 1) Generate ETag from response, 2) Set response header, 3) Check conditional request headers, 4) Return 304 Not Modified or full response, with validation steps.
Remove all generic boilerplate ('Provides step-by-step guidance', 'Follows industry best practices') and replace with specific ETag patterns: weak vs strong ETags, cache validation flow, concurrency control with If-Match for PUT/PATCH.
Add concrete examples of common ETag pitfalls (e.g., ETags changing due to compression, clock skew with Last-Modified) and how to handle them.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and boilerplate. It explains nothing Claude doesn't already know, provides no specific technical content about ETags, and pads with generic phrases like 'Provides step-by-step guidance' and 'Follows industry best practices' without any substance. | 1 / 3 |
Actionability | There is zero actionable content—no code, no commands, no concrete examples of ETag implementation, no HTTP headers, no caching logic, no middleware patterns. The skill describes what it could do rather than instructing Claude how to do anything. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. There are no steps, no sequence, no validation checkpoints. The skill merely lists vague capabilities without any process for implementing ETag handling. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of generic text with no references to supporting files, no structured sections with real content, and no navigation to deeper materials. 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.