CtrlK

conditional-request-helper

Conditional Request Helper - Auto-activating skill for API Development. Triggers on: conditional request helper, conditional request helper Part of the API Development skill category.

Install with Tessl CLI

npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill conditional-request-helper

What are skills?

Overall
score

17%

Review — 0%

Does it follow best practices?

Validation — 11 / 16 Passed

Validation for skill structure

SKILL.md

Review

Evals

Activation

This description is essentially a placeholder with no substantive content. It fails to explain what conditional requests are, what actions the skill performs (e.g., implementing ETags, handling If-None-Match headers, caching strategies), or when users should invoke it. The redundant trigger terms provide no value for skill selection.

Suggestions

Add specific capabilities: describe what the skill does, e.g., 'Implements HTTP conditional requests using ETags, If-Modified-Since, and If-None-Match headers for efficient caching and bandwidth optimization.'

Include natural trigger terms users would say: 'ETag', 'conditional GET', 'If-Modified-Since', 'HTTP caching', '304 Not Modified', 'cache validation'.

Add an explicit 'Use when...' clause: 'Use when implementing HTTP caching, handling conditional headers, or optimizing API responses to avoid redundant data transfer.'

Dimension	Reasoning	Score
Specificity	The description only names the skill ('Conditional Request Helper') and mentions 'API Development' as a category, but provides no concrete actions or capabilities. There is no explanation of what the skill actually does.	1 / 3
Completeness	The description fails to answer 'what does this do' beyond the name, and the 'when' clause is just a redundant repetition of the skill name rather than meaningful trigger guidance.	1 / 3
Trigger Term Quality	The trigger terms are just the skill name repeated twice ('conditional request helper, conditional request helper'). No natural user keywords like 'ETag', 'If-Modified-Since', 'caching', 'HTTP headers', or '304' are included.	1 / 3
Distinctiveness Conflict Risk	The vague 'API Development' category and lack of specific capabilities means this could easily conflict with any other API-related skill. Nothing distinguishes it from general API helpers.	1 / 3
	Total	4 / 12 Passed

Implementation

This skill is essentially an empty placeholder that describes itself rather than providing any actual instruction. It contains no concrete information about conditional HTTP requests (ETags, If-None-Match, If-Modified-Since, caching headers, 304 responses, etc.) and would provide zero value to Claude when handling API development tasks.

Suggestions

Replace the meta-description with actual content: explain conditional request headers (ETag, If-None-Match, If-Modified-Since, Last-Modified) with executable code examples

Add concrete implementation examples showing how to implement conditional GET requests and handle 304 Not Modified responses in at least one language/framework

Include a clear workflow for implementing conditional requests: 1) Add ETag/Last-Modified to responses, 2) Check conditional headers on requests, 3) Return 304 or full response

Remove all 'this skill provides' and 'when to use' boilerplate - focus entirely on actionable technical content

Dimension	Reasoning	Score
Conciseness	The content is padded with generic boilerplate that provides no actual information. Phrases like 'provides automated assistance' and 'follows industry best practices' are meaningless filler that waste tokens without teaching Claude anything specific.	1 / 3
Actionability	There is zero concrete guidance - no code, no commands, no specific examples of conditional requests (ETags, If-Modified-Since, etc.). The content describes what the skill supposedly does rather than instructing how to do anything.	1 / 3
Workflow Clarity	No workflow is defined. The skill claims to provide 'step-by-step guidance' but contains no actual steps. There are no processes, sequences, or validation checkpoints for implementing conditional requests.	1 / 3
Progressive Disclosure	The content is a monolithic block of meta-description with no useful structure. There are no references to detailed materials, no organized sections with actual content, and no navigation to supporting documentation.	1 / 3
	Total	4 / 12 Passed

Validation

69%

Warnings & errors only

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: 23 days ago

Table of Contents

Activation 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.