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.
34
0%
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/conditional-request-helper/SKILL.mdQuality
Discovery
0%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 repeats the skill name as its own trigger term, provides no concrete actions or capabilities, and lacks any 'Use when...' guidance. It would be nearly impossible for Claude to correctly select this skill from a pool of available skills.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Implements HTTP conditional requests using ETags, If-Modified-Since, and If-None-Match headers to optimize API responses and reduce bandwidth.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about ETags, conditional headers, 304 responses, HTTP caching, If-None-Match, or cache validation in API development.'
Remove the duplicate trigger term and replace with diverse, natural keywords users would actually use when needing help with conditional HTTP requests.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description provides no concrete actions whatsoever. It only names itself ('Conditional Request Helper') and states it's for 'API Development' without describing what it actually does—no mention of ETags, If-Modified-Since headers, caching, or any specific operations. | 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 or equivalent trigger guidance. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are the skill's own name repeated twice ('conditional request helper, conditional request helper'). There are no natural user keywords like 'ETag', 'If-None-Match', 'HTTP caching', '304', or 'conditional headers' that a user would actually say. | 1 / 3 |
Distinctiveness Conflict Risk | The description is extremely generic—'API Development' could overlap with dozens of other API-related skills. Without specifying what conditional requests entail or what distinguishes this skill, it would easily conflict with any other API development skill. | 1 / 3 |
Total | 4 / 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/placeholder with no actual content about HTTP conditional requests. It contains no code, no examples, no concrete guidance, and no domain-specific knowledge — just repeated references to the skill name wrapped in generic boilerplate sections. It provides zero value to Claude.
Suggestions
Add concrete, executable code examples showing HTTP conditional request patterns (e.g., ETag generation, If-None-Match header handling, returning 304 Not Modified responses) in at least one framework.
Define a clear workflow for implementing conditional requests: e.g., 1) Generate ETag/Last-Modified on responses, 2) Check conditional headers on incoming requests, 3) Return 304 or full response accordingly, with validation steps.
Remove all generic boilerplate sections ('When to Use', 'Capabilities', 'Example Triggers') and replace with actionable technical content about conditional request headers (ETag, If-None-Match, If-Modified-Since, If-Unmodified-Since) and status codes (304, 412).
Include specific examples for REST API frameworks (e.g., Express.js, FastAPI, Spring Boot) showing how to implement conditional GET and conditional PUT/PATCH with optimistic concurrency control.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and boilerplate. It explains nothing Claude doesn't already know, repeats the phrase 'conditional request helper' excessively, and provides zero domain-specific information about HTTP conditional requests (ETags, If-None-Match, If-Modified-Since, etc.). | 1 / 3 |
Actionability | There are no concrete code examples, commands, HTTP headers, status codes, or any executable guidance whatsoever. Every section is vague and abstract — 'Provides step-by-step guidance' without actually providing any. | 1 / 3 |
Workflow Clarity | No workflow, steps, or process is defined. The skill claims to provide 'step-by-step guidance' but contains none. There are no validation checkpoints or sequences of any kind. | 1 / 3 |
Progressive Disclosure | The content is a flat, monolithic placeholder 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.