etag-handler

Etag Handler - Auto-activating skill for API Development. Triggers on: etag handler, etag handler Part of the API Development skill category.

1.00x

Quality

Does it follow best practices?

Impact

100%

1.00x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./planned-skills/generated/15-api-development/etag-handler/SKILL.md

Quality

Discovery

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 severely underdeveloped, essentially serving as a placeholder rather than a functional skill description. It provides no information about what the skill actually does with ETags (generate, validate, parse, etc.) and offers no meaningful trigger guidance beyond repeating the skill name. Claude would have no basis for selecting this skill appropriately.

Suggestions

Add specific actions the skill performs, e.g., 'Generates and validates ETag headers for HTTP responses, implements conditional GET requests, manages cache invalidation logic'

Add a 'Use when...' clause with natural trigger terms like 'Use when implementing HTTP caching, handling conditional requests, working with If-None-Match headers, or optimizing API response caching'

Include common variations users might mention: 'etag', 'cache headers', 'conditional requests', '304 Not Modified', 'HTTP caching', 'cache validation'

Dimension	Reasoning	Score
Specificity	The description only names the skill ('Etag Handler') and mentions 'API Development' but provides no 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 the name, and the 'when' guidance is essentially just the skill name repeated. There's no explicit 'Use when...' clause or meaningful trigger guidance.	1 / 3
Trigger Term Quality	The only trigger terms listed are 'etag handler' repeated twice, which is redundant and overly narrow. Missing natural variations users might say like 'etag', 'cache validation', 'conditional requests', 'If-None-Match', 'HTTP caching', or '304 response'.	1 / 3
Distinctiveness Conflict Risk	The term 'etag' is fairly specific to HTTP caching mechanisms, which provides some distinctiveness. However, 'API Development' is very broad and could overlap with many other API-related skills. The lack of specific capabilities makes it hard to distinguish from other API skills.	2 / 3
	Total	5 / 12 Passed

Implementation

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This skill is essentially a placeholder template with no actual instructional content about ETag handling. It lacks any concrete guidance on HTTP caching headers, If-None-Match/If-Match handling, or implementation patterns. The content describes meta-information about the skill rather than teaching Claude how to perform the task.

Suggestions

Add executable code examples showing ETag generation, validation, and 304 Not Modified responses in at least one language/framework

Include specific HTTP header examples (ETag, If-None-Match, If-Match) with request/response pairs

Define a clear workflow for implementing ETag handling: generate hash -> set header -> validate on subsequent requests -> return 304 or full response

Remove all generic boilerplate ('provides automated assistance', 'follows industry best practices') and replace with actual technical content

Dimension	Reasoning	Score
Conciseness	The content is padded with generic boilerplate that explains nothing specific about ETags. Phrases like 'provides automated assistance' and 'follows industry best practices' are filler that waste tokens without adding value.	1 / 3
Actionability	No concrete code, commands, or specific guidance is provided. The skill describes what it claims to do but never shows how to actually implement ETag handling - no HTTP headers, no caching logic, no validation examples.	1 / 3
Workflow Clarity	No workflow is defined. There are no steps, no sequence, and no validation checkpoints. The content only lists vague 'capabilities' without explaining any actual process for implementing ETag handling.	1 / 3
Progressive Disclosure	The content is a flat, uninformative document with no structure beyond generic headings. There are no references to detailed materials, no examples, and no navigation to related resources despite mentioning 'Related Skills'.	1 / 3
	Total	4 / 12 Passed

Validation

81%

Warnings & errors only

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

Repository: jeremylongshore/claude-code-plugins-plus-skills
Commit: b8a3b3e

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

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.