etag-handler
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill etag-handlerEtag Handler - Auto-activating skill for API Development. Triggers on: etag handler, etag handler Part of the API Development skill category.
Overall
score
19%
Does it follow best practices?
Validation for skill structure
Activation
7%This description is severely underdeveloped, essentially just naming the skill without explaining its purpose or capabilities. It lacks any concrete actions, meaningful trigger terms, or guidance on when to use it. The repeated 'etag handler' trigger term suggests auto-generated content without human refinement.
Suggestions
Add specific actions the skill performs, e.g., 'Generates and validates ETag headers for HTTP caching, handles conditional GET/PUT requests, implements cache validation logic'
Include a 'Use when...' clause with natural trigger terms like 'caching headers', 'conditional requests', '304 Not Modified', 'cache validation', 'HTTP caching'
Describe the scenarios where this skill applies, e.g., 'Use when implementing HTTP caching, handling conditional requests, or optimizing API responses with cache headers'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names 'Etag Handler' without describing any concrete actions. There's no explanation of what the skill actually does - no verbs describing capabilities like 'generates', 'validates', 'manages', etc. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond naming itself, and provides no 'when should Claude use it' guidance. The 'Triggers on' section just repeats the skill name rather than providing meaningful trigger scenarios. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'etag handler' repeated twice, which is technical jargon. Missing natural user terms like 'caching', 'HTTP headers', 'conditional requests', '304 response', or 'cache validation'. | 1 / 3 |
Distinctiveness Conflict Risk | While 'Etag Handler' is a specific technical concept that wouldn't broadly conflict with many skills, the lack of detail about what it actually handles means it could overlap with other API or caching-related skills without clear differentiation. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%This skill content is essentially a placeholder template with no actual substance. It contains zero technical information about ETag handling (HTTP headers, cache validation, If-None-Match, weak vs strong ETags, etc.) and provides no actionable guidance whatsoever. The content describes what a skill should do rather than actually teaching anything.
Suggestions
Add concrete code examples showing ETag generation, validation, and response handling (e.g., returning 304 Not Modified)
Include specific HTTP header examples: ETag response header format, If-None-Match request header handling
Provide a clear workflow for implementing ETag-based caching: generate hash -> set header -> validate on subsequent requests -> return 304 or full response
Remove all generic boilerplate ('automated assistance', 'industry best practices') and replace with actual technical content about ETag patterns
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains nothing specific about ETags. Phrases like 'automated assistance' and 'industry best practices' are filler that Claude doesn't need. | 1 / 3 |
Actionability | No concrete code, commands, or specific guidance on implementing ETag handling. The content only describes what the skill claims to do without actually providing any executable instructions. | 1 / 3 |
Workflow Clarity | No workflow is defined. There are no steps, no validation checkpoints, and no actual process for implementing ETag handling in APIs. | 1 / 3 |
Progressive Disclosure | No structure beyond generic headings. No references to detailed documentation, no examples, and no navigation to related resources that would actually help with ETag implementation. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
69%Validation — 11 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 11 / 16 Passed | |
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.